Android is already Linux-based, so that is just running regular Linux binaries while providing tweaks and shims to make those binaries play nicer with Android's setup. Things running in it don't have root access, they've only got the access that the base "UserLAnd" app has due to how Android handles security but that's more than enough to get you a "traditional" desktop with utilities.
It's more akin to installing and running all sorts of programs on a non-admin Windows account with all the "Install for only me" options instead of "Install for all users". Except instead of Windows, it's just Linux.
Basically, this.
Cinnamon is my choice on both laptop and desktop, though if it's for a particularly underpowered system, I go for MATE.
In theory yes, but right now the main kbin.social website's DDoS protection solution is making it a bit wonky for Lemmy instances to properly federate with it. At least that's what I've heard as of a couple days ago. Not sure if they've got that fixed yet.
EDIT: Looks like as of yesterday, they've fixed that so it should be working correctly in theory.
Optimally the defederated instance should not show the community at all but that would require changes on actual lemmy code.
I agree, that would be the best thing is if it just made the defederated community disappear instead of become a local fork. My thinking for the sidebar notice was in case a local fork was the intended outcome by the Lemmy devs as opposed to an unintended side-effect or a bug. If it was intended then it should be made obvious that it happened, and if it wasn't intended, it should just be hidden all together.
My concern about it isn't for false-flags, but for end-user confusion.
In specific cases like this, it looks, to the defederated instance's users, like they're still participating in the whole community they thought they were participating in. There's nothing outwardly visible to that end user that implies it's anything except what they thought it was unless they already had prior knowledge about how it works and about whether their instance was still federated with the instance that hosted the community. Under the hood, however, it's only a small fraction of the actual whole community, and it's completely isolated from the rest of that community out in the fediverse. That's where the problem comes in, is that there's no indication that you're actually only viewing and participating in a small fraction of that community instead of the whole one you thought you were.
The fix for this could be as simple as the local Lemmy instance checking if it's still federated with the remote community and if it isn't, put a note in the community's sidebar (and maybe one under the post/reply buttons) that says it isn't currently federated and that you'll only see local user activity and your posts/comments won't show up for non-local users. Something like that would basically eliminate the confusion and solve the problem that's being seen here.
So it appears that lemmy.world users can only see and interact with other new lemmy.world posts, so if you see a post from beehaw right now while using a lemmy.world account, it’s clear it’s from another lemmy.world user (if you are aware of the defederation, it definitely doesn’t tell you which is pretty bad imo)
Well that's weird, but I see what you're saying now. From Lemmy.world, you can still see the Beehaw communities and participate in them, but only as if they were local Lemmy.world communities. There's nothing in the UI to show that they're not actually communities hosted on Beehaw, but functionally they still act as local communities, even though their name, description, icon, stats, and mods are all copies of the actual community on Beehaw.
Yikes then, but for a different reason, and that seems like a bug with defederation in Lemmy.
It's not really drama or a beef between Lemmy.world and Beehaw, but Beehaw has recently (as in yesterday) added both Lemmy.world and sh.itjust.works to their blocklist as those two instances are very large with completely open registrations and Beehaw admins/mods were having trolls/unsavory people go through those two instances and creating new accounts to get around bans and stuff like that, is my understanding.
Right now, Lemmy doesn't have more fine-grained controls for instances like Beehaw which requires approval/vetting to create an account on to block interactions from particular instances without just cutting off ties with that instance completely. Ideally, Lemmy would add an option to allow federation between instances as normal, but require external users (from other instances) to be approved by the instance (such as Beehaw) before being allowed to interact with the communities there.
I've got both a Lemmy.world and Beehaw account so I can still participate in communities on here, but... I also seen this post come up in my "Local" feed as soon as you posted it.
That's not the weird thing though, as I was on Lemmy.world when that happened, and I'm also not subscribed to [email protected] on my Lemmy.world account, yet it still showed up in "Local" there.
Currently attempting to comment from my Lemmy.world account instead of my Beehaw account, to see if that's still working as well. If this submits, then I'm wondering if something about the federation blocklists in Lemmy isn't quite working as it should.
EDIT: Well, viewing and posting from a defederated instance apparently still works, so yikes indeed.
Yeah, to me it seems like that would be helpful to someone who's a moderator on that community or an instance admin, but I've seen it mentioned by several other people that anyone actively viewing the thread will see that notification, no matter their moderator status or lack thereof.
Perhaps it could be a bug with the Lemmy backend software?
(I just got the "Report created" notification while typing this reply, as well! Strange!)
If I understand correctly, it will just pop that up if a comment is reported in the thread you're currently viewing, as Lemmy auto-refreshes everything going on in the thread you're viewing.
Linux Mint for desktops/laptops (Cinnamon if the hardware can handle it, MATE if it's a bit long in the tooth), and Debian for servers.
I've used several distros (yes, even Arch btw) through the years but I just keep finding myself coming back to the Debian-based ones. I guess I just feel most at-home with the way it has things set up, or something.