Hosting your own PDS would be like hosting your own email, but with the caveat that you can only access it through the Gmail interface and need to use the Gmail relay to communicate with others. In other words: completely pointless.
Admin on the slrpnk.net Lemmy instance.
He/Him or what ever you feel like.
XMPP: povoq@slrpnk.net
Avatar is an image of a baby octopus.
Hosting your own PDS would be like hosting your own email, but with the caveat that you can only access it through the Gmail interface and need to use the Gmail relay to communicate with others. In other words: completely pointless.
Mostly yes, but people were a bit naive back then and many onboarded friends and family onto the Gmail service and that burned some bridges and good-will as for Gmail users other xmpp users simply ended up as if offline and never responding.
This is not what really happend. Yes initially they added features other XMPP implementations had trouble to catch up with, but the main problem was them not implementing important security features like s2s TLS encryption, thus forcing others to cut them off. Google continued to run their xmpp servers for many years after, but they were so badly maintained and insecure no one wanted to interact with them anymore.
The rest of the xmpp ecosystem continued to grow at a slow pace and is alive and well, it was just an annoying set back going from being able to contact many millions of users on their Gmail linked xmpp accounts to not being able to do that anymore.
Technically true, but since this tool got widely adopted it does mean pretty much a full pipe of everything: https://lemmy-federate.com/instances
I agree, the all feed is commonly misunderstood to mean all of the Lemmyverse, but this is both a technical impossibility and also a false notion.
What the all feed actually means is all communities subscribed to by a member of your instance.
Especially on thematic, not too big, instances this can be quite interesting and definitely more useful that a bland feed of everything mixed together.
Obviously the bigger the instance, the more the all feed will tend to conform to a bland mix, and somewhat controversially a lot of instances are registered with a bot service that actively auto-subscribes each to other communities making the effect much worse.
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.
Last time I had a look at it the Lemmy package in Yunohost was severely outdated.
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.
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).
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.
Communities want more discoverability to get more members that post relevant things. This does the opposite and actively hides the specific community from potential posters while increasing the noise in the comments.
I think people really need to have some serious thought about the consequences of what they are asking for. These feeds, similar to algorithmic recommendations of commercial social media, increase engagement (a dubious metric, primarily interesting for advertisers) but not discoverability.
Odd, it doesn’t work here on our instance.
No, the problem is that people that have no relation to the community start commenting and getting into arguments.
Say for example a /c/anarchism gets added to a “politics” feed. And suddenly you have a bunch of people that have no clue (or even a pretty false idea) commenting on posts in the anarchism community because they think it is just another politics posts. Then others that are actual members of that community start getting into largely off-topic arguments with these commenters and when moderators step in you shortly after get complaints from people about being “censored for their totally valid opinion about politics” and so on.
First of all that’s all hypothetical and secondly that thought experiment only talks about an app that uses the PDS as an auth source and data storage. It does not talk about your PDS communicating with another PDS, for which AFAIK a relay is needed.