Sounds great! I would definitely welcome it @amenthes, any thoughts on this?
Any help is appreciated! Go right ahead!
If there is anything you need, feel free to reach out to me
Any specific instance you want the account on? I do have my own at masto.nixnet.xyz but I’m fine with wherever if you’d prefer a different one!
I’m wouldn’t recommend to use an instance where you already have an account (as this maybe becomes annoying with switching accounts all the time), so maybe fosstodon?
Not a really strong preference, I could also imagine things like floss.social or mastodon.technology. But I also don’t mind when you decide to go for your own instance As I said, my main concern would be the account switching required to manage it
Unless you’ve got anything against it, how about social.snopyta.org? I’m looking for one that isn’t run by Masto.host or behind Cloudflare. Plus the admin’s a friend of mine
As long as we can make sure we don’t have to move every view weeks because some smaller instance died, we should be fine, so sure, go ahead
Even when I have to say that some statements in their terms are funny. Like the child usage policy ^^
I can vouch for his stability and infra. Being part of the librehosters, we both have to have bus factor strategies in case something happens to one of us and ours is to give the other root access. He’s got a massive server, everything runs in its own dedicated container, and he does automated backups daily.
I’ve created the account and done some preliminary icons and such. What do you think?
I added the link here before I edited the account so the preview won’t show it lol.
I like it a lot! Looks great, now all that is missing is content I guess we can solve this problem ^^
Any topics we should/want to tackle on your side?
We could do like a daily series of tips to using CodiMD. For example, I just found out how amazing slide mode is and will be using it to present at SouthEast LinuxFest next month. One toot could be something like:
Did you know #CodiMD has a slide mode? You can use it to create complex presentations just with Markdown and a few lines of YAML!
<link to an example>
<screenshot of the overview with multiple branches>
And so on. The account could also be used to announce new releases, talk about contributors/community members, etc.
How is this?
Nice! I like this first toot, time to make the account a bit more official!
I’m a bit worried that when we go for “daily tips and tricks” we’ll run into issues of having no more content after the first 3 weeks. But on the other hand, things are moving forward and for the first 3 weeks it can only help to grow the account, so let’s go for it. We might want to setup a pad with drafts.
So let’s go
I think in 1.4.0 we could add a link to the Mastodon account in the footer.
In order to make sure we never end up with a dead link, I’ll create a redirect as we already did for translations and similar things, as this gives us control over the namespace
How about https://social.codimd.org/mastodon?
That’s exactly what I was thinking as well. Doing it every other day would help.
That is a wonderful idea and I like the link!
We could start a CodiMD pad with all tipps and check off those that were already posted. If the list is very long, I don’t see a problem with daily tipps. If the list gets shorter, we can always switch to longer intervals.
I would suggest to add a hashtag to those tips. In case anyone wants to mute daily tips to just receive release notifications and low-volume info, they should be able to do so as well.
Also: I really like the way https://mastodon.social/@climagic handle their account. They sometimes do reruns of basic tips for newcomers. (I also their frequency of tweets/toots).
Started a document to collect some old toots of mine, that could be re-used (with some updates).
Feel free to extend, improve and modify
It might be cool to put user feedback somewhere on a site or page like the “testimonials” you see other projects do. For example, these are some good ones I’ve seen so far:
In English (translated by DeepL), the last one is:
It’s really great software. Especially the presentation feature is great. And in the Fediverse they are also still.
I guess “getting a website” is one of the next big things. But let’s grow healthy in an appropriated way for our project
Right now, we just redirect https://CodiMD.org to our GitHub repository.
another thing I’d like to propose is: featuring parts of CodiMD. We rely on a ton of dependencies, most notably perhaps CodeMirror. So anything that improves them will also improve CodiMD.
So tweets in the form of
Did you know that CodiMD uses CodeMirror? We use it to give you a full-fledged code-editor. If you would like to know more, find them at …
Internally, CodiMD relies on Sequelize. This is what stores your Notes in a PostgreSQL database. To learn more about this, go to …
CodiMD uses ForkAwesome, which gives you a ton of icons within CodiMD. Something is missing? Propose it here: https://forkaweso.me/Fork-Awesome/community/#requesting-new-icons
and so on. It’s a little bit similar to Follow-Friday. Perhaps
What do you think in general? Its this something we should do?