Like with spam and its basically zero conversion rate, yes. But I’ve seems to remain clear of it in the tags I follow. So far.

I just hope that the fediverse stays small enough to remain an undesirable target for AI slop mongers.

I think the difference is scale. Before it was x% of humanity making shitting opinions where x < 100. Now it’s x% of humanity+AI, where x is, say, 100,000% of humanity. I don’t think we’re currently equipped to separate the wheat from that much chaff.

Yikes. Back to Newegg for me!

When I was in college we had disposable film cameras. That was more than enough intrusion, thank you very much. I’ve always been incredibly happy that we did not have digital cameras in those years. 😅

“Every dependency is an asset. Every dependency is a liability.”

It never happened–since they knew in advance, they had time to whip up something cool if there wasn’t anything else. It didn’t have to be massive. I just wanted to see some clean non-trivial code and a clear understanding of how it worked. Fizzbuzz wouldn’t have impressed. :)

One of my classmates years ago loved bash. They wrote a filesystem for their OS class in Bash. It was a really, really impressive and bad idea.

But how do you handle candidates who say something like “look, there’s heaps of code that I’m proud of and would love to walk you through, but it’s all work I’ve done for past companies and don’t have access (or the legal right) to show you?”

It never once happened. They always knew in advance, so they could code something up if they felt like it.

I asked candidates to bring me some code they were proud of and teach me how it worked. Weeded out people really quickly and brought quality candidates to the top. On two separate occasions we hired devs with zero experience in the language or framework and they rocked it. Trythat with your coding interview, eh? 🙂

mpv also works well from the command line.

The author said they wanted maximum accessibility, so they didn’t opt for a particular platform’s voting system.

They most definitely do.

Recommendation algorithms are great for discovering related information and new stuff.

I agree that open, controllable recommendation algorithms would be great. But right now using none of the currently widespread social media recommendation algorithms at all (and just matching keywords instead) makes for a less-abusive, more positive experience. IMHO.

I mean, I have a BS and MS in computer science, so you can use that as guidance as to whether or not I know what an algorithm is. :)

In this context, though, it should be clear that “The Algorithm” refers to a specific social networking algorithm that chooses the content you see in order to maximize advertising revenue.

So yes, Lemmy has algorithms that show different content based on your input, but that’s a wildly different animal. Notably, I’m the one deciding, and also they’re not trying to maximize ad revenue.

Disk is cheap. Always get a copy of whatever it is you “buy”. If that’s somehow not possible, consider the purchase a short-term rental.

What’s the pay rate for artists?

Algorithm-free solves a lot of problems.

The real problem with the internet isn’t Facebook or Twitter or Reddit, it’s the fact the entire experience is pretty much controlled by Microsoft and Google. As they shape your content, lock you out of areas and generally dictate what’s “legal” or even what gets found during your searches.

I agree the Google and MS are a problem, but Facebook, Twitter, Reddit are also a problem, albeit a different one.

Another option here is GitHub. I keep my markdown notes in a repo that I just clone from there to my various machines… And then I get to edit them in vim. 😂

If you’re up on your bash coding skills: in the Firefox debugger, you can find the URL to the page images and see if there’s a usable pattern in the URLs. If there is, you could script it in bash and repeatedly call curl to download the images.

I don’t think it’s bad–it’s impossible to make error-free material, and it’s more error-free than not, for sure.

But other people are right: you’ll “graduate” to MDN and not look at W3 Schools again.

You can absolutely write a Star Wars knockoff, though. You just can’t call it that. There’s some gray line in there somewhere.

A shell script can be more concise if you’re doing a lot of shell things. Keeps you from having os.system() all over the place.

Things like “diff the output of two programs” are just more complex in other languages.

I love rust, but replacing my shell scripts with rust is not something I would consider doing any more than I’d consider replacing rust with my shell scripts.

This is my favorite cd feature by a large margin.

“The expert has failed more times than the beginner has even tried.” 😊👍

As much as I hate ads and hate the concept that I would be forced to view them, these kind of legal wranglings freak me out. It seems quite possible that a ruling in my favor here would be used against me somewhere else. Courts and lawmakers don’t understand technology and don’t realize the effects laws have. And frankly, the rest of us don’t have much idea, either.

“Unless you give us all your money to put in our new bank, we might be facing insolvency issues.”

So the page says:

And this does in fact happen - even though some of your data was still waiting to be sent, or had been sent but not acknowledged: the kernel can close the whole connection.

But Stevens says:

By default, close returns immediately, but if there is any data still remaining in the socket send buffer, the system will try to deliver the data to the peer.

The SO_LINGER socket option lets us change this default.

And, referring to the default close behavior:

We assume that when the client’s data arrives, the server is temporarily busy, so the data is added to the socket receive buffer by its TCP. Similarly, the next segment, the client’s FIN, is also added to the socket receive buffer (in whatever manner the implementation records that a FIN has been received on the connection). But by default, the client’s close returns immediately. As we show in this scenario, the client’s close can return before the server reads the remaining data in its socket receive buffer. Therefore, it is possible for the server host to crash before the server application reads this remaining data, and the client application will never know.

Also:

If l_onoff is nonzero and l_linger is zero, TCP aborts the connection when it is closed. That is, TCP discards any data still remaining in the socket send buffer and sends an RST to the peer, not the normal four-packet connection termination sequence.

I’m having trouble reconciling this with the article’s position that data will be discarded by the sender OS with a plain non-SO_LINGER close().

I can see how the sender might be blissfully unaware that the receiver program might have crashed after the data had been sent and the connection had been closed, but before the data had arrived at the receiver program. And that’s where some kind of application ACKing mechanism might be in order.

I can also see that the receiver OS might happily collect the data and shutdown the socket correctly and then the sender app thinks everything is fine, but the receiver app has crashed and will never see the data.

But neither of those conditions result in the receiver app in the example showing less than 1,000,000 bytes received unless there’s an error.

What am I missing?

For sure–I just don’t tend to watch anything more than once. :) Most of my federated identity and offsites are at SDF, which is a solid place with a mission I respect and certainly don’t mind giving $36/year to. Grayjay for stupid vids (if I could just get it to work with FCast…)

Depends on your definition of “evil”, I guess.

Might get there. Right now I just have external SSH access (key only) to get to the files. I also need an offsite, so it’s all sent to a remote server with rsync and gocryptfs. I only have about 90 GB of stuff on there right now; I don’t do any media serving.

https://archive.is/tCWIM

I took my money from YouTube and started giving it to Kagi. 🙂👍

I’m a gray developer and nothing makes me more get-off-my-lawn than too many levels of abstractions. :)

I used to give Google money for services (Drive and YouTube), but I’ve already stopped doing that because of their evil ways. This just hammers it home that much more.

Edit: The shitty part is what a cool company it used to be. And to watch it destroy itself like this is just sad.

I was a premium subscriber for a long time, and probably still would be if Google hadn’t turned so evil that I can no longer in good conscience pay them any money.

But what pushed me over the edge with an ad blocker was a page I got to where every paragraph had a video ad in between. That was it.

Turns out if you get rid of ads and the algorithm, you end up back in the land of sanity.

Louis Rossmann: “when the pirate experience is better than the paid experience, you have a problem.”

I haven’t tried it, but anything that’s interoperable is fine by me.