Recent comments in /f/Coding

z3d wrote

Without more information about what you want to learn and what your objectives are, it's hard to recommend specific sites. Do you have any idea what language you're aiming to take up, and have you got a specific project in mind?

Here are some basic guidelines if you're just looking to get involved:

  • Before just diving in, work out what you want to achieve. Sometimes it's easier to take an existing project and work on adding features than starting from scratch. Identifying your area of interest will help narrow the selection of languages you'll want to focus on.
  • Start small. Don't take on big projects until you're comfortable achieving tasks you set yourself. Running code on a webserver is a good way to start seeing immediate results. Choose a language that suits, and hack something together. Javascript, html and css are a good entry into coding, and the results are immediate, no compilation required, just a webserver and and browser!
  • Find a text editor that you're prepared to invest time learning. VS Code / Codium might appear daunting at first, but if you're committed to learning, it'll pay off in time by helping you write and format your code with inline help, syntax highlighting, autocomplete, and error checking etc. For something simpler but still coder-focused, Bluefish is a lot less capable but a lot easier to pick up, and still has syntax highlighting and support for various languages.
2

cumlord OP wrote (edited by a moderator )

I have a project (that's tied into this) that I'm prioritizing for the moment, and will be making a more fleshed out version of this available soon after.

I want some more granular tools with individual torrents too, and some stats, so I'll see what i can do.

The transmission-rpc plugin works great for managing one snark at a time though.

1

NotQball wrote

I will wait for a more mature/developed tool that has alarms and monitoring of torrents. Ideally it will monitor torrents and have some kind of configurable actions. It would be like a stock (stockmarket) chart analysis tool. Start (buy), Stop (hold), Delete the evidence (unusual patterns). I like to start simple... but it is always complicated.

2

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