I’ve been using fediverse stuff (Mastodon and, most recently, Calckey – I’m just going to use “Mastodon” as shorthand here, purists can bite me) for over a year now, a…
I’ve been using fediverse stuff (Mastodon and, most recently, Calckey – I’m just going to use “Mastodon” as shorthand here, purists can bite me) for over a year now, a…
I agree with this. The first platform to get discoverability between servers right will likely lead the way. It doesn’t help that there’s a double @ system for both users and subreddit equivalents. I think eliminating the first @ for users and using a different character for topics would simplify the system. For example, a user could be [email protected] just as in email, and subreddit like forum could be /[email protected] (or #topic@dom.ain but I’m not a fan of this one).
#kbin has managed to pike my interest.
It’s far from perfect and missing many features, but it does looks promising.
The biggest drawback is the lack of mobile app yet. The mobile browser experience ain’t bad though.
Regarding the /[email protected] example, it looks so much better than the bunch of @s we have now!
But the # symbol is already used for tags (as your message shows). So it becomes difficult to differentiate between tags & topics. Especially with platforms that use either/both for different things. kbin is pretty unique because it offers both microblogging & link aggregation which adds an additional layer of complexity.
You could classify hashtags on other fediverse platforms as a sort of topic which one could subscribe to but how does that work with actual hashtags on kbin’s microblogging. I think these kinds of decisions wont be made by a bunch of smart heads sitting together or chatting across fediverses platforms but rather some random developer that happens to be working on the one platform to get its UX down pat & break the mold.