First newsletter is out for October. Catch that over at There is work going towards showing those posts nicely on (already works but has some issues, thanks @bram!)

If you write roles and were looking for a tool to aid in writing role documentation, take a look at the brand new! It's still quite experimental and I'm certainly looking for feedback

people, I've packaged mailman3 over at I'd love some feedback if you take it for a test run (doesn't have a YunoHost rating "level" yet and only supports install/remove). Also see

For all the people, we just got a new release candidate out for , see - the new driver is included, so you can test your roles against live hetzner boxes and molecule takes care to bring them up and tear them down

More progress coming down the tubes over at Nowhere near anything usable or demoable yet 😅

If you've read and are considering running your own, check out

It's a project which aims to make self-hosting more accessible. All the major federated platforms are available to install via a friendly user interface.


Support is available over at


Finally: Alpine Linux, i3wm and a physical keyboard on a mobile phone. The keyboard may be a bit worn down, but the n900 is still going strong like it’s 2009 💖

last question:

if Pleroma were to use a different federation protocol for federating between Pleroma instances, which was very well documented, and supported real security features, and real nomadic identity (backed by a DHT + sharding), would you be willing to accept only interoperability with AP networks for cases where an activity is representable over AP?

@DashEquals I'll pretty much just be echoing a lot of the other replies lol.

Just because it's public doesn't mean it should stick around forever. There's a reason why the "right to be forgotten" has its own Wikipedia page. There's a specific section of Article 17 that pertains to this and it's officially called the "Right to erasure" and unofficially called the "right to be forgotten". It allows people to erase public information about themselves.

Personally, I consider and similar organisations a threat. It may have changed now (I'll know for sure when I hear back about my exclusion request) but, in the past, they would archive any site they came across without the owner's permission *even if* they disallowed it in their robots.txt. Yes, you can go through the trouble I have and block a list of IP addresses they own but robots.txt is supposed to be an understood standard. "If I don't want you accessing my site, I will put an exclusion here. Please respect that and don't." The fact that they ignore it, quite frankly, pisses me off and I regard them as a malicious entity because of it.

OSINT specialists love the Wayback Machine because they can look at a site and see historical information about it that the author may not be aware is public. Attackers use this all the time and it is dangerous.

If the Wayback Machine was opt-in and I could choose when snapshots were taken, I would be all for it. I would love to have a tool like that. As it is, it's not and I take preventative measures to block them.

I wasn't sure my tactics would actually work until I checked a few minutes ago. It's good to know they do.

I am not happy that they archived my old site

As well as my old Fosstodon account and GitHub page. I doubt they'll remove those but I'll see what I can do anyway.

Damn. No python implementation for the project yet and nothing officially planned due to lack of funding AFAICT. These new decentralisation projects are really lacking €€€

Show more

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!