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.
Dobrym podejściem są też web-aplikacje starające się integrować wiele profili z różnych serwisów. Np. #Phanpy, który ostatnio integruje #Mastodon i #Pixelfed (jego Media-firt UI jest świetne).
Innym tematem jest uparte trzymanie się przez Mastodona obsługi jedynie typu Note (i ułomne wyświetlanie Article). A ponieważ Mastodon dominuje w #Fedi, nie rozwija się (tak jak mogłoby) wsparcie dla innych typów treści #ActivityPub: image, video, audio, artist, album, track, playlist. De facto obrazki czy filmiki albo audio to po prostu załączniki do typu Note, bo Masto tak ma i nic innego nie wyświetli :/
Więc IMO pole do rozwoju jest ogromne, nie trzymajmy się kurczowo jednego konta (to wymysł marketingowców budujących silosy), zostańmy przy jeden login do wielu usług, jeśli już musimy ;)
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....
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?
FF really doesn't respect ppls donations. They are Goo-funded. Scamazon and Cloud(G)lare work through them too. A few years ago Mozilla snubbed bitcoin donations. Their priorities are clear.
Projects that seem to respect ppl and/or seem to need support/volunteers, include #I2P, #gNUSocial, FSF, #Parabola (gnulinux), #libreboot.at, ForgeFed, #OpenWRT, DeCloudflare.
In the beginning, there was Laconica, which later became known as StatusNet. A massive amount of the work that went into this is due to Evan Prodromou ( @evan ) , who is now spearheading an effort to standardize work on a communication protocol with the W3C Social Working Group.As a networking project, it was the first public implementation of the communication protocol known as OpenMicroBlogging, which later evolved into the OStatus protocol. These technologies provided a significant building block for future federated networking projects to study and reference.
In terms of how StatusNet was used, it resembled an early version of Twitter, with the added benefit of group functionality. What made it unique is that users on one Laconica server could communicate with users on completely different servers.
Aside from an error complaining that vendor/autoload.php is missing, I was getting this logging constantly when running docker compose up:
gnu-social-worker-1 | Fatal error: Uncaught LogicException: You need to add "symfony/framework-bundle" as a Composer dependency. in /var/www/social/bin/console:18
gnu-social-worker-1 | Stack trace:
gnu-social-worker-1 | #0 {main}
gnu-social-worker-1 | thrown in /var/www/social/bin/console on line 18
Aside from an error complaining that vendor/autoload.php is missing, I was getting this logging constantly when running docker compose up:
gnu-social-worker-1 | Fatal error: Uncaught LogicException: You need to add "symfony/framework-bundle" as a Composer dependency. in /var/www/social/bin/console:18
gnu-social-worker-1 | Stack trace:
gnu-social-worker-1 | #0 {main}
gnu-social-worker-1 | thrown in /var/www/social/bin/console on line 18
@mj
Ich war viele Jahre komplett ohne Social Media. Vor vielen Jahren hatte ich einen Facebook Account. Den habe ich irgendwann gelöscht weil der FB Algorithmus es schafft das schlechteste in mir zum Vorschein zu bringen. Vor einiger Zeit dann zu Twitter. Sobald klar war dass Musk übernimmt habe ich das Konto zur Löschung eingestellt. Seitdem Mastodon.
The next version of #Share2Fedi will add support for other Fediverse projects. I need to test it, but I don’t have any accounts to do it with. That’s where you come in:
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....