That’s one of the many fundamental design shortcomings of the Fediverse.

But, in this particular case, the “how” could be a simple “redirect to a different instance” button, where you could select yours. Or the site could check for the cookies of known servers and check if one has a valid login token, and automatically redirect there.

Right, so it’s all “this might work, or it might not, or might die in a bit” - it’s chaos. It should be a native feature of the fediverse to auto-redirect to your instance.

And then on top of that you find a random Mastodon link in the wild, click it, a Mastodon instance loads, but you can’t reply/toot/do anything, because it’s not your instance and you’re not signed in. I still don’t know how to “convert” a link to my own instance (granted, I haven’t looked into that much really).

Enjoy the ride! :)

Oh! You might find this useful. It’s a list of various setting changes/fixes I made after switching and encountering various issues, or annoyances. Some of these were under Kubuntu, most are under Garuda, but I don’t think anything in there is distro-specific, so it should work on both Debian-based and Arch-based.

If you’ve never installed Linux before, I would start with something user-friendly, like Kubuntu or Bazzite. Both come with KDE as their main Desktop Environment (“DE”), so you could do what OP did looks-wise.

If you’re a technical user, and don’t hate having to sometimes do things manually, try Garuda Linux - it’s Arch-based, but catered very towards Linux newbies and does a lot of hand-holding. I use it and I enjoy it very much.

To specifically do what OP did with his DE - KDE comes with the concept of Panels and Widgets. The top bar you see in the screenshot is a Panel. On it, there are (from right to left) the System Tray widget, a Spacer widget, a Digital Clock widget with customised display format (something you can do in the settings of the widget), another Spacer, an Icons-Only Task Manager widget (displays active applications and lets you pin applications - like the Taskbar in Windows or Dock in macOS), and finally the Application Launcher widget (the Start menu equivalent). Everything is pretty heavily customised (presumably with Panel Colorizer? Not sure), so that - out of the box - even with this exact setup copied, yours would look slightly different.

Maybe you need to read what I wrote again…?

My doctrinal explanation was about suicide being a sin, which is the reason for people of faith not offing themselves left and right. This has nothing to do with how a person handles grief because it’s a different topic.

In terms of grief, I explained that however people may understand the logic of the doctrine, their physical bodies still react to the chemical signals received, and therefore grief is still present.

I’m baffled at your take that this is somehow a “doctrinal explanation”, mate. It’s literally the opposite, I’m talking about biology here.

I have no clue what you mean. Other than stating that suicide is a grave sin, I never touched doctrine or “religion logic”. What are you talking about?

Yeah, that’s essentially what I meant. The validation could happen much like with PGP keys and passwords.

Yep there it is, this is completely contradictory to how GPL 3 works

Judging by their repo tags, they use AGPL, MIT, and Apache, with one repo sitting under BSD. But your point stands.

I did a cursory glance at their GitHub repos - all the ones that state the license terms of the repo are AGPL, Apache or MIT, with one exception - BSD.

So I don’t really get what “licensing terms” are being violated here.

I can’t speak for all religions, but in Christianity suicide is a grave sin, so doing that guarantees eternal damnation.

The other bit, people not being happy about a loved one passing, is not really an issue too - it’s just the “logic of faith” vs “emotions of loss”. Even if we knew for a fact that once you die you get reincarnated into a Happy Bunny, people would still grieve, because that’s how our brain chemistry works.

Depends on how you create it. It could be set up that your app talks to the website, and the identity provider, but the identity provider never talks to the website. As in: you get a token from the IP, store it locally, send it out to he website, the website confirms retrieval and logs you in, and then all the logs get purged on your device so they can’t be retrieved.

The IP side would only see that someone has requested access to some of your data (e.g. proof of age, proof of human, maybe citizenship, if the content is region-locked), and that you have agreed to share it.

The website would only see the tokens of proof, but not who you actually are.

Ironically, the tech behind NFTs might be super helpful with this.

Yup! Which is why institutions that already handle identities (governments, banks, etc) should be involved.

The way I see it: an institution verifies your identity as a human and has your personal details (such as DoB). A tool (similar to, e.g. Sweden’t BankID) is available to the user. When a website says “you must be 18 years old to access this”, a QR code is generated. You scan the code with your tool, and agree to send only the information about whether or not you’re an adult. Not the DoB, not anything else, just a token of “yup, adult”. If a website has a strong anti-bot policy, same same goes for your “proof of human”.

This can be set up in a way that guarantees the user’s privacy (e.g. by just not storing any logs).

If it’s a third party tool that does the verification, that’s false.

The other 50% is knowing what the correct choice* is.

* Notice: whatever choice is made, half the encountered users will say it was the wrong choice.

AFAIK, still no conclusive studies that show microplastics having an overly adverse affect on the human body

The problem is that we’ll never know because there’s no control group. Everybody has them, even fetuses still in the womb. You would have to build bunkers with perfect air filtering, and then go through, like, four generations of humans to breed microplastics-free specimen, which you could then use a the control group for the rest… Only them never leaving the bunker would already invalidate the tests… So, yeah…

The only reason they decided to obfuscate the use of Claude was due to the community starting wars and sending them death threats over it. Nobody is downplaying anything, they literally stated that they did that because managing shit-tier Issues that were all basically “why use AI” was becoming too damaging to the project.

Not sure I understand what you mean.

Like, you verify the account and then give it away to a bot? My assumption is that the “proof of human” would be a unique identifier, meaning that once you’ve attached it to an account, you can’t use it to verify another.

It’s evidence that it works. That the missing piece is the crowd source. You said it’s impossible and magical

The company you linked is 11-13 people. That’s not crowd sourcing, it’s just AI doing the work.

So, which is it? Crowd sourcing, or AI fighting AI?

You said it’s impossible and magical. That is wrong.

Yeah, the way you were voicing it originally (crowd sourcing through communities) requires magic. If you’re suddenly OK bringing in AI of your own, sure, but then you don’t need crowd sourcing - as in the example you yourself posted, a dozen people can do this.

A problem is the datasets are from before the APIs were locked down. It’s hard to get new data. New methods are needed.

You don’t need APIs to do this work. You can easily write clients that just read comments as they appear through regular browser clients. The API lock-down was about preventing people from interacting and posting with the content outside of the official app. You can read content just fine (as far as I’m aware, correct me if I’m wrong).

Communities should be built to combat bots

Communities can’t do much about it. Sure, they’ll ban a bot of five, but your own example showed where the problem lies - you yourself can’t tell if a certain user is a bot, or just a propagandist (or passionate about a topic??). Just recently there was a poster on r/cats (or some such) who was banned by mods for being a bot posting AI slop. They had to register a new account, and re-post their photos with a piece of paper with the date and the cat next to each other, the cat just looked weird. But the community mass-reported the post, and the mods didn’t notice that it was all legit.

Community work would not work here, it’s been proven a billion times already (see: Brexit, 2016 US elections, Romanian elections, Slovenian elections, etc., etc., where network and social media content analysis showed after the fact that there were hundreds of thousands of bot accounts posting russian propaganda).

Instead it seems like the people that are disadvantaged by these networks and bots also have this mentality to ignore and avoid it all.

Much like OP, I agree.

Your proof of your “crowd source this away” idea is a link to a company that very explicitly uses AI to detect trends…? Are you for real right now?