I thought this was about the Dino messenger, an open-source Jabber/XMPP messenger with E2E security (OMEMO or OpenPGP) [1]. [1] https://dino.im/. - Source: Hacker News / 9 months ago

Thanks for the reply, I'll definitely keep an eye on all that. > For a Slack competitor like Linen it would make more sense to use web UI because of the video calling/WebRTC stuff. I'm not even sure it matters so much, for instance there is this XMPP client that uses (lib)WebRTC for audio/video calls and has all of its UI build with Gtk (no web): https://dino.im/ > Proper GUI toolkits give you a lot of stuff out... - Source: Hacker News / 12 months ago

Dino is the GNOME client for XMPP. It was recently ported to GTK4 and Libadwaita. Source: over 1 year ago

If you want something that's more of a Slack/Discord alternative, gajim is receiving a lot of attention and polish lately, with Dino and Beagle as simpler alternatives. Source: over 1 year ago

I used Pidgin back in the day of AIM and ICQ, but nowadays, for XMPP, there’s Dino and Gajim for desktop and Conversations.im for Android. As far as I know, OTR has been superseded or replaced by OMEMO in most clients. Source: over 1 year ago

I have used Markdown before (https://dillinger.io/) so wouldn't have a problem with using it again as long as on page SEO isn't any extra effort. I am not sure how I would use Markdown and then add the content to the blog to be deployed and if that is going to be much harder than a headless CMS, I would go for the headless. Source: 7 months ago

Useful rescources for this are: Markdown Cheatsheet and Markdown Editor. - Source: dev.to / about 1 year ago

-put chatgpt output into dillinger.io and save as markdown file. Source: about 1 year ago

Did you try pasting the response in a Markdown editor and check if it's working? Here's one online - https://dillinger.io/. Source: about 1 year ago

Which works at https://dillinger.io/, but not https://insiders.vscode.dev. Source: about 1 year ago