Yeah, seems more like Insulate Britain disrupting M25 traffic, getting arrested, and drawing plenty of ire (and ridicule).
Yeah, my money’s on the Pleroma federation being the source as well. On my old domain, I ran an ActivityPub relay, subscribed to it and many others on that old Pleroma instance and, well, in addition to spamming the Fediverse (oops!), I completely drowned my instance in traffic; had to abandon the domain for this new one.
I’m a bit gun-shy of relays in particular, you might say. But I’m wondering whether not subscribing to an ActivityPub relays might mean that I’m regulated to some outer ring of the Fediverse. I haven’t found much in the way of documentation around this, tbh; been at the mercy of kindly instance admins learning most of what I know to date.
I don’t think my Pleroma instance is federating very well these days. :-( Sorry. Well, the song itself is on Spotify, I think.
Time to try to troubleshoot my instance again, I guess. (Without bringing the Niagara Falls of Fediverse traffic down on my head this time. RIP pleroma.nfld.uk.)
Edit: new link: https://nfld.uk/audio/CBCR3Track_2010-04-14.mp3
Actually, it’s my own personal Pleroma instance. Thought it was an interesting political song, and was just trying to find a sensible way to share it here with the commentary included.
Edit: @yogthos@lemmy.ml knows me! I’m not a spammer; honest! ;-)
Are you sure it is? :-)
Yeah, I was coming back to post a similar comment. Trying to self host these projects can be a nightmare, particularly if that’s your intro to Python or Node.js. I’m finally getting to a place where I can build more than half of what I attempt, and tools like venv and nvm have been crucial to that milestone.
Started with Red Hat, about 20 years ago (~6.x?). Tried OpenSUSE for a bit too, as I recall. Used KNOPPIX for a lot of stuff, back in the day. Ran OpenWrt for a few years too. Then Ubuntu from the early days – have pretty much always run that somewhere since. Mint is my main desktop, and has been for, oh, six years or so, I guess. Tried Puppy for a bit, to breathe life into my old netbook; switched to LXLE and am really happy. Just started running Xubuntu on an old desktop I found; workin’ great so far.
I’m enjoying DCGLUG: https://matrix.to/#/!kzbkknTCYXqxiTVvUw:matrix.org?via=matrix.org
As @Tomat0@lemmy.ml says, realistically, these are long-term goals. I know of a few Discord servers that have a channel or channels dedicated to Matrix bridging, but I’ve also had admins outright refuse my overtures.
To date, my biggest coup was bridging a 500 member Telegram group with a 200 member Matrix room on the same topic. The admin on the Matrix side was sympathetic, but the Telegram admin was skeptical. It took a solid month of negotiations, with plenty of space for them to consider things and think of new questions, either about Matrix and bridging generally, or the specific initiative I was posing, and the community on the Matrix side.
There’s also the infrastructure considerations. Moderation is a big concern, particularly with Telegram, or a Discord server of significant size and / or popularity. There can be concerns about the bridge being a conduit for spam, but, equally, proposing automated solutions that bridge, like Matrix’s Mjolnir, can be a selling point. I run my own homeserver and Mjolnir instances with this in mind. Similarly, I run my own appservices, to open up bridging possibilities to more obscure IRC networks, or to take advantage of newer features than are available on the older branches run by established services like the fab t2bot.io.
In summary, it’s the long game, and spending time getting to know any particular community is essential. They may be predisposed to the idea if you target specific topics, as Tomat0 suggested, but that’s no guarantee. In fact, it could easily swing the opposite way, where concerns about logging and search engine indexing could scupper the initiative. Ultimately, successful bridges are partnerships, the criteria for which are common across many subject areas, including those well beyond technology.