a better solution is to decouple the query from individual api requests by adding a caching layer. we’ll get there eventually

Just saying…

https://www.telegraph.co.uk/news/2017/09/08/florida-gun-owners-encouraged-shoot-storm-fire-guns-hurricane/

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.

[email protected]

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?

It’s not just you! sh.itjust.works is down.

Ah, ok. So if lemmy.world dies, but [email protected] 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?

I wonder about this as well – because communities are tied to a specific home instance, that instance going down affects that community, potentially killing it. Something more akin to hashtags/tags/labels wouldn’t be tied to an instance so they would be more robust, though you’d lose the moderation of a community and just have a firehose of posts/comments…

It’s called a single-point of failure in Engineering.

For that instance, yes. For the whole of Lemmy, no. Everything else keeps on chugging along.

yes, you can subscribe to any community that has been federated. search communities “all” or just go to [email protected]

Good stuff 👍 Right now you’re using “can” and “should” which are somewhat vague. What happens if bots don’t do something they should?

Consider clarifying requirements using the following RFC-style language: “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL”.

ref: https://www.rfc-editor.org/rfc/rfc2119