jrollans.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
I had a chicken-and-egg #admin problem last week: We have #Vodafone for DSL. They fscked up somewhere on their side, hours before I was about to leave for a short holiday. Instead of screaming into the void hours before leaving I didn‘t call support but waited if it was fixed when I‘m back and just rebooted the router.
It seems #Unifi #USG turns off #pppoe when it‘s not connected and on next reboot doesn‘t load the kernel module.
So Vodafone fixed the problem, but our router did not reconnect.
#SpamBot Alert for #Moderator / #Admin teams...
I'm seeing a bot making the rounds which leaves the message "1-Click to Freedom", with a promise to "Erase Up to $100K Debt Instantly" and an obviously fraudulent link. If you have an automated system, go ahead and set it flag that.
What kind of issues or concerns might I have if I shut down one kind of AP server software and then set up a different AP server on the domain previously occupied by the now decommissioned first AP server?
(I don’t think the soon-to-be-shutdown server has a self-destruct.)
How about no? You're way overstepping with this, poisoning the entire ActivityPub ecosystem. Let me break this down for you... In short: if you really intend to federate, respect your users and their data. Implementing federation while keeping these terms is a severe breach of trust, and would poison the entirety of the network in an way which will cripple ActivityPub, and undermine the very foundation of what AP stands for with regard to privacy, data ownership, and control over what we post to the network. Hopefully that's not your intention. Is it? RE:
I’ve once again started the process of installing and setting up Nextcloud on one of my servers. It occurs to me that my Nextcloud instances always die a slow death. Something about that piece of software, I think, sort of just falls apart over time. This time I’m attempting to future proof it a little bit more than the previous times, but honestly I fully expect it to go about the same as usual. Then again, historically I have installed all kinds of plugins (or apps) and was running it on fairly low powered hardware. Setting it up on some decently powerful hardware on this go around though. I’ll also try to be more conservative with the app installs as well.
I might actually set up two separate instances and federate them together. Perhaps if I maintain multiple servers they’ll survive a bit longer? Or I’ll just be creating twice the amount of tinkering and maintenance for myself.