#glitchsoc — Public Fediverse posts

@_elena Hello fellow #YunoHost person. Yes I love yunohost and serve #glitchsoc here as well as some other apps.

:boost_ok: We'd like to move to fosstodon.org (or any other #FLOSS-centric Instance; preferably with #GlitchSoc support for #MarkDown)…

- Anyone willing to do a recommendation / offer an invite?

#OS1337 #Fediverse #Migration #PleaseBoost

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!

#mastodon #glitchsoc #fediverse

I switched my instance to glitch-soc.

It now supports:

• Markdown formatting
• Longer posts (5000 chars)

Docs: https://glitch-soc.github.io/docs

#GlitchSoc #Mastodon #Fediverse

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…)

#mastoadmin #glitchsoc

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 \
"INSERT INTO schema_migrations (version) VALUES ('20260127141459');"
INSERT 0 1 and docker exec -it mastodondb psql -U postgres -d mastodon -c \
"INSERT INTO schema_migrations (version) VALUES ('20260127141820');"
INSERT 0 1, I was successfully able to do the prescribed migrations for upgrade...

I 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

#glitchsoc #glitch #mastodon #mastoadmin

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...

#glitch #mastoadmin

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

#upgrade #update #mastodon #glitchsoc #ssrf #jsonld #lsbt

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.

#mastodon #glitchsoc

@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>

#Mastodon #GlitchSoc #UI #UX #FAIL #Firefox

А вот эта хуйня (в многоколоночном режиме) мне совсем-совсем не по нраву! 😡

New by me: Catppuccin Complete UI for Mastodon Now Supports GlitchSoc

https://www.kylereddoch.me/blog/catppuccin-complete-ui-for-mastodon-now-supports-glitchsoc/

#Mastodon #Catppuccin #GlitchSoc #OpenSource #Projects

Instance was having issues this morning. It started throwing up ‘500’ errors all over the place. Reboot fixed it for a spell and then it would happen again. No idea why.

I stepped back to a backup from a couple days ago and everything appears to be working now.

Posts I made between then and now will be lost like tears in the rain, bit really it’s no big loss. 🙂

#SelfHost #SelfHosting #GlitchSoc

@Katika @ctt @Datenpunks

Ich freue mich auf deinen Besuch in #Bielefeld!

Und was für eine wunderbare Zeichnung! Neulich bei einem Vernetzungstreffen der https://datenfreu.de schlug @b_rain vor, mehr selbstgemachte Krakeleien zu verbreiten als Protest gegen den »KI«-Kitsch. Da fiel mir ein, dass die auf https://fedifreu.de laufende Mastodon-Variante #GlitchSoc ein kleines Malprogramm dabei hat. Ich werde versuchen, in Zukunft mehr Tröts damit zu verzieren.

#aislop #kikitsch

This is so weird I tried setting up #GlitchSoc on #Yunohost and it worked but I couldn't log in correctly.