mastodon VS sydent

I'm the admin of a small server, which I set up a few months ago with the one-click install and then migrated to glitch-soc (https://glitch-soc.github.io/docs/). Recently I tried updating it to the new version of glitch-soc due to recent security updates. However I seem to have broken my server.

I imagine it might turn out to be something similar to https://glitch-soc.github.io/docs/

Have a look at glitch - a fork of Mastodon that looks and feels and behaves mostly just like mastodon but has Markdown support.

A good start to see Mastodons upstream finally implement features considered so necessary that they existed in a fork for years beforehand[0].

I'm not trying to sound cynical, this is legit a good change. Other fedi implementations have supported different message formatting (mainly markdown) for ages and that shit still degrading away to plaintext on Mastodon is extremely aggravating if you decide to (for example) use a bulletpoint list.

[0]: https://glitch-soc.github.io/docs/

You don't have to maintain a soft fork; Glitch-soc is a "friendly fork" which shares maintainers with upstream and has lots of great features, including a configurable post length limit.

What the fuck is your problem? Why do you some here just to see? Are you so fucking retarded that you don't think this issue have been brought up before? Do you think I'm just making up this on the spot? https://github.com/glitch-soc/mastodon/pull/1502 https://github.com/GlitchCatFedi/Policy/blob/main/Global%20Fulltext%20Search.markdown

Can we expect to see any of the https://glitch-soc.github.io/docs/ features coming to Mastodon mainline soon? Post formatting? Highlighting of misleading links? or local only posting?

Mastodon Glitch Edition

So this one is a fork, and infosec.exchange is a fork (https://github.com/glitch-soc/mastodon); are the mastodon committers opposed to incorporating those changes, or this fork situation is "as it should be" while these experiments run their course?

I'm all for experimentation, but since "the exodus" I've become acutely aware of how many instances are out there advertising their version number, so the first big rails (or mastodon itself) vuln is going to be some ooooonooooz

GitHub Discussions can also be a great place for support as long as these are regularly monitored. Another option along the same lines is Discourse and the Open Source Matrix which is used by quite a few Open Source and community-based projects.

Tangential: the article notes that Telegram is an “encrypted messaging app”. While this is technically true, it's worth keeping in mind that it's not end-to-end encrypted, so it's less secure in that regard than, say, Signal or even WhatsApp. Telegram does have opt-in end-to-end encrypted one-on-one chats, but those are very inconvenient to use.

For a properly encrypted chat app, including group chats (opt-in), try Matrix instead: https://matrix.org/

I'd love something like the Matrix [0] data model (JSON messages aggregated in an eventually-consistent chatroom CRDT) transmitted over something like simplex for metadata resistance.

[0] https://matrix.org

Trillian mod here. There's this new thing called Beeper, works on matrix.org. It's not as the good old times, but I'm currently using whatsapp, FB messenger, discord, telegram, signal, imessage and a few more. It's not Cerulean experience, but it's... slowly improving.

I'm trying to change my account provider from "matrix.org" to whatever Element One needs, and for the life of me I just don't understand what values I have to put where to be able to log in. I tried `element.io`, which takes me to sso.element.io but this doesn't seem like the right thing (no credentials work as I expect.