elk VS mastodon

This has lead to a delightful variety of custom clients like https://phanpy.social/ - https://elk.zone/ is another example that I really like.

It's the complete opposite of the Twitter API situation, where they locked their API down and killed the entire ecosystem of third-party clients.

And there are tons of third party clients. I think Tusky is the best one I’ve seen for Android, and there’s an interesting web-based one called Elk that’s very nice. You load up https://elk.zone and then use it as a front-end to sign in to your server.

The answer to that is https://elk.zone atm, a fun and chef's kiss interface (built with nuxt). You can insert elk.zone/ before any Mastodon url. https://phanpy.social is also great, with multi columns even for lists.

A browser plugin (like "Mastodon – Simplified Federation") to follow, favorite, etc. directly on any server has also improved my experience a lot.

Quick! Tell Obama and Taylor Swift about https://elk.zone! They're going to be so excited!

Also try logging in through https://elk.zone/ if you want to stick with the familiar twitter interface

For me, the boost/reply-numbers using https://elk.zone have been much more reliable than the original app. (It's also the (web)app that convinced me. Mastodon is the real deal.)

Try elk.zone. You can log into the UI with an account from any instance. I use it as my main UI and it looks pretty close to twitter, at least close enough for me.

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