86
we need more users
(discuss.tchncs.de)
I've been one of the people saying "we don't need more users. we need quality over quantity" and i was wrong.
the way it's going, lemmy needs active users who post content sothat the network stays relevant. networks like the fediverse benefit from network effects and that means that if we have more users, that improves the value and quality of the fediverse overall.
So please, everyone, when you can, make advertisement for the fediverse in your personal area. Go talk to friends, make attractive stickers and put them everywhere, stuff like that. We would all benefit from it.
edit: source for the graph
Let's stop working on "Lemmy app" , "mbin app", "PieFed app", "Mastodon app" and just embrace ActivityPub as the single API.
There is a difference between Mastodon and Lemmy because Mastodon is user-centric and Lemmy is content-centric. I wrote about this here
phone apps can't use activity pub as that's a server protocol so if you want a good mobile interface you generally speaking need a rest-y api that an application can query. yes, lemmy and piefed both feature PWA frontends that can be installed to your homescreen, however on older phones this can be an extremely suboptimal experience as PWAs tend to require more RAM than native apps.
You don't need to get rid of the server. All I'm saying is that we can have a server that uses the ActivityPub API directly instead of these ad-hoc APIs for each different use case.
i don't understand how that negates the utility of a mobile app that presents this information. also i'm not saying to get rid of the server-client paradigm, not sure what you're talking about
I think that would just increase the fragmentation LOL. It's like that XKCD comic
It's the complete opposite of that.
"Use ActivityPub directly for interacting with the social web graph" is the same as saying "Use HTTP and HTML directly to interact with the world wide web".
The reason we don't see different websites using different versions of HTTP, or that someone can open a HTML document on pretty much website and read its contents is because we are building the application on top of the protocol layer.
But ActivityPud is very barebones so you will need to implement a lot of features. In doing so you are effectively creating a new Lemmy.
Indeed, I am. But to be perfectly honest, I'm doing a lot less work that I original thought in the server side, and when I get to start working on Mastodon compatibility, I will probably just change the internal implementation of mastodon's js sdk.
Right but you understand how this makes fragmentation worse right?