#glitchsoc — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #glitchsoc, aggregated by home.social.
-
CW: Mentions and hashtags on Hubzilla are more "normal" in version 11.4, and this probably isn't pandering to Mastodon; CW: long (over 3,200 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, hashtag meta
I've noticed that Hubzilla 11.4 handles mentions and hashtags (closer to) the Twitter way instead of the Identi.ca way now. The@and the#became part of the link (@Jupiter's Fedi-Memes on (streams), #Hashtag, for example).
I wouldn't cry out "pandering to Mastodon" now. I don't think this happened in the same vein as Forte giving the choice between starting an enclosed conversation and starting a microblogging-style loose thread. After all, it's vanilla Mastodon out of all microblogging applications that handles the old Identi.ca way quite gracefully. And even what didn't work as intended didn't cause a big mess instead either.
Other Fediverse applications are way less prepared for this. From the Mastodon fork Glitch to all the *keys and, I think, the *omas, not only can't they handle the Identi.ca way, but they tend to fail rather ungracefully because they don't even expect anything else than the Twitter way. Especially on Misskey, this has been recognised as a bug in 2024 already, and nothing much has happened in terms of fixing it. Of course, all the Forkeys have inherited the bug, and I think none of them has fixed it instead of waiting for upstream Misskey to fix it. I'm not even sure if Iceshrimp.NET, a complete rewrite in C#, hasn't re-implemented it.
I mean, if lots of Fediverse server applications render Hubzilla's old "#Hashtag" (with the number sign outside the link, the Identi.ca way) as its Markdown representation, "#[Hashtag](https://hub.netzgemeinde.eu/search?tag=Hashtag)", and people keep complaining, then someone has to step in and put an end to this mess. And lots of fingers were pointing at Hubzilla. While tens of thousands of Mastodon accounts blocked Hubzilla channels for their long posts, hundreds of *key accounts blocked Hubzilla channels for how completely messed up their hashtags came out.
Also, unless I'm completely wrong, the first Fediverse server application that handled mentions and hashtags the Twitter way rather than the Identi.ca way wasn't Mastodon either; it was GNU social, itself a fork of StatusNet, the software that used to power Identi.ca before its switch to pump.io.
So this wasn't a case of Hubzilla acting up on Mastodon. It was a case of Hubzilla acting up across at least half the Fediverse, Mastodon actually largely excluded.
That is, it may still worry you that Hubzilla whose foundation was laid in May, 2012, based on Friendica which is another two years older, adapted to software which came later instead of playing the "we were here first" card. A whole lot of software which came later and which was largely created independently from Mastodon (although both Mastodon and Pleroma started their lives as something akin to alternative frontends for GNU social), but still.
By the way, don't Friendica, (streams) and Forte still cause the same issue? Especially Forte that has actually started pandering to Mastodon as of late?
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #GlitchSoc #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Friendica #Hubzilla #Streams #(streams) #Forte #Hubzilla11 #Hashtags #HashtagMeta #CWHashtagMeta #Mention #Mentions #MentionTag -
CW: Mentions and hashtags on Hubzilla are more "normal" in version 11.4, and this probably isn't pandering to Mastodon; CW: long (over 3,200 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, hashtag meta
I've noticed that Hubzilla 11.4 handles mentions and hashtags (closer to) the Twitter way instead of the Identi.ca way now. The@and the#became part of the link (@Jupiter's Fedi-Memes on (streams), #Hashtag, for example).
I wouldn't cry out "pandering to Mastodon" now. I don't think this happened in the same vein as Forte giving the choice between starting an enclosed conversation and starting a microblogging-style loose thread. After all, it's vanilla Mastodon out of all microblogging applications that handles the old Identi.ca way quite gracefully. And even what didn't work as intended didn't cause a big mess instead either.
Other Fediverse applications are way less prepared for this. From the Mastodon fork Glitch to all the *keys and, I think, the *omas, not only can't they handle the Identi.ca way, but they tend to fail rather ungracefully because they don't even expect anything else than the Twitter way. Especially on Misskey, this has been recognised as a bug in 2024 already, and nothing much has happened in terms of fixing it. Of course, all the Forkeys have inherited the bug, and I think none of them has fixed it instead of waiting for upstream Misskey to fix it. I'm not even sure if Iceshrimp.NET, a complete rewrite in C#, hasn't re-implemented it.
I mean, if lots of Fediverse server applications render Hubzilla's old "#Hashtag" (with the number sign outside the link, the Identi.ca way) as its Markdown representation, "#[Hashtag](https://hub.netzgemeinde.eu/search?tag=Hashtag)", and people keep complaining, then someone has to step in and put an end to this mess. And lots of fingers were pointing at Hubzilla. While tens of thousands of Mastodon accounts blocked Hubzilla channels for their long posts, hundreds of *key accounts blocked Hubzilla channels for how completely messed up their hashtags came out.
Also, unless I'm completely wrong, the first Fediverse server application that handled mentions and hashtags the Twitter way rather than the Identi.ca way wasn't Mastodon either; it was GNU social, itself a fork of StatusNet, the software that used to power Identi.ca before its switch to pump.io.
So this wasn't a case of Hubzilla acting up on Mastodon. It was a case of Hubzilla acting up across at least half the Fediverse, Mastodon actually largely excluded.
That is, it may still worry you that Hubzilla whose foundation was laid in May, 2012, based on Friendica which is another two years older, adapted to software which came later instead of playing the "we were here first" card. A whole lot of software which came later and which was largely created independently from Mastodon (although both Mastodon and Pleroma started their lives as something akin to alternative frontends for GNU social), but still.
By the way, don't Friendica, (streams) and Forte still cause the same issue? Especially Forte that has actually started pandering to Mastodon as of late?
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #GlitchSoc #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Friendica #Hubzilla #Streams #(streams) #Forte #Hubzilla11 #Hashtags #HashtagMeta #CWHashtagMeta #Mention #Mentions #MentionTag -
CW: Mentions and hashtags on Hubzilla are more "normal" in version 11.4, and this probably isn't pandering to Mastodon; CW: long (over 3,200 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, hashtag meta
I've noticed that Hubzilla 11.4 handles mentions and hashtags (closer to) the Twitter way instead of the Identi.ca way now. The@and the#became part of the link (@Jupiter's Fedi-Memes on (streams), #Hashtag, for example).
I wouldn't cry out "pandering to Mastodon" now. I don't think this happened in the same vein as Forte giving the choice between starting an enclosed conversation and starting a microblogging-style loose thread. After all, it's vanilla Mastodon out of all microblogging applications that handles the old Identi.ca way quite gracefully. And even what didn't work as intended didn't cause a big mess instead either.
Other Fediverse applications are way less prepared for this. From the Mastodon fork Glitch to all the *keys and, I think, the *omas, not only can't they handle the Identi.ca way, but they tend to fail rather ungracefully because they don't even expect anything else than the Twitter way. Especially on Misskey, this has been recognised as a bug in 2024 already, and nothing much has happened in terms of fixing it. Of course, all the Forkeys have inherited the bug, and I think none of them has fixed it instead of waiting for upstream Misskey to fix it. I'm not even sure if Iceshrimp.NET, a complete rewrite in C#, hasn't re-implemented it.
I mean, if lots of Fediverse server applications render Hubzilla's old "#Hashtag" (with the number sign outside the link, the Identi.ca way) as its Markdown representation, "#[Hashtag](https://hub.netzgemeinde.eu/search?tag=Hashtag)", and people keep complaining, then someone has to step in and put an end to this mess. And lots of fingers were pointing at Hubzilla. While tens of thousands of Mastodon accounts blocked Hubzilla channels for their long posts, hundreds of *key accounts blocked Hubzilla channels for how completely messed up their hashtags came out.
Also, unless I'm completely wrong, the first Fediverse server application that handled mentions and hashtags the Twitter way rather than the Identi.ca way wasn't Mastodon either; it was GNU social, itself a fork of StatusNet, the software that used to power Identi.ca before its switch to pump.io.
So this wasn't a case of Hubzilla acting up on Mastodon. It was a case of Hubzilla acting up across at least half the Fediverse, Mastodon actually largely excluded.
That is, it may still worry you that Hubzilla whose foundation was laid in May, 2012, based on Friendica which is another two years older, adapted to software which came later instead of playing the "we were here first" card. A whole lot of software which came later and which was largely created independently from Mastodon (although both Mastodon and Pleroma started their lives as something akin to alternative frontends for GNU social), but still.
By the way, don't Friendica, (streams) and Forte still cause the same issue? Especially Forte that has actually started pandering to Mastodon as of late?
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #GlitchSoc #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Friendica #Hubzilla #Streams #(streams) #Forte #Hubzilla11 #Hashtags #HashtagMeta #CWHashtagMeta #Mention #Mentions #MentionTag -
CW: Mentions and hashtags on Hubzilla are more "normal" in version 11.4, and this probably isn't pandering to Mastodon; CW: long (over 3,200 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, hashtag meta
I've noticed that Hubzilla 11.4 handles mentions and hashtags (closer to) the Twitter way instead of the Identi.ca way now. The@and the#became part of the link (@Jupiter's Fedi-Memes on (streams), #Hashtag, for example).
I wouldn't cry out "pandering to Mastodon" now. I don't think this happened in the same vein as Forte giving the choice between starting an enclosed conversation and starting a microblogging-style loose thread. After all, it's vanilla Mastodon out of all microblogging applications that handles the old Identi.ca way quite gracefully. And even what didn't work as intended didn't cause a big mess instead either.
Other Fediverse applications are way less prepared for this. From the Mastodon fork Glitch to all the *keys and, I think, the *omas, not only can't they handle the Identi.ca way, but they tend to fail rather ungracefully because they don't even expect anything else than the Twitter way. Especially on Misskey, this has been recognised as a bug in 2024 already, and nothing much has happened in terms of fixing it. Of course, all the Forkeys have inherited the bug, and I think none of them has fixed it instead of waiting for upstream Misskey to fix it. I'm not even sure if Iceshrimp.NET, a complete rewrite in C#, hasn't re-implemented it.
I mean, if lots of Fediverse server applications render Hubzilla's old "#Hashtag" (with the number sign outside the link, the Identi.ca way) as its Markdown representation, "#[Hashtag](https://hub.netzgemeinde.eu/search?tag=Hashtag)", and people keep complaining, then someone has to step in and put an end to this mess. And lots of fingers were pointing at Hubzilla. While tens of thousands of Mastodon accounts blocked Hubzilla channels for their long posts, hundreds of *key accounts blocked Hubzilla channels for how completely messed up their hashtags came out.
Also, unless I'm completely wrong, the first Fediverse server application that handled mentions and hashtags the Twitter way rather than the Identi.ca way wasn't Mastodon either; it was GNU social, itself a fork of StatusNet, the software that used to power Identi.ca before its switch to pump.io.
So this wasn't a case of Hubzilla acting up on Mastodon. It was a case of Hubzilla acting up across at least half the Fediverse, Mastodon actually largely excluded.
That is, it may still worry you that Hubzilla whose foundation was laid in May, 2012, based on Friendica which is another two years older, adapted to software which came later instead of playing the "we were here first" card. A whole lot of software which came later and which was largely created independently from Mastodon (although both Mastodon and Pleroma started their lives as something akin to alternative frontends for GNU social), but still.
By the way, don't Friendica, (streams) and Forte still cause the same issue? Especially Forte that has actually started pandering to Mastodon as of late?
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #GlitchSoc #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Friendica #Hubzilla #Streams #(streams) #Forte #Hubzilla11 #Hashtags #HashtagMeta #CWHashtagMeta #Mention #Mentions #MentionTag -
CW: Mentions and hashtags on Hubzilla are more "normal" in version 11.4, and this probably isn't pandering to Mastodon; CW: long (over 3,200 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, hashtag meta
I've noticed that Hubzilla 11.4 handles mentions and hashtags (closer to) the Twitter way instead of the Identi.ca way now. The@and the#became part of the link (@Jupiter's Fedi-Memes on (streams), #Hashtag, for example).
I wouldn't cry out "pandering to Mastodon" now. I don't think this happened in the same vein as Forte giving the choice between starting an enclosed conversation and starting a microblogging-style loose thread. After all, it's vanilla Mastodon out of all microblogging applications that handles the old Identi.ca way quite gracefully. And even what didn't work as intended didn't cause a big mess instead either.
Other Fediverse applications are way less prepared for this. From the Mastodon fork Glitch to all the *keys and, I think, the *omas, not only can't they handle the Identi.ca way, but they tend to fail rather ungracefully because they don't even expect anything else than the Twitter way. Especially on Misskey, this has been recognised as a bug in 2024 already, and nothing much has happened in terms of fixing it. Of course, all the Forkeys have inherited the bug, and I think none of them has fixed it instead of waiting for upstream Misskey to fix it. I'm not even sure if Iceshrimp.NET, a complete rewrite in C#, hasn't re-implemented it.
I mean, if lots of Fediverse server applications render Hubzilla's old "#Hashtag" (with the number sign outside the link, the Identi.ca way) as its Markdown representation, "#[Hashtag](https://hub.netzgemeinde.eu/search?tag=Hashtag)", and people keep complaining, then someone has to step in and put an end to this mess. And lots of fingers were pointing at Hubzilla. While tens of thousands of Mastodon accounts blocked Hubzilla channels for their long posts, hundreds of *key accounts blocked Hubzilla channels for how completely messed up their hashtags came out.
Also, unless I'm completely wrong, the first Fediverse server application that handled mentions and hashtags the Twitter way rather than the Identi.ca way wasn't Mastodon either; it was GNU social, itself a fork of StatusNet, the software that used to power Identi.ca before its switch to pump.io.
So this wasn't a case of Hubzilla acting up on Mastodon. It was a case of Hubzilla acting up across at least half the Fediverse, Mastodon actually largely excluded.
That is, it may still worry you that Hubzilla whose foundation was laid in May, 2012, based on Friendica which is another two years older, adapted to software which came later instead of playing the "we were here first" card. A whole lot of software which came later and which was largely created independently from Mastodon (although both Mastodon and Pleroma started their lives as something akin to alternative frontends for GNU social), but still.
By the way, don't Friendica, (streams) and Forte still cause the same issue? Especially Forte that has actually started pandering to Mastodon as of late?
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #GlitchSoc #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Friendica #Hubzilla #Streams #(streams) #Forte #Hubzilla11 #Hashtags #HashtagMeta #CWHashtagMeta #Mention #Mentions #MentionTag -
Salut #fediverse !
Me voilà de retour après quelques mois d'absence suite à un crash de mon instance perso (mise à jour de #Glitchsoc qui était vérolée... Arrgh).
Comme j'étais bien occupé, je n'avais pas pris le temps ni le soin de revenir...
La bonne nouvelle, c'est que, visiblement, #mastodon and co, ça ne rend pas accro et/ou dépendant•e !
Petit plaisir d'arriver et de tomber sur un post de @finnmyrstad qui nous partage une excellente illustration de l'enshittification ou emmerdification en good french !
Comme je ne l'ai pas trouvé ailleurs que sur Vimeo 🤮 , je l'ai déposé sur une instance Peertube.
https://video.liberta.vip/w/4ZrbKqU5UCBVhqQuAQZHLs
C'est vraiment excellent et cela mériterait d'être traduit dans tout plein de langue pour que le concept soit pleinement accessible au plus grand nombre.
J'ai récemment terminé un excellent bouquin « Les lumières sombres - Comprendre la pensée Néoréactionnaire » ** (sur les auteurs des #darkenlightment ) d'Arnaud Miranda** !
https://www.gallimard.fr/catalogue/les-lumieres-sombres/9782073140326
Juste après #Apocalypsenerds Nastasia Adjadi et d'Olivier Tesquet, ça donne de véritables clés de lecture des « logiques à l'oeuvre » (si si il y en a quand on sait ce que peuvent écrire des #CurtisYarvin et autre #NickLand notamment...)
C'est vraiment deux livres à lire pour les personnes qui sont ici et qui entendent tout la journée que #DonaldTrump est fou.
https://www.editionsdivergences.com/livre/apocalypse-nerds
Au plaisir, mais surtout au plaisir de se voir dans la rue, dans les luttes ! ✊✊✊
-
Happy I Love Free Software Day! 💕
Unfortunately, this year I could not join nor organize any in-person celebration, BUT of course I want to share my gratitude to the many, countless #FreeSoftware services I don’t merely use, but actually depend on.
Last year, I decided to focus only on #YunoHost, because it would have been crazy to list all the projects I use and I love.
This time, even if I will most certainly forget someone, I am challenging myself to mention all the #LibreSoftware my life is powered by.
Without further ado, THANK YOU to:
- @yunohost, for powering Nebuchadnezzar
- @fedora, for running my beloved #Framework laptop
- @frameworkcomputer, for designing and building repairable, #Linux-friendly and truly open hardware
- @gnome and @GTK, for being just gorgeous
- @calyxos (thus @LineageOS), for powering my #Fairphone5
- #Obtainium, for making me directly download apps on my phone, and @fdroidorg for distributing them
- #AuroraStore, for proxying the download of apps I am doomed to get from Google Play
- @element, for developing #Synapse, even though the new proprietary Synapse Pro is VERY PROBLEMATIC AND DISAPPOINTING
- #Fractal, for being the most beautiful and awesome #Matrix client ever
- @signalapp, for keeping me connected with the people I love
- @Mastodon, for also maintaining a feature-packed experimental fork (#GlitchSoc), that is what Pan runs
- #Tuba and #Moshidon, for being the most beautiful and awesome #Mastodon clients ever
- #Firefox, for still remaining the best possible #browser choice, despite #Mozilla’s governance messiness
- @openstreetmap, for allowing us to find the right path, both literally and metaphorically!
- @organicmaps, for being the simplest, cleanest, yet feature-rich #OSM client and navigation app
- @protonvpn, for making me browse safely from/to anywhere in the planet and @protonprivacy #ProtonMail, for hosting my email, despite the latest alarming political statements…
- @libreoffice, for allowing me to draft documents with ease, the last of which was my #CV
- #LanguageTool, for preventing me from making embarassing spelling mistakes
- @photoprism, for safely storing and indexing all my photographic memories, on Aby, and for providing stellar and friendly support too!
- #Actual, for moderating the very likely risk of ending up completely broke, since it forces me to manage my finances consciously and coherently
- @readeck, for storing and sorting ALL my varied and overwhelming inputs
- @nextcloud, for storing and synchronizing my data, for its #calendar, its #tasks, and all its awesome apps
- #Rustdesk, for preventing my friends and family members from going crazy, by allowing me to remotely connect to their devices and directly address the issues they have
- #Listmonk, for sending out my newsletter
- @eleventy, for powering all the websites I maintain, above all the virtual representation of my mind, and for being the only reason why I resist and try to continue learning #JavaScript
- @forgejo, for giving us a chance to truly control and collectively develop the sources of our software, but most importantly @Codeberg, for RESISTING, RESISTING, RESISTING, despite the hatred and attacks nazi assholes throw at them
- @musicbrainz for keeping music knowledge open and free, and @ListenBrainz for scrobbling the crazy music I listen to
- The @fsfe, for promoting this celebration and fighting the good fight!
Lastly, but most importantly, the biggest thank you goes to all the free software libraries and dependencies the above mentioned #software are made of/built with, including #C, #JavaScript, #Python, #Rust, and all community-maintained programming languages.
I am super sorry if I forgot someone!
#OpenSource #ILoveFS #SoftwareFreedom #Fairphone #Android #LineageOS #FSFE #OpenStreetMap #PhotoPrism #LibreOffice #Readeck #Eleventy #11ty #GNOME #Signal #forgejo #Codeberg #MusicBrainz #ListenBrainz #MetaBrainz
-
My list of ‘tested’ “general use” #fediverse instances per software:
(in no particular order)
* Hubzilla (with Account Portability / Nomadic Identity)
* https://zotum.net (with diaspora connection)
* https://node9.org (with diaspora connection)* Calckey (note: pending rebrand; a Misskey fork)
* https://calckey.social (flagship)* Mastodon
* https://c.im
* https://writing.exchange* Socialhome
* https://socialhome.network (with diaspora connection)* Glitch-soc (a Mastodon fork)
* https://aleph.land (my original Mastodon-software home 2017-04-05)* Misskey
* https://hashi.icu* Meisskey (a Misskey fork)
* https://meisskey.one (no Local / Social timelines)* Rebased (a Pleroma fork)
* https://c.wtf#SNS #MyceliumNetwork #SocialMedia #SocialNetwork #YourOnlyOne #Listicle #Listicles
#Hubzilla #Calckey #Mastodon #Socialhome #Glitchsoc #Misskey #Meisskey #Rebased #Pleroma