Right, you do have to understand that either way, if you put something on the public internet, it is gone.

I don’t want a company to sell my data, making money off of me, then having the audacity to ask me for MORE money on top (nitro). It feels gross.

I don’t mind sharing bits of myself online otherwise.

The owners of federated instances can also just start selling your data too at any point. And as you said, advertisers will also just scrape public data trivially. Basically, the internet and world is a terrible place.

But Discord has cultivated a queer membership by serving a different need than those platforms: privacy.

Yeah, gonna stop reading right there. Discord is absolutely selling your data. Nothing against inclusivity features though.

Discord became ubiquitous because it works well, and is free. Take VC money, run at loss, get tons of users, enshittify, die because something better becomes good enough. It’s just another one of those speed runs, which will happen over and over again until the end of humanity.

Also, how do I verify that this fork isn’t malware wrapped in emulator code?

The code is open source, you read it all, ensure that you download exactly the code you read, and you compile it yourself. That’s the only way, in general, to accomplish this.

I can assure you that Google, an ad tech company with a near monopoly on web browsers, has an interest in eliminating ad blockers in the browser that they have direct control of.

Will be interesting to see the new “verification” methods that people come up with. AI won’t be good at “weird” things, like, I dunno, putting your shirt over your head and doing a jumping jack. At least until millions of those videos exist, then time for a new move? It’s not like people will just give up because this tech exists, we have the entirety of human history to tell us that much.

Isn’t it that horrid ugly fucking foot

Read… instructions? I love teaching people that git very often prints out what you should do next.

git: “to continue, resolve conflicts, add files, and run rebase —continue”
dev: …time to search stack overflow

All that said… just use lazygit. It does help to know CLI git first to put things in context, but if you do, no need to punish yourself every day by not using a UI.

fzf? https://github.com/junegunn/fzf

Out of the box, would only help searching shell commands that have been run, so for files, things like “vim file.txt”, which is obviously not usually how files are edited (you’d use the file browser in a text editor or IDE)

However if you find a way to list all files on your system by modified time, you can pipe it to fzf for a slick fuzzy find search.

Maybe ag would work here too: https://github.com/ggreer/the_silver_searcher

Debugger good for microscopic surgery, log stream good for real time macro view. Both perspectives needed.

deleted by creator

To be that dick, a headless component library is still meant to do something, show an example of it being used!

Would be funnier if it was just “JS” on the right, because obviously HTML and CSS are involved too, but JS is where all hell breaks loose

Seems more about salvage of what’s on the board:

[…] the process makes it easier to retrieve the valuable metals attached to it. “After [it dissolves], we’re left with the chips and circuit traces which we can filter out,”

If it’s easier to salvage, maybe more salvaging will be done than dumping.

This is what life is when all viable phones are made by two giant tech companies.

You can also just… pay for it? I give money to JetBrains in exchange for incredibly useful tools. It’s okay to pay for things.

I’m sure plenty of the offenders are legitimate, but it’s completely safe to check private key pairs into code, or to bake them in to images. It entirely depends on what the key pairs are used for. Very common to include key pairs for development/test environments, for example. If it’s a production secret, of course you don’t do this.

Pussy on the chainwax!

It’s here, it’s there, it’s everywhere. The problem with replacing things that work with something “better” is that “better” is subjective, so you end up with a new “better” way every few years, and maintaining existing systems becomes a god awful slog. See the JavaScript ecosystem.

The bash I wrote 10 years ago still works today, and it will still work in 10 more years. The same bash will very likely work on your computer, on a remote server, etc. This is the power of not chasing “better” all the time.

Try running a Ruby or Node program from 10 years ago today on your computer. Now, try running it on a random Linux server.

Please do not take this as a slight against Ruby or Node, or any other high level programming language. Bash compared to those is simply apples and oranges, they are not the same thing.

By all means, if you have a project that requires a Ruby runtime anyway, write operational scripts with Ruby, run them with Rake, etc.

Want a portable script that doesn’t depend on a complex runtime? Use bash.

If bash is too limiting, use Perl. No, seriously. Perl is fine. It is about as ubiquitously available as bash, and the standard library likely has what you need to get the job done. People blindly dismiss Perl because some blog post told them to, usually in the context of writing application code. You’re not writing application code, you’re writing scripts. Would you write an application with bash? No.

Feels like this will be a very common occurrence with people rushing to build and use new apps, and host new servers. There are plenty of positives to fediverse vs centralized, but it doesn’t come without negatives.

I tried it, but for some reason I can’t stand the fake iOS interface. It just feels cheap or something, I like kbin as a PWA much more. For the record, I use an iPhone and I do like actual iOS