KubeRoot

Ah, but you see, “John” and “Doe” are two names - first and last - and when you say “My name is”, you’re really listing out your names, with spaces inbetween!

But then there’s hyphenated names, and I have no idea how those are treated.

I’d say having a GUI is not inherently stupid. The stupid part is, if I understand it correctly, the GUI being a required component and the primary access method.

“There’s a big issue with how Lemmy works, here’s how I think decentralization should be approached instead.”

Again, I feel like you’re making the wrong point in the wrong place. My understanding is that you came to a project designed with the ideals of federation, and you complain that it shouldn’t be federated. That should probably be done as a fork of Lemmy, or an independent competitor.

It seems to me like you’re in ideological conflict with Lemmy’s developers, where you see no value in what Lemmy seeks to create. That’s completely fine, of course, but I really feel like you’re making your case in the wrong place.

Having terabytes of information possibly disappearing because one person gets in a car accident on their way to work isn’t an improvement vs a centralized system hosted on AWS.

Federation does not mean terabytes of information disappearing - to my understanding, posts, comments and votes are already duplicated across the instances. What would be lost is ownership of communities/posts, and accounts created on that instance, as well as things like image posts where the images are stored on one instance.

However, if images weren’t stored as links in those posts, accounts could be fully migrated, and communities could be migrated or even just federated with other communities, nothing would have to be lost.

Communities would be moderated by their creator, server admins could decide not to host content from any communities they don’t want to host, if no server admin wants to host your community then you’re free to host it on your own server or to fix the problems with it.

I feel like that structure wouldn’t work, just looking at how much defederation is happening, server owners wouldn’t want to be affiliated with certain content at all. It did also remind me of the fact that ActivityPub is not just Lemmy - you can also interact with mastodon and kbin on Lemmy, which is rooted in the federated approach.

There’s illegal content on Lemmy right now, even instances that don’t want to host it need to clean up their images folder because of it, so it’s not as if the way it works right now is any better for that and it’s not as if there’s no instance admin ready to host that content.

True, I feel like the issue only gets worse as you blur the line between different instances more, but I have no data to back that up.

User credentials can be stored securely. Do you think your instance admin has a text file with your password written in plain characters?

I feel like you failed to address my point, that with the current security standard, data leaks are still considered a threat to your password security. Even in the best case, getting access to hashed passwords means being able to brute force it without any rate limits. Maybe I’m wrong, but you’d need to either prove that password hashes leaking are not an issue at all, or figure out a way to provide trusted decentralized authentication server architecture, or figure out a way to store the passwords where leaks are not an issue… Or give up on using passwords and require a different authentication method, like public key authentication.

The third credential I was suggesting is just one solution […]. I’m sure much more intelligent people could come up with another solution.

It’s a bit hypocritical of me, since I mentioned smarter people than me working on something, but I feel like if you’re strongly suggesting Lemmy should be majorly reworked in this way, there’s some expectation for you to provide a solution, not just say that somebody will figure it out.

Sounds like what you want basically is not Lemmy.

It also raises some pretty big issues, like who gets to moderate communities? Right now you make a community on a specific instance, you follow that instance’s rules, so the instance host has authority over the community. If you disagree with the instance’s rules, or with the way the community is ran, you can make a community on another instance, or even make your own instance with your own rules.

And from the other side, there need to be people with the authority to remove communities, and remove people/posts across different communities. Right now that’s the responsibility of the instance hosts, to my understanding - content is hosted on a primary instance, and stored through federating instances, so the primary instance has a responsibility to keep it clean of illegal material. Who would have this power and responsibility if instances aren’t differentiated? Sounds like the best case is giving trustworthy people an excessive amount of power, and the worst case is the entire network being shut down due to distributing illegal content and being effectively impossible to moderate.

You also didn’t address the issue of passwords - currently it’s a pretty big deal when hashed+salted passwords leak, considering those passwords compromised… The comparison with AWS is flawed - when using AWS, you’re trusting them, because it’s a big company with a reputation to keep. The situation seems very different when it’s random enthusiasts with highly differing views, and without a central authority to verify them (though there are probably too many to verify anyways)

And you propose that anybody can join the network and receive users’ passwords? On top of that, you’re proposing that you need to also know the “server” your data is stored on and supply that with logging in? Sounds like a really annoying friction point for the user.

I really feel like you’re approaching this from the wrong direction, suggesting Lemmy should abolish the very structure it’s built on for one you’d like more, but I think it could be possible to make the experience nicer without going to those extremes.

Maybe it’d be possible to let multiple instances have authority over an account, without changing its home instance, so that if your original instance goes down, you can keep the same account. And to reduce friction from communities being made across multiple instances, some way for communities themselves to federate/combine would be nice, and is probably being considered by people smarter than me.

I don’t think that’d work, with Lemmy being a federated model, not a fully decentralized one.

How do you handle the actual login? Does that mean every server has access to your password hash? Or do you overhaul the account system to use something like a private and public key, with the user needing to store and transfer the private key to every device they use?

And what happens if two people register with the same username on two instances that aren’t federating? Do they somehow need to still communicate with all other instances in the network they operate in, to prevent that from happening? Because the alternative I see is the login being random in some way or tied to the instance, in which case you still lose the impression of a single service.

If I’m not mistaken, right now anybody could host a non-federating Lemmy instance, if they just wanted a small private community in this style. To my understanding, that’s the idea behind federation, and a founding concept of Lemmy - it’s not a giant service distributed across trusted servers, but a network of smaller communities that communicate with limited trust.

I know that after arch is Gentoo, the last one is FreeBSD

I think calling it “a page worth” is understating it somewhat, especially if you want a full install to actually use stuff. In reality, when installing at first, you’ll be finding stuff you missed for a while, like hardware video decoding.

Also, are you referring to just the direct instructions for one choice? Because to me, the point of installing manually is educating yourself on the choices, choosing one that suits you, and understanding what you’re doing to set it up. Of course, when you’re doing subsequent installs, you already know that stuff - but at that point you might just want to write an install script instead of running them manually.

Funny that you mention it, a few months ago when updating stuff I got a new feature on my Android phone… Offline subtitle generation based on audio, just realtime generated from anything outputing sound on my phone.

A Google search suggests this might be an older feature - not sure if my phone didn’t support it, or if I maybe just missed it, or if they added a more obvious button.

Google has a separate app for that stuff, called Private Compute Services. Right now it’s nothing like an offline Google assistant replacement, but I thought it’s really nice to have that stuff available without relying on internet access.

That’s not exactly anti-FOSS, to my understanding, since the “free” part refers to freedom. As long as after you pay you are free to use the software as you want and get access to the source code, I think it might still count as FOSS? And then, of course, there’s the option of paid support on free (of charge) software, though I think recent events might suggest that’s not really sustainable.

If I may shill for a moment, that’s something I like about sublime merge - the buttons mostly map to git commands, and it has a nice log showing the commands it ran and their output.

It is pretty well optimized. I think it might not be, like, genius-level amazing, but the devs care about performance and worked to improve it.

In the end though, it’s a game where the entire map (as generated so far) is simulated - I think there’s cases where chunks go to sleep, but it’s not Minecraft’s “stop simulating anything not next to a player”. When combined with players building lots of machines moving many, many items around, you’ll inevitably end up with some serious CPU usage. Not a problem on a decent computer, but I have had friends struggle on weak laptops, even getting dropped as they literally couldn’t keep up with the server.

I do have both installed, Plasma seems better for gaming with performance and experimental features, while GNOME is very stable for work and, ironically, customizes better for my preferences.

EDIT: I use Arch BTW

They’re extruded, but not into strips or strings. I’d argue they’re not long enough to be described as “long”, but that part is certainly imprecise

According to your quote, noodles are long, and they’re strips or strings

That just sounds like a reason to not bother supporting Linux, when Windows is so much more popular

Another counterpoint: When you start implementing all that dummy proofing, you make the software more and more tedious to work with for people who know what they’re doing.

I think it’s quite obviously an issue that needs balance. Some software is meant to be seamless to get started with, so that users can get something done once in a while, some software is meant to be used long-term by professionals and requires productivity. And yet, many people jump on anything they don’t immediately understand as bad UX.

an Artificial Intelligence, a sentient being

So, an artificial sentience then?

It was the laser that’s 20 gigawatts, according to the article, which is notable because such a laser is hard to redirect.

As for the viability of holodecks… Obviously the rest of your points are still valid, but one can only hope that someday we’ll figure something out, the technology being impossible/unviable right now doesn’t mean it’ll stay that way. And this seems to show a theoretical possibility of manipulating light mid-air in the necessary way.

Screw you, Arch is great. It’s not for everybody, but if you want to know how your system is set up, decide what’s running on it, and don’t mind researching and maintaining your software, it’s lovely.

Sincerely, I use Arch BTW

I’d say it would be more clickbaity if you just removed the “TV”, because it’d make you think of smartphones, and those would be much more concerning