samae

https://gist.github.com/yunfachi/6c073cc6edc18f78cfc60bb9bb3f7143

Osmand?

You're assuming it is useful enough to find the person, and not just A person.

What's scary here is the lack of training/understanding on the investigation side… This is just ignorance.

the family deserves to know that we tried everything

Like, have you tried praying? We don't have any data, so it may be effective.

I run RSS2email and… read my RSS as emails, delivered fresh every morning :)

https://github.com/rss2email/rss2email

Been using self-hosted, static website builder https://simonrepp.com/faircamp/ with satisfying results here

Keep instance small, with all users in the same timezone. Use NixOS, let it update everynight automatically and safely. It's good enough for a small service, downtime is mostly when people are sleeping.

Try again elsewhere, you'll eventually find the right place!

Assembling a second dynamics (analog compressor). First one took me over 8h of work.

Mastodon is part of Lemmy?

I hope you understand how this is discouraging: at present, federation is anything but straightforward.

There's also a question of perspective. If you approach federation with the mindset that it will be like the sort of SSO you get with using google products, microsoft ecosystem, or facebook to log in to many websites, then yes: it's doesn't look straightforward.

If you approach it with the perspective that the coupling between fediverse applications being more loosely coupled, and have the way email work in mind, then it is actually more natural. Each application can do their own thing, and provide all or partial compatibility with the fediverse. Think of a blog application, which rely on the fediverse only for the comment section of each blog posts, but also does other things specific to that application. Taking the example of email again, nobody thinks they should be able to log-in to microsoft outlook using their gmail account, or to gmail using their home-made account, in order to read and send emails.

There's a narrative aspect to it too.

Wouldn't that overload popular instances even more? Right now, popular instances only need to accommodate their users, but with a "fediverse-wide" auth, soon they'll also have to serve content to people who followed that popular link to their content?