Quick vibe check on @elk usage.

[piebob@metasocial.com]

@ayo @elk i used elk for over a year but switched to phanpy about 6 months ago and imo it's much nicer and is updated more frequently.

[ecstrema@mas.to]

@ayo @elk I use it everyday. It does everything, is clean, installable as a PWA, very responsive. Never had any issues with it, and find it significantly more nice to the eyes than the default client,

[Guest]

@ayo @elk I love Elk and it’s the only Mastodon client I can stand looking at, day in, day out 🥲

[ghosttie@mastodon.gamedev.place]

@ayo @codinghorror @elk is there a page somewhere that says what the differences are?

[dirk@gts.0x7be.net]

@ivory @claudinec @ayo @elk I hope for that since I started using Elk some years ago. It absolutely needs a toggle between rendered and raw Markdown.

Elk trying to be smart sometimes hinders me writing messages how I want them to be.

[ivory@tapbots.social]

@dirk We don't support writing markdown yet as that isn't a feature of Mastodon yet. As soon as the API allows for it, we will add it. For now it's read only as it is in Mastodon.

[wcbdata@vis.social]

@ayo @elk Looks like a Mastodon client with built in AI? No thanks.

[crocodisle@woof.tech]

@ayo @elk I tried web app a few times and I like it, but it's a bit out of the way and I only feel as excited to use it as I do towards the default mastodon interface.

Having more features to enhance the masto experience sounds cool, but I also worry about drifting too far into specialized-UI land that it could end up making the default interface feel too clunky to use by comparison. Since I don't have too many complaints about the default interface, I don't feel too pressured to change rn.

I do think Elk is neat though!

[ifilipau@mas.to]

@ayo @elk

IIRC there were features missing + rough edges "paper cuts".

I used Elk because it worked best for doom-scrolling the trending. Not without bugs, but better than rest of mastodon clients. But then one update broke the doom-scrolling. So... Elk is just too unfinished. It needs a decent amount of systematic UX polishing.

[mcdanlj@social.makerforums.info]

@ayo @elk Elk is my primary client. It's definitely my favorite and the experience is generally much better than the default client, or in general all the other clients that feel the need to wrap everything up in boxes inside boxes on virtual "cards". Phanpy is the only one that makes that work at all, in my opinion (though I don't like the boost carousels; personal preference), and for every other client I know, the UIs look like they are a few decades old.

Two flies in the ointment for me, though...

Editing glitch+soc formatted posts in Elk generally kills formatting, which forces me back to the default UI. The built-in formatting doesn't know about bullet lists and keeps turning them into italics, which is frustrating.

The experience is getting worse running Elk main on mobile Firefox (Android), to the point that I'm struggling. I have to assume that no Elk devs are using mobile Firefox as a daily driver.

[chrismessina@mastodon.xyz]

@ayo @elk I would like to use it again if it were under (more-) active development!

[hanajima_saki@mstdn.party]

@ayo @elk 我经常使用Elk客户端，我主要在电脑浏览器上使用，它的中文翻译很完善，我可以基于以前在小蓝鸟的习惯使用Mastodon这样的SNS社交网络。看起来许多人没有用过这个客户端。
另外，Elk客户端中文翻译的「鹿鸣」是一个很有意思的译名，其字面意思可以看作为「鹿的声音」

[codinghorror@infosec.exchange]

@ayo @elk let me start by donating to your work. Show me how to do that.

[ayo@social.ayco.io]

@codinghorror @elk Thank you!

The team has an open collective: https://opencollective.com/elk

It is also possible via GitHub sponsors: https://github.com/sponsors/elk-zone

[ayo@social.ayco.io]

@wcbdata @elk Elk doesn't have AI, but there was a contribution to use AI translations if that exists on your browser. So the choice is on the users hands, whether they use a browser with this capability.

[codinghorror@infosec.exchange]

@ayo done

[ayo@social.ayco.io]

@codinghorror Thank you so much! This will go a long way

[i@toot.pouyan.net]

@ayo @elk I wanted to try it with my #akkoma instance, but got a "missing authentication code". Didn't debug further though. Is this a known issue?