Haha, that's a throwback to the days when I helped to manage a phpBB board and there were a few members that would just continuously get into arguments so I edited the database so both of them had each other on their block list. It was very telling when I discovered they unblocked each other a few weeks later and got back to arguing and derailing thread topics.
777
joined 5 years ago
It is definitely slower than usual. It's not just you. The site is clearly under very heavy load.
I've been thinking about this joke for a while and don't feel I understand it. I expect there is a double meaning or a cultural saying that is lost on me, please can you explain it?
I like the Hacker News compromise - you have downvotes only after your account is a certain age and karma, and you can't downvote responses to your comments.
What a terrible day to have the ability to imagine that in vivid detail. What a cursed image, well done OP.
Yes, I loved that sub too, even though I have nothing to do with the food service industry it has been interesting reading about one of the more challenging and somewhat thankless market segments and the passion and camaraderie of those who work in it. I do hope that something equivalent is started here.
E-introverts represent, it has been a change really. I found that in Reddit, the sheer number of participants led me to only contribute meaningfully in smaller subreddits. I think I've made more comments today than in the last year on Reddit.
I think probably a pluggable storage backend is the best move. For example, any cloud hosted instance could use a native document storage format such as dynamodb, which is often quite cheap or free for small use-cases.
There is an android and iOS app available for Lemmy. Please see here: https://join-lemmy.org/apps/
Furthermore the mobile web app is quite nice too.
Precisely, the microblogging format really doesn't resonate with me. I don't feel I have anything necessarily good to announce to the world, but I enjoy a conversation or the invitation to share my own experience with something.
Apologies, this was meant to be in response to a comment concerned about Rust security. I’m still getting used to Mlem.
I expect it's accurate to say; their architecture is not like a database where you can add an index on a blocked state and then join against it. You have to get a list of potential posts that the user might want to see and then eliminate any in the block list. There will be a few edge case users who have thousands of block entries and a multithreading strategy is likely required to swiftly filter it in a reasonable timeframe.
However, an architecture I've seen that works around this is to build this timeline in the background and present it to the user from a cache, I don't know if this is what Twitter does as I never worked on that. However, if you want to not have a block feature but have some kind of mute feature anyway I don't see how there is a meaningful difference.