What a wird little keyboard. Very inspiring.

But the guide is soooo detailed. Wow, great work!

Doesn’t look like it, but you can be the one writing one.

Embrace, Extend, Extinguish

1. Embrace:

They implement ActivityPub and connect to all the available servers. A load of new users will see the content here and all the communities here will be absolutely flooded with new content and users.

2. Extend:

ActivityPub will be extended. Many new features will be added, that don’t really match the standard, but they are mostly useful so some developers will try to add them to let’s say Lemmy. They won’t be blr to develop new features on their own and some stuff with threads will always be broken or half baked. Threads users will belittle the users here, some will maybe go there, cause it just works and is otherwise the same.
New users at the same time will most likely go directly to threads cause it’s backed by a giant company, always works and has more features.

3. Extinguish:

They will cut the federation.
Communities here will feel empty and most users will just leave. Only the hard core will stay and that won’t be sustainable. The fediverse becomes even less attractive for new users and will devolve into a niche community.

I don’t use obsidian. I use Joplin. It has nextcloud integration and works flawlessly.

For the rest (e.g. Tasks, Collaborate Office) I use DAVx5 and the nextcloud App to sync.

Doesn’t Nextcloud do all this?

I don’t really know, why it really HAS to be all that. I think that not a lot of people will have those specific set of requirements.

Also I really dislike the section about “solving not wanting to self host by making it federated” that is not how that works. Please host stuff yourself. Please support those who host your stuff. This part makes you sound cheap and stupid.

https://xkcd.com/345/

I like how it’s a full stack but years of experience for each individual part position.

Yeah, just have 10 years of Javascript, C++ and rust. Also you must prove to have designed and built huge systems of microservices. And also be a product owner with your customer-facing awesome communication skills (which they have listed twice btw.).

No biggie.

Oh and also we won’t even give hints about pay, but we do up to the minimum legal requirements in non-financial benefits.

Pease be satire! 😐

Okay, the others are a little short for what you need.

Your VPN needs it’s own DNS. With that DNS you can route the traffic internally from the VPN subnet to the server. Then you can set the server up to only take requests from that subnet either via firewall or the reverse proxy.

This is the way! I also have a synapse with this ansible playboy up and running and it works like a charm.

Look into Periodical as well, it’s on fdroid and completely local. It also shows when the next period should be and works better than some closed source apps.