Apples and oranges.
Wireguard is a VPN technology. DuckDNS is a service that lets you create a subdomain on the duckdns TLD and point it at your server. They do completely different things.
You would use DuckDNS if you don’t want to rent your own domain (“rent” because it’s a recurring payment for something over which you have only nominal control). It provides no security, no access control, and it creates no network. It’s just a pointer in the global DNS DB.
Wireguard is a VPN technology, for creating private networks.
One is like a mailing address. The other is like a strongbox. You could give the strongbox to a friend to deliver it to someone who has the key (Wireguard). Or you could write a message on a postcard and mail it (DuckDNS). Or you could put the address on the strongbox and mail it (DuckDNS + Wireguard). The point is, they serve completely different functions.
The two could be used together.
Sure. If nothing else, you could proxy it through an authenticated endpoint, requiring people to log on to view it. But I don’t know the blogging software space very well - there are probably projects with built-in support for this. I’ve started looking around; I suspect the ideal platform isn’t so much a blogging platform, but it’s designed more around a blog design.
If you come across one, please let me know! I’ll keep updating that CryptoPad document. I also started a spreadsheet, which is better suited to the data than a document table, but CryptoPad doesn’t have the ability to embed assets from other documents (other than images), so I’m just doing the table manually.
Absolutely. Good projects attract multiple maintainers; there’s a bit of Darwinism there. When one project I used was archived, I offered to take over maintainership; the author didn’t want to hand it over to me, so I hard forked it and worked with distributions to replace the no-longer-maintained version with mine. It’s the OSS lifecycle, right? And the best thing about OSS - if the maintained loses interest, someone else can simply take over. And if no-one does, maybe it isn’t worth maintaining.
This is so important! Especially for this purpose. Getting several people to join a platform and then put content on it introduces a lot of technical inertia. That’s why it’s important for me to reduce the odds of the project changing their terms of use; increasing costs; moving popular, free features to the “paid” column; and other shenanigans.
See, I don’t believe this. It’s possible the project would die, but so often have popular projects lost their maintainers, and new people step in. They fork it, or have a peaceful transition of ownership, but the project carries on. Yes, some just disappear into obscurity, but the popular ones tend to keep going, sometimes under other names. X11 to XOrg; OpenOffice to LibreOffice; OwnCloud to NextCloud; so on and so forth. And increasingly, many projects add data migration paths from other projects, especially if they’re popular. Many ActivityPub servers can import Mastodon account data, for instance.
It does look pretty close to ideal for what we’ve been discussing; I need to install it and try it out, because so far all other options have failed in some way. There’s another forest of options in the blogging style, so I’m still optimistic, but I may try HumHub anyway.
Yeah, that was an interesting avenue; I suspect the user client experience will be where that fails for me. It can’t require any technical expertise.