they already are
they already are
a better solution is to decouple the query from individual api requests by adding a caching layer. we’ll get there eventually
I’m trying an instance-specific link, it isn’t working.
if you click https://lemmy.world/comment/2024416 what do you see? i see nothing, just a blank page
this area is known as the Sahel, it contains some of the poorest countries in the world.
I love U 235
Lemmy has cleared some early hurdles to grow from near-zero to 60k DAUs in a month. I’ve enjoyed talking to people over the past month in a more friendly and intimate way than on that other site. The main communities are fun and viable but the niche ones are mostly empty. I run a niche hobby community and despite having a few hundred subscribers <5% have ever commented, <0.5% have posted. I think Lemmy needs to be perhaps 10x larger than it is now to be self-sustaining for niche communities.
Great instance review, thank you! FYI your markdown links are broken, switch the brackets, links are [like] (this) not (like)[this]
A lot of mobile apps don’t display community banners, and they’re how a lot of people interact with lemmy.
By which method are you determining status?
deleted by creator
Currently showing sh.itjust.works as 100% online. Are you sure about that?
Ah, ok. So if lemmy.world dies, but !somecommunity@lemmy.world was federated to 2 different other instances, those instances wouldn’t be able to “talk to each other”? They’d just have snapshots that they could locally interact with, but never see anything else? So is the fate of the Lemmyverse a graveyard of communities from dead instances?
meaning you could read my reply on a community that basically no longer exists
oh really? does it actually work this way? if lemmy.world dies, can all its communities continue to live on as long as there are lemmy instances out there federated and subscribed?
web interface indicates the shield is “speak as moderator”, i assume this is intended to highlight or distinguish a comment as a moderator speaking officially on behalf of the channel, as opposed to a normal comment with a moderator speaking for themselves personally. i can find API documentation and a github issue around this feature but can’t see any documentation yet