#glitchsoc — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #glitchsoc, aggregated by home.social.
-
Warum ich Sharkey (Misskey Fork) empfehle
Hallo Fediverse
Vorab, ich rate nicht von anderen Micro-Blogs wie Mastodon, Akkoma, GoToSocial etc. ab. Es gibt viele tolle Micro-Blogs im Fediverse und alle haben ihre Vor- und Nachteile. Was macht jetzt Sharkey so besonders für mich? Ich hatte einige Jahre parallel ein Glitch-Soc- (Mastodon Fork) und ein Sharkey-Konto. Andere habe ich zwischendurch ebenfalls getestet, GTS, Friendica, Akkoma, Hubzilla und weitere, die mich letztlich jedoch nicht gänzlich überzeugt haben.
Sharkey läuft sehr schnell und flüssig und spart massiv Ressourcen (Letzteres wichtig für Instanzen). Es hat tolle Funktionen, die leider nicht mit allen Micro-Blogs kompatibel sind, jedoch interessanter werden, wenn mehr Menschen Sharkey nutzen: Chats, Gruppenchats, Kanäle etc. Es gibt zwar keine voll kompatiblen Clients, doch das braucht es glücklicherweise nicht, die Weboberfläche funktioniert sehr gut und sieht sehr schön aus. Zudem kann man das Aussehen selbst konfigurieren und individualisieren. Es gibt viele Markdown-Funktionen, um Beiträge schöner und interessanter zu gestalten.
Im eigenen Profil lassen sich Galerien, Seiten und weiteres erstellen.
Warum dieser Beitrag?
Wenn in den Medien von alternativen sozialen Netzwerken gesprochen wird, hört man in der Regel von Mastodon oder einfach Fediverse als Überbegriff. Sharkey wurde, meines Wissens nach, noch nie wirklich erwähnt. Meiner persönlichen Meinung nach sehr schade, da mir Sharkey mehr bietet als die anderen.
Wer also noch nie etwas von Sharkey gehört hat, schaut es euch einfach mal an, und wenn euch Leute nach Alternativen im Fediverse fragen, erwähnt doch auch mal Sharkey. :sharkey: :fediverse:
Danke für eure Aufmerksamkeit und habt einen schönen Samstagabend.
#sharkey #fediverse #microblog #mastodon #akkoma #gotosocial #glitchsoc #friendica #alternative -
🚨 BREAKING: This instance is now running Mastodon v4.7.0+glitch.
A huge upgrade. A beautiful upgrade. The servers are stronger, the database survived, Sidekiq is working, and federation is doing what federation does best: being gloriously complicated.
Some people said: “Maybe test it first.” We did. In production. Like adults with backups.
Anyone still running 4.6.6? Fake news. Loser Mastodon. Shut up.
-
Moin ihr Lieben auf https://lsbt.me ,
ich habe heute unsere Instanz auf glitchsoc-4.6.6 angehoben. Damit sind wir wieder uptodate.
Ganz viel Spaß!
LG Christin#lsbt #update #upgrade #glitchsoc #mastodon #instanz #instanzupgrade #instanzupdate
-
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 -
Is there a list out there of mastodon servers that include glitchsoc? Just curious..
Not sure why mastodon doesn’t just include markdown regardless…
-
🇩🇪 ┊ Announcement / Ankündigung
Die 3 Welten ( #AWiT #FEROX #Weindl ) haben heute Nacht auf #GlitchSoc migriert.
Neue Limits:
🔹 Bio: 161+0 Zeichen
🔹 Toot: 5k+161 ZeichenWarum? Weil wir können. Und weil 161 nicht verhandelbar ist.
━━━━━━━━━━━━━
🇬🇧 ┊ Announcement
All 3 of our worlds ( #AWiT #FEROX #Weindl ) just migrated to #GlitchSoc overnight.
New limits:
🔹 Bio: 161+0 characters
🔹 Toot: 5k+161 charactersWhy? Because we can. And because 161 is non-negotiable.
#Fediverse #Mastodon #GlitchSoc #SelfHosted #AdminLife #Infrastructure #AntiFascism #NoPlace4Fascism #OpenSource #DigitalSovereignty
-
@_elena Hello fellow #YunoHost person. Yes I love yunohost and serve #glitchsoc here as well as some other apps.
-
I think I'm going to play with followed hash tags on glitchsoc as I've never really given the mastodon / glitchsoc sites a chance until now. It will be a fun adventure I looking forward to. Let's go!
-
so, #Glitchsoc has something mastodon does not, in the main glitch website you get, you have a thread mode. I'm still learning how to use it. I will be researching how this works. This is a new fresh reinstall from when ever I got this one up and running, I think 2 weeks ago.
-
so, for those who want to know what happened and why I was offline for about 2 months here's the shortened version.
On April 13, I attempted to upgrade my #GlitchSoc instance. The upgrade itself appeared to complete, but restoring from the backup did not work. After that, the application was no longer functional even though the system itself was still mostly running.
Initial troubleshooting focused on configuration and basic recovery steps, however the issue turned out to be related to the runtime environment. The required Ruby setup was not in a working state, and some of the background services refused to start, preventing the application from starting correctly.
Over time, Multiple attempts were made to recover the instance, however the issue was not resolved. After a period of no progress, the focus shifted to stabilizing the system. System packages were updated, repository issues were corrected, and the server was brought back to a clean and consistent state.
Once the system was stable, GlitchSoc was reinstalled from scratch instead of attempting another restore. The reinstall completed successfully. This included rebuilding the required runtime environment via yunohost’s configuration when the app was chosen. The application is now running normally.
The previous backup was not restored due to compatibility concerns and the risk of reintroducing the same issue. Instead, The instance is being rebuilt gradually.
#Fediverse #Mastodon #SelfHosting -
so, I can't read the quote of my own post. I mean I can read my quote, however I cannot read the post being quoted. This by using the mastodon keys on the main mastodon / glitch site and hearing my statement then the status message that the post contains a quote. All that to say, maybe I'm missing something or misunderstanding how that is supposed to work.
#mastodon #Glitchsoc #Accessibility -
@fraser #glitchsoc lets you do that with a simple env var, also did that for this reason
-
Well cool! import of my second batch failed. I'm looking into siddkick. I've seen this before
#Mastodon #Glitchsoc -
@ivory any chance you have support for the #glitchsoc local-only post change planned?
The 👁️ was depreciated and no longer works.
-
I think this is the longest wait I've had to wait for a glitch-soc release after a mastodon release since I started my instance 😟
(No, I'm not really complaining. Claire has and deserves a life. But I'm still a little sad…)
-
Tough Mastodon #GlitchSoc upgrade to v4.6.0 this morning... The pre-deployment migration step got stuck here:
StandardError: An error has occurred, this and all later migrations canceled: (StandardError)
PG::DuplicateColumn: ERROR: column "avatar_description" of relation "accounts" already exists
/opt/mastodon/db/migrate/20260127141459_add_avatar_description_to_accounts.rb:5:in 'AddAvatarDescriptionToAccounts#change'(later followed by the same error on
AddHeaderDescriptionToAccounts)As any "good" sysadmin does, I blindly followed the LLMs instructions. It worked, I think?
After running
docker exec -it mastodondb psql -U postgres -d mastodon -c \and
"INSERT INTO schema_migrations (version) VALUES ('20260127141459');"
INSERT 0 1docker exec -it mastodondb psql -U postgres -d mastodon -c \, I was successfully able to do the prescribed migrations for upgrade...
"INSERT INTO schema_migrations (version) VALUES ('20260127141820');"
INSERT 0 1I feel gross.
-
v4.6.0-rc.2
WarningThis is a pre-release! This has not been as widely tested as regular releases, although it is still tested on mastodon.social and some other servers. If you update to this release, you will not be able to safely downgrade to the existing...
https://github.com/glitch-soc/mastodon/releases/tag/v4.6.0-rc.2
-
Today I had the issue of not being able to login to my fedisocial.de instance anymore, which is authenticating against LDAP. Yesterday I switched to #glitchsoc and apparently it's either an issue with glitchsoc itself or with thet new base of Mastodon v4.6 beta.
If you are running the latest glitch-soc/Mastodon on Rails 8 / Ruby 3+ and your LDAP login suddenly breaks with an Error 500, you are likely hitting a
FrozenError.The Issue: FrozenError (can't modify frozen Hash) in app/models/concerns/user/ldap_authenticable.rb:61The Cause: OpenSSL::SSL::SSLContext::DEFAULT_PARAMS is now frozen by default. The .tap block trying to inject verify_mode directly triggers the crash.
The Fix: Create a mutable copy using .dup before calling .tap on the parameters:rubytls_options: OpenSSL::SSL::SSLContext::DEFAULT_PARAMS.dup.tap { |options| options[:verify_mode] = OpenSSL::SSL::VERIFY_NONE if Devise.ldap_tls_no_verify },
Tested & works on my instance. Hope this saves someone a headache!
As I don't have any Github account anymore and there doesn't seem to be a mail address for bug reports... maybe a developer finds this...
-
An alle auf https://lsbt.me
Unsere Instanz ist auf der aktuellsten, stabilen Glitchsoc Version. Damit sind (unter Anderem) folgende kritische Sicherheitslücken behoben und geschlossen:
- Linked-Data Signature bypass through JSON-LD graph restructuring features
- SSRF protection bypass
Viel Spaß! 🙂
LG Christin
-
Endlich kann fedifreu.de auch übersetzen! Damit kann unser Mastodon-Server alles, was die vermeintlichen Flaggschiff-Instanzen können. Und dank #GlitchSoc kann er einiges mehr – und das auf stromsparender ARM-Hardware.
Um einen Account bei uns zu bekommen, müsst ihr nur eine Begründung formulieren. /c
-
RE: https://mastodon.social/@mastodon_releases/116607135436705422
Kita tunggu #glitch merge dan release container image nya.
-
@Sicherheit_ohne_Ueberwachung Danke!
Das Malprogramm ist ein #GlitchSoc-Feature, das sich wunderbar eignet, eigene Skritzeleien zu posten statt »KI«-Kitsch.
(Der Vorschlag kam von @b_rain bei einem Online-Treffen der Datenfreude-Gruppen.)
-
#TIL that if you're using #markdown in the #glitchsoc version of Mastodon, it doesn't render pretend 'tone' closing HTML tags, like
</snark>unless you escape them, see here for an example: .So if I've accidentally (and it was an accident I assure you) offended you today, my apologies, and please insert the right tone tag to make the toot more reasonable.
</laughingbutalsocrying>