I personally prefer browsing the web with JavaScript disabled, and using search engines like Marginalia to find simple websites. I don't see a big difference in experience between browsing these websites in lynx or edbrowse, vs using Gemini.

I get the appeal of having everyone on the network share the same culture and values, but I prefer to just find the people doing that in the wider network of the web.

Still, I'm happy it exists and that people enjoy using it. To each their own!

Nice to see that even in the virtual world, anti-immigration protesters are not "patriotic" enough to know what the flag looks like.

Personally, I'm pretty sentimental about my bike (also a beater, but single speed) and want to keep it going almost no matter what. I think only the frame has remained the same throughout, and at times, I've definitely spent more than the bike is worth to fix it up.

I know that with cars, there's a definite cliff edge where it becomes prohibitively expensive to maintain compared to a new one. But I feel like that's not really true with bikes, perhaps because there are just fewer parts to replace, and it's less invasive to strip out any given part?

I suppose it depends on a few things. Do you have any sentimental attachments to it, and is there anything you would change about the bike if you were buying a new one? Do you think you can get a better one for $200?

It's really hard. Here's my best shot:

A discussion platform for communities.

It's an alternative to Lemmy with some different features. Since it uses the same protocol under the hood, its instances federate with Lemmy. There's more info on the differences here.

You can trust the software in your distro's repositories (if you run a distro with well-maintained repositories). This is because, generally only well-known software gets packaged, the packager should be familiar with both the project and the code, and everything is rebuilt on the distro's own infrastructure, to ensure that a given binary actually corresponds to the source.

It might still be possible for things to slip through, but it's certainly much safer than random programs from online.

Now, I'm not asking companies to open-source their entire codebase. That's unrealistic when an app is tied to a larger platform. What I am asking for: publish a basic GitHub repo with the hardware specs and connection protocols. Let the community build their own apps on top of it.

I agree with this. I think the most important thing is not necessarily the original company releasing their proprietary code (although that would be nice), but it being easy (and legal!) for hackers to reverse engineer and/or build on top of the platform.

The irony is that, since most such products will have some GPL'd code in there somewhere, most products already basically have such a requirement, thanks to the section requiring complete corresponding source including installation instructions. Hopefully, the Vizio case will establish the precedent that users, as well as copyright holders, can take action against such companies.

This might be a silly question, but in what ways did it get worse? Is it the size of the keyboard changing, the predictions not being as good anymore or something else?

With my knowledge of tech companies, I'm not exactly surprised, but I'm not an iPhone user and struggling to understand how a keyboard of all things could get worse.

For me, it would be for her to actually respect my boundaries, and to show an active interest in who I actually am instead of what role I can fulfill for her.

Wait is this how you get up to date when your system is past long term support?

Pretty much! You just modify the apt sources, and upgrade incrementing by each stable release until you reach current stable. Each upgrade guide has a section that points you to the guide for the previous version if your version doesn't match.

Would not recommend doing backups drunk.

:D in my experience, there's a certain amount of drink-inspired overconfidence that can be helpful, but it's very easy to go over. I need more testing to find the exact line - it might also wrap around again if you drink more. More investigation needed :)

I'm happy this has happened. I'm still pretty wary, though. Can there be a cross party debate and agreement on what the limits should be? I worry the "mandatory" part will just get pushed through later on, like the encryption backdoor clause of the OSA.

By dumbing down the suite, are you talking about things like flatpak / atomic distros?

If so, I am also not a fan of those things - give me Debian stable and the software in the repos and I'm happy - but I also don't think I will be harmed by others coming in and trying different approaches. From what I can tell, with each paradigm shift, the old approach doesn't go away, but stays powered by the volunteers who care about it.