Hello,
Yesterday and last night, I installed a glitch-soc Mastodon instance on my server.
It wasn’t exactly a walk in the park, but I eventually got it done.
I took the opportunity to learn and to uncover a few flaws, if not bugs, in Dokploy.
Learning and Know-how#
I only deployed this tool to learn how to do it.
There, it’s done.
We don’t share the same vision of the digital world#
I have been puzzled by some of the design choices made in Mastodon for quite some time now.
When I set up my own instance, I tested a “personal” installation (without opening registrations to third parties).
Some might tell me this is logical, but I argue the opposite: in this mode, the tool does not offer to generate two separate accounts—one for administration and another for communication (the actual usage).
First of all, I find this contrary to basic user interface design principles. You don’t design an admin interface the same way you design a user interface. And, above all, you don’t mix the two—unlike what I observed here.
More importantly, it goes against all my rules and best practices regarding security. Regardless of the projects I work on, I always have at least two separate accounts with no bridge between them (see my articles on sudo 1, for example).
I avoid logging in with elevated privileges as much as possible, and I compartmentalize (I use Qubes OS, those who know will understand).
This is yet another item on my long list of things “I wouldn’t have done that way.”
Veni, vidi, abii#
Since I had the tool handy, I took the opportunity to browse around the Fediverse a bit.
This inspired the following reflection:
“I came, I saw, I left.” — Marc JESTIN
Best regards,
Marc JESTIN
https://marcjestin.fr