I added a more flexible time-frame filter to lemmy that will come in 1.0.0 .
dessalines
I'm not sure how we could make this more clear either on https://join-lemmy.org/ , or the docs: https://join-lemmy.org/docs/index.html
https://join-lemmy.org/docs/users/02-media.html#torrents
Torrents should be used, as it entirely solves the static data distribution problem, and keeps servers from having to shoulder potentially enormous hosting costs.
I've even added a lot of torrent-support related features to lemmy-ui and jerboa, that will come in 1.0
This is correct. Torrents should be used.
How would two communities named news
, work for say, a server about star trek, and another located in a city.
Having distinct communities is a feature, not a bug. If two cities set up their own lemmy instances, say lemmy.sao_luis.br
, and lemmy.lagos.ng
, they can each have a news
community, without them overlapping.
Do a search for metroid, and subscribe to whichever ones you like.
Which tools specifically? I ask because this is a common complaint, but 99% of the time its something we already have, that most ppl are unaware of.
The key important one is being able to move posts to different communities.
Lemmy like all federated services, can't rewrite history, but you can already cross-post (although it would be the mod cross-posting, as we don't let mods alter user data except to remove it). It would just take someone adding that as an issue to lemmy-ui and working on it.
No seriously he's retired and cooks his brain watching fox news all day. If he got off that drug for even a month he'd return to being a sweet and caring person.
This is a serious problem, that we didn't anticipate during the first reddit migration wave. Since then, we added a join dialog to join-lemmy.org, and tried to make its join page sort by random, to spread out users more evenly.
Unfortunately, the people evangelizing lemmy on other platforms like reddit, continue to link specific popular servers, rather than join-lemmy.org or server pickers that sort by random. And people also tend to just link their own home server as a sign-up, instead of join-lemmy.org, so we'll likely continue to see centralization problems.
We're doing what we can to fight it, but other need to also.
I would love to see some community driven livestreams or events, where we could fund the developers ourselves through donations. We're all refugess from reddit, but that doesn't mean we have to be "libre reddit." I think we could easily fund ourselves if we fostered more of a connected sense of community through events and conversations, turn this group of websites into something more than just friendly social media.
@nutomic recently added Donation dialogs, which adds support for wikipedia-style banners (which are annoying, but they work). I think most of lemmy's problems could be solved if we were able to add a few more full time devs. We currently don't even have a single dev funded.
2nding @nutomic, that I'm really happy with the stack.
The one that seems really magical to me, is diesel. With it we get a compile-time-checked database, that's tightly integrated to the rust objects / code.
Every single join, select, insert, etc is checked before lemmy is even run, and it eliminates a whole category of errors resulting from mismaps.
Its made adding columns, and changing our data structures so much less error-prone than when I lived in the java-world.
Whenever we find that we'd want to do things differently, we usually do a refactor ASAP so as not to keep rolling spaghetti code. We've had to do this many times for the federation and DB code, and even have 2 major refactors that also add features ongoing. But luckily we've been able to stay in the rust eco-system for that.
As for UI, leptos didn't exist when I built lemmy-ui, so I went with a fast react-like alternative, inferno. Its showing its age now, so @sleepless1917 is working on lemmy-ui-leptos, which hopefully will supercede lemmy-ui.
It can't be transferred, but the posts / content will never vanish. Most importantly, it will stay searcheable.
The best option is just to create another community on a living server, and link to the local version of a dead one in a sidebar.