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.

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.

If Mozilla open sourced it years ago like they promised, it could be picked up by someone else.

Not really. There was a recent article that came out that said tumblr is still losing money. I don’t see them spending time and money on something that doesn’t have a direct monetization strategy, especially since their userbase isn’t actually asking for ActivityPub

Rereading my comment, it comes off a little brusque so I want to clarify a bit. I think user-defined multireddits are a good feature and could exist alongside my own proposal. Users having more control over their own feed is a good thing.

But my proposal has a different goal, which is to reduce duplication of links and keep conversation more centralized. It’s not a feature most users would even be aware of because it’s only manageable by community mods.

Community Grouping #3071 is an issue I created and it’s specifically not related to multis. Its purpose is to allows mods to unite their distinct communities into a logical community.

But #1 is predicated on #2. If developers are aware of the risk of EEE, then they won’t try to remain compatible with Meta extensions, which means development of the open AP ecosystem will continue at the same pace.

Yes I read that and explained why I don’t think its relevant. Facebook can’t slow down progress on the fediverse because:

1. progress is already slow. The fediverse has been in development for 15 years and still is a clunky, niche network and likely will always be less polished than large corporate networks.
2. Every developer on the fediverse is aware of the EEE playbook and next to none of them will try to remain compatible with any corporate extensions.

I’ve never really understood the EEE argument here. XMPP was an open proptocol, Google embraced it and attracted users, then extended it and took those users away. But according to this article, Google didn’t extinguish XMPP. It’s still around and serving its niche community.

That’s already the situation the fediverse is in. This is a niche community and there are already existing social media companies that the majority of internet users are on. If Facebook joins the fediverse, it brings billions of new users to the fediverse. If they then leave the fediverse, ActivityPub will still be here and all of us on the real fediverse will still be here, in a niche community. Everyone here has already chosen the fediverse despite it being a clunky, unpolished, niche network. How is EEE a relevant fear for the fediverse?

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.

This article seems needlessly antagonistic. Lemmy and kbin are new software (kbin has been live for about a month). Of course there are incompatibilities right now. Those will be worked out. Also, I’m not really sure which incompatibilities they’re talking about. Lemmy/Kbin posts show up and can be replied to on other fediverse services. you can even create a post in a lemmy community from a microblog acct.

A key thing to remember is that the entire fediverse is built by hobbyists. Gargron and mastodon did a bunch of marketing to get grants/donations but the rest of the fediverse is built by individual people in their free time. Fixing these issues will take much longer than a corporate network would take.

Sidenote: There is no primary fediverse application. I know they meant mastodon because its the most well known but that’s happenstance and bad journalism. Mastodon wasn’t the first fediverse application and I think lemmy/kbin will outgrow it soon.

Lemmy doesn’t federate hashtags so they’ll appear in the post on other fediverse services but they won’t appear in hashtag feeds/searches.

EDIT: FYI, there’s a cross-post button on lemmy. it’s the button that looks like a copy button (A square overlaid and offset over another square).

I should have checked the issue tracker before posting this. There’s already an issue related to community discovery at https://github.com/LemmyNet/lemmy/issues/2951

They abuse the subject field which I think lemmy ignores. name is a separate field that is used for the title

It’s not as common to push users to apps on desktop, but its a tried-and-true practice on mobile. I’m sure companies would do it if they could, but app stores and app lockin aren’t as strong on desktop as on mobile

Users can block those with extensions so the data isn’t as reliable

A lot of kbin users are coming from reddit and don’t care about its additional (microblogging) features. Using a Lemmy-API powered app would give them exactly the experience they’re looking for. And there’s nothing stopping these Lemmy-API apps from adding support for the kbin extended api.

Fedilab is an app that was originally built for Mastodon and uses the mastoapi but also supports some Pleroma specific features. Apps don’t need to be directly one-to-one tied to services.

The lead dev of kbin has said he’s evaluating implementing the API.

kbin has a totally different backend and also additional functionality that is not available in Lemmy apps.

This doesn’t make it less likely. They can implement the lemmy api for compatible features and add their own api (or more likely use the masto-api) for the other features.