Cool. It's actually still on my long to do list to try this. Thanks for the update!
I use one pod per app more or less. The reverse-proxy conf depends a bit on the specific app so that depends, but it will probably work for most by sharing a network and exposing the ports in the pods
Don't use the kube stuff. That's entirely seperate from Quadlets and some sort of Kubernetes compatibility.
If you can get someone else with a local account to open the community they can hand it over to your slrpnk.net account afterwards. Most of the many previous bugs around moderation functions have been fixed in 0.19.8/9.
However there are two main issues remaining:
-
You will rarely get any reports as those do not properly federate right now. A fix is supposedly in the works for the next Lemmy release, but this has been promised a few times with limited success.
-
If de-federated instances differ then you can end up with impossible to moderate situations. For example hexbear.net is blocked by slrpnk.net but it is not blocked by lemmy.dbzer0.com. This means people from that instance can post to the community, but these post are entirely invisible to you as a moderator with an account from slrpnk.net.
My recommendation is that you do not do remote moderation alone. At best you can help someone with an account on that remote instance to moderate a remote community.
I don’t believe that a report will federate to a remote instance that doesn’t meet one of those criteria, even if it hosts a moderator for the community, but I’m not certain about this one.
That's pretty much the issue with remote reports. In practical terms that means the vast majority of the reports are not delivered to the person moderating. For example I moderate /c/europe@feddit.org and I rarely get any reports from that community on my slrpnk.net account, and it is a popular community with lots of reports according to my co-moderator with a feddit.org account.
Apparently there is a fix in the works for Lemmy 0.20/1.0 but that release is still a while out according to the devs.
Generally speaking Trump is not getting into an alliance with Russia, but rather joins the "multipolar" club of imperialists that want to carve out their own sphere of influence without the others interfereing. China agrees with this but there are other reasons why the interests of the US and China still clash.
Woodpecker is more mature and I can control access better since I am not the only one using my Forgejo. But I think at some point the built in ones might reach feature parity.
Experimented with selfhosting a Woodpecker CI as a complement to my Forgejo.
Works quite nicely, I just need to set up a native ARM64 agent as the overhead of cross compilation on x86_64 is quite big.
XMPP also has a working ActivityPub bridge. But I think at some point these bridges are a bridge too far.
Software like Friendica or Hubzilla that can speak multiple protocols including AP are clearly part of the Fediverse, but things that need 3rd party bridges IMHO are not, as the creators clearly do no intend them to be part of it. Otherwise Xhitter would be also part of the Fediverse as bridges exist(ed in the past at least).
Igalia is currently working hard on making it easy to use Servo as an embeddable browser engine similar to how Chromium can be used.
The problems of doing that with Gecko, the browser engine that powers Firefox, is main reason why there are so few alternative browsers based on it.
Words have a meaning you know? "Discoverability" comes from "discover", which discribes an act of looking for something and not having something pushed into your field of view with minimal own effort.
view more: next ›
The Mastodon software seems to be in a kind of anti-sweetspot for this kind of hosting service. It kinda sucks that other better options have so much less name recognition that marketing becomes hard.