bufalo1973

Nice joke!

A federated roaming user directory so you can have the same user at once in different aspects of the Fediverse.

A self-hosted instance has a big advantage: only those working on that admin can have a user. So if you see, p.e., @Emmanuel.macron@gov.fr you know it’s the real account and not a fake one.

Is there a way to join two communities into one?

An initial screen with a select default option.

With containers and shared_ptr/unique_ptr?

I think the "no-JS’ approach is too extreme. I’d rather do a “no-JS framework” buy limited JS.

Joma (Spanish) are good ones. Also Paredes.

Krita and Gimp have very different uses.

The red ones aren’t made of concrete.

Why think it’s a song? That’s like a dog thinking humans sing all the time.

With Android the “AOSP team” has to play cat and mouse with Google.

The nice part is that all those parts can be recreated as open source if SailfishOS gains traction. Just like in Linux private blobs have their open source counterparts.

It’s GPL so you can extend it as you want.

I’m thinking of a federated validation service. The check should be only the first time you use the instance and then at random to check if it’s still valid. And the service could have a journal of instances and send then a message if an account changes. This last part as an option.

The account should be the bare minimum data: name, password, contact and little more.

It would be great if there was a “federated auth service” for all the instances. One account that you could use in each server you like.

Maybe you already know but if you throw yourself into a volcano you don’t dive like in water. You stay above it because of density.

If you can “fly, you fools!”

If it’s private code why not have a private git repository?

Own servers for the cloud and backup servers on another Union government servers with encryption. That should be the both in the Union.