Recent comments in /f/Coding

BlueHat wrote (edited )

Reply to by ____

Is it open source?

- futaba + futallaby + tinyib -

What are those links supposed to be? It seems like only one of them is pointing to a repository, although the other two also mention some kind of code. Am confused.

2

TallestSkil wrote

The trick is to never learn JavaScript (or have post-traumatic stress from the professor who taught it to you such that you don’t remember it), and therefore you won’t be ABLE to code a website with bad JavaScript. It’s the perfect solution.

Joking (am I?) aside, you’re obviously right. What we need to fight back is a browser explicitly designed to destroy all tracking mechanisms. And not just the obvious ones. For example, wipe all loaded websites of the ability to track cursor location and page scroll depth. Automatically erase all HTTP referrers from every single link so websites have no idea where you came from when you got to a specific page (make them think you manually typed in the URL every time). Oh, and the big one:

A WEBSITE SHOULD ONLY BE ABLE TO SEE COOKIES FROM ITS OWN DOMAIN. IT SHOULD NEVER HAVE ANY CAPABILITY WHATSOEVER TO EVEN SEE A RANDOMIZED, ANONYMIZED HASH OF WHAT OTHER COOKIES ARE ON THE DEVICE. When I heard that browsers just let any website see any other website’s cookies, I was so fucking appalled that I couldn’t put it into words. The mere idea of such a security flaw never even occurred to me, yet it’s literally common practice in browsers.

7

smartypants wrote (edited )

I don't really care about that, seems like 4Chan level bickering at that point. I care more about the poor code pushed out.

Me too.

That said, lots of fun memories hanging around some skilled FreeBSD programmers in San Francisco years ago, with me busting their chops.

Their biggest complaint? Any cool driver fixes for "pc platform" USB , Audio, Network Cards, etc was lifted, duped , forked to OpenBSD , etc, then rapidly "stolen" AND COPY-LEFTED with GPL and shoved into Linux with new restrictive headers rubber stamped on all files... and crippled by GPL.

They REALLY really believe in totally free software and puke at hypocritical GPL2 GPL3 etc.

1

Rambler wrote

Donenfeld identified numerous problems with Macy's code, but rather than object to the port's release, Donenfeld decided to fix the issues. He collaborated with FreeBSD developer Kyle Evans and with Matt Dunwoodie, an OpenBSD developer who had worked on WireGuard for that operating system. The three replaced almost all of Macy's code in a mad week-long sprint.

A good response.

This went over very poorly with Netgate, which sponsored Macy's work. Netgate had already taken Macy's beta code from a FreeBSD 13 release candidate and placed it into production in pfSense's 2.5.0 release. The forklift upgrade performed by Donenfeld and collaborators—along with Donenfeld's sharp characterization of Macy's code—presented the company with a serious PR problem.

Not a great response.

This combative response from Netgate raised increased scrutiny from many sources, which uncovered surprising elements of Macy's own past. He and his wife Nicole had been arrested in 2008 after two years spent attempting to illegally evict tenants from a small San Francisco apartment building the pair had bought.

I don't really care about that, seems like 4Chan level bickering at that point. I care more about the poor code pushed out.

1

Wahaha wrote

The simpler sales pitch is that vim can do everything you can and cannot imagine. Just do a search for what you want to accomplish and find out how it is done.

First time users should just go through vimtutor, which will start vim with a document that shows you all the basic functionality and let's you do all these things, so you can build muscle memory.

As for the things vim can do that you cannot even imagine: you can type stuff in vim, let's say text_A, then undo this and write something else, let's say text_B. If you now decide text_A is really where it's at, in normal editors you're fucked, but vim can actually get it back: with this plugin

2

idk wrote

Reply to comment by abralelie in Gitlab hosted on I2P by abralelie

When did I say that? It is the official I2P code host. I'm a member of the I2P team, I run the service, we own the "I2P Developers" namespace. We approved the TOS before they went into effect on zzz.i2p. We require GPG for our commits so all the checkins are attributable to the person who checked them in. People who want to can file an issue with the TOS in the TOS repository I linked before. I can't guarantee that I will take action on it but the catch-all answer behind the answer to issues with my TOS is to host more competing git hosts on I2P, which I wrote an easy-to-follow guide for that is linked prominently in the TOS.

It's open to the community so the community can contribute, and host their own code if they want. In the same way another team member ran the old mtn host. The only difference is that I can allow people to join gitlab and use it as a public code host, whereas mtn was open only to the I2P team.

2

idk wrote

Reply to comment by Google in Gitlab hosted on I2P by abralelie

I am familiar with this complaint, but it came a little too late for me to change the hosting service decision from Gitlab to Gitea. That being said, since I generally consider gitea a little more managable for smaller, self-hosted deployments, and since it's pure-Go and a little more monolithic, it will be slightly easier to set it up to be self configuring with SAMv3. So give it a little time, and I'll make Gitea I2P-Native.

2

idk wrote

Reply to comment by abralelie in Gitlab hosted on I2P by abralelie

TL:DR because I write the TOS. It's a service hosted and administered by me, personally, and made available to the community. I'm not a corporation, I don't have staff, I kind of have a datacenter but it's actually just a bunch of old desktops and a switch, and I have non-gitlab responsibilities. I have to make policies that keep this service manageable for me to administer and that means things like not allowing people to potentially automate registration. The fact that I have to go in and approve accounts case-by-case means that automatic registration is almost moot point and I don't have to set up a captcha.

If my TOS are not satisfactory, I also wrote a guide to hosting your own gitlab service on I2P using gitlab: http://i2p-projekt.i2p/en/blog/post/2020/03/16/gitlab-over-i2p which is still accurate. It can be hosted on old hardware, raspberry pi's, probably with enough hacking a chroot on a phone if you wanted. There are plenty of other easy-to-setup git services like gitea, cgit, gitbucket, or whatever else anyone wants. Just point a tunnel at the web service and the SSH port and set the http_proxy environment variable to the value of an HTTP Proxy.

2