@stgiga Even #Mastodon is not the original #Fedi software. That title belongs to an extinct software that’s even older than #GNUSocial & #Hubzilla (which both are older than Mastodon). For more details on Fedi history, check this timeline compiled by @youronlyone/@youronlyone who corrected some of my own misconceptions & wrong thoughts about Fedi stuff.
Genocide apologist are safe and welcome at #mastodon dot social. This person has dedicated their time to harass, lie and libel the @palestine They keep spreading proven lies as the "beheaded babies" and "mass rapes" (there's zero evidence of either), yet Mastodon dot social mods don't do anything about this obvious troll, while they ban pro-Palestine accounts.
@trankten No se que podemos hacer ante eso, pero espero que si es cierto que se ha vendido a Meta le espero que le pase lo mismo que "hizo" el con #GNUsocial cuando dejo Ostatus y puso ActivityPub. El #fediverse como bien sabes es muy grande.
I've implemented basic support for meta groups (groups of groups). There's a lot of redundancy because of the federated nature of the azoriverse, with similar groups duplicated across multiple servers. Meta groups are a solution, by presenting users with a (somewhat transparent) single group that collects all of the posts....
There's something to terminology and design to ponder, I think.
@diogo of #GNUSocial submitted the #UnboundGroups#FEP before, that can be used to indicate an #ActivityPub Group is 'spread out'/supported on multiple instances:
If you haven't heard, sadly, #ChirpSocial, one of the popular #ActivityPub “groups” platform, is shutting down “probably” on February 29th.
In an email they sent to admins, the owner and developer can no longer support https://chirp.social financially as they failed to find a new job after they were laid off by #Google last year.
This reminds us the importance of having a built-in groups feature, and one where the groups feature actually federates.
Back in 2008, when the #Fediverse was born, we did have a built-in federated groups in #Laconica / #StatusNet (today known as #GNUsocial). We used bang (!) instead of at (@). A built-in groups feature is more stable as established instances can host them.
Today, we have #Friendica and #Hubzilla (as well as #Streams-based instances) to fill in that, as groups is a built-in feature in those software products. It's just a matter of finding an instance that's open to hosting groups for any topic for the ActivityPub protocol.
That said, any Friendica, Hubzilla, Streams-based instances you suggest for groups?
@smallcircles
To be fair, we get a sense that many instances are operated by those who are invested in highly questionable endeavours, which make them function similarly to a large corporation.
One of the goals of Fediverse proponents like us is to make setting up secure instances fairly easy, and not too burdensome. We think #Mastodon isn't able to provide such, but with #BloatFE and no javascript, maybe it can.
Getting to know the #gnusocial internals was fun. I managed to get composer autoloading (PSR-4), active orm and a cli pysch powered REPL. I think it would be easier to start from scratch than bring gnusocial into the modern php era.
meta groups
I've implemented basic support for meta groups (groups of groups). There's a lot of redundancy because of the federated nature of the azoriverse, with similar groups duplicated across multiple servers. Meta groups are a solution, by presenting users with a (somewhat transparent) single group that collects all of the posts....