I use TiddlyWiki via TiddlyPWA. It’s an offline-capable PWA with builtin sync and encryption. It doesn’t have folders but it does have nestable tags. I don’t think it supports markdown out of the box, but I’m positive you can find a plugin to use markdown. Plugins are crazy easy to install in TiddlyWiki; you just drag and drop the plugin into your wiki window and confirm the installation.
TiddlyWiki via TiddlyPWA is what I use. I don’t know if it supports the S Pen and the notes are all saved in a single HTML file.
but it’s the one many first-time Fediverse users coming across from Twitter end up on.
That’s because it’s the only one ppl will mention as an alternative. Stop telling ppl to try mastodon, tell them to try firefish or akkoma.
Also, the jump effect is way overstated. Some users do end up moving to other software, but many more just leave because they don’t like mastodon.
Entirely unmoderated tags are not an option for lemmy as the moderation workload would be too much. Additionally users being able to type out tags themselves introduces splintering in the tag contents due to typos. A better solution is a curated list of tags users can attach to their posts
I vehemently disagree with the main idea behind this RFC. Just let users put arbitrary tags on their posts and other users can search for whatever tags they want. The rest of the fediverse has unmoderated hashtags and it works fine. I don’t see a good reason hashtags should require moderation. And typos can be corrected by editing the post.
Adding those restrictions just makes this feature more complex than it needs to be and reduces compatibility with the fediverse. Users of any fediverse software can create a post in a lemmy community and those posts may have arbitrary tags. Why should lemmy users have less capability on lemmy than external users?
Finally, hashtags could be a useful way to filter posts within a community if these restrictions are dropped. I posted this in the github thread, but imagine a general programming community. Posts could be tagged with a language, paradigm (OOP, functional, etc), or whatever else to allow users to browse subtopics within a community. Having to request moderators add a tag is an unnecessary extra step.
This is exciting. I think code forges are one of the biggest opportunities for ActivityPub to really go mainstream and change the internet. Not only because it’ll make working with open source way easier since you can work with any compatible forge, but developers will be more exposed to ActivityPub just by working with the software and so more likely to participate in AP dev. It will be interesting to see what effect this has on the fediverse. There’s been a lot of talk from various organizations/companies but this will be the first large project adopting AP. I’m interested to see how development goes for them and for other fediverse projects.
I wonder what changes it will force on Mastodon. Masto won’t be the biggest project anymore and won’t be able to throw its weight around as much. Just like the recent influx of users forced the implementation of full text search and has reenergized conversations about quote posts, I think federated gitlab would force masto to rethink some things.
The numbers for lemmy are probably way outdated. Take a look at https://lemmyverse.net/communities. It lists 636 instances but FediDB only has 302. And remember most of this growth has only come in the past week or two.
Also, mastodon only has 1.25 million active users according to FediDB, though that’s probably outdated too.
nodebb and discourse are working on activitypub support. See https://crag.social/@devnull/111732273308478221