The money thing is definitely an issue… when lemmy’s NLNet grant runs out, we will need to transition to a more sustainable model.
The best option for open source projects like this one to stay alive, is subscriptions (which we already have via liberapay and opencollective). I really like what tasks.org has to say about it:
I know you hate subscriptions. I don’t like them either.
Mobile apps must be maintained and supported forever, and one-time purchases are not an effective method of funding development¹. When one-time sales dry up then developers abandon the app. Subscriptions give them an incentive to keep you happy.
Thanks <3
For me at least, the burnout comes from the fact that I want to code, not troubleshoot. I want to make new features, build snazzy front ends, and not have to worry about money.
But as lemmy’s gotten more popular, a big chunk of my time is spent doing the things the article mentions: responding to an endless stream of notifications that builds faster than you can close them, helping debug people’s system setups, address people’s odd use-case pet features they want, and troubleshoot other issues.
Many times people can be very rude, not realizing they’re asking you to do free labor for them. Its very similar to how some people treat restaurant servers as their personal servants.
pictrs_1 | Error: Error in DB, Read corrupted data at file offset None backtrace ()
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | Read corrupted data at file offset None backtrace ()
Its a pictrs issue, not with lemmy. @asonix@lemmy.ml or ask in the pict-rs matrix channel.
Medium is even one of the ones explicitly called out here: https://idlewords.com/talks/website_obesity.htm
They managed to make displaying some text, a bloated javascript spyware mess.
I think its a good idea obvi. Its a collision between the microblogging / twitter-style that masto and pleroma employ(that have no title, only a body), vs the link-aggregator style (which has a title, and an optional body).
Both platforms should try to resolve the missing fields in whatever way possible, even if that means extrapolating bodies to titles and vice versa.
Federated communities do show up both on the search page, and the communities page.
This is a really good question.
For micro-blogging, the only one of those that’s internal to your service, is “boosts”. The equivalent for lemmy, would be cross-posts on communities you already follow, where the url field is either your local copy, or the federated link. Someone would x-post a link from another community, you’d see it, then subscribe to it.
A better answer to your question tho, would be a global community discovery service. Someone could either write one, and @nutomic@lemmy.ml has also written a lemmy-instance-crawler for join-lemmy.org to do the same. We could also potentially expand what join-lemmy.org shows, to list the most popular communities globally, and for each instance.
Since communities aren’t tagged, the only real way to look through them would be by popularity tho. But it would at least be a centralized place to see every known community on every known instance.
I’d thought we had another issue for this, but here’s one: https://github.com/LemmyNet/lemmy/issues/1026
IE making the community size affect the rank.
Its definitely limited, mainly in order to keep it small.
Another project I’d thought about, was essentially a semantic wiki of torrents, using their infohashes as keys, where people could contribute stuff like that openly to all existing torrents. And it could have semantic tags, so people could label the type of content, comment about it, add descriptions, etc. IE a TorrentWiki.
They removed it to pre-emptorily comply with German anti-piracy laws.
The project is https://torrents-csv.ml
I had the muvo!! I loved that thing.
Smartphones really did wipe out a ton of those single-function devices.