lemmy.world has the community, and is keeping up to date with it, because someone (me, actually) brought it through and subscribed.
midwest.social has the community, but won’t get further updates because no-one subscribed (so technically I don’t have the inbox address for it - it’ll be the same format as everyone else of course, but it would reject updates with the ‘community has no subscribers’ error if I sent stuff to it anyway).
justworks was in the same situation as midwest.social, but it has a subscriber now, so now it has everything and will keep up to date. I didn’t have to do anything - the new subscriber’s action re-fetched the outbox (discussed below) and luckily that contained everything that was missing. The post from infosec.exchange is there too, so that wasn’t affected by federation blocks.
lemmon.website isn’t running lemmy - the tails community is ‘virtual’ in that it’s just a bunch of static files pretending to be a real community. The main address 403s 'cos thats just a folder.
infosec.pub doesn’t have the community most likely because no-one who is logged in there has searched for it (instances won’t search outside their own database if the query isn’t from a logged-in user). lemmon.website is in their /instances list though, so there’s no blocking.
An outbox on lemmy contains the last 20 or so original Announces that the main community uses to tell the communities on other instances about a new post. To illustrate: curl --header 'accept: application/json'https://lemmy.world/c/microblogmemes/outbox | jq .orderedItems[0] would be for the most recent post on microblogmemes. (Op’s post is at orderedItems[6]).
Fetching this allows a new instance to re-create recent posts, as if it had received them at the time.
Someone clicked !tails@lemmon.website, but didn’t go further (they probably got lemmy’s misleading error screen and gave up). As with midwest.social - no subscribers = no more updates.
Yeah, lemmon.website is mine. Not running lemmy means I fudge things a bit (including having posts from Mastodon users, of course)
Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: !microblogmemes@lemmy.world
lemmy.world has the community, and is keeping up to date with it, because someone (me, actually) brought it through and subscribed.
midwest.social has the community, but won’t get further updates because no-one subscribed (so technically I don’t have the inbox address for it - it’ll be the same format as everyone else of course, but it would reject updates with the ‘community has no subscribers’ error if I sent stuff to it anyway).
justworks was in the same situation as midwest.social, but it has a subscriber now, so now it has everything and will keep up to date. I didn’t have to do anything - the new subscriber’s action re-fetched the outbox (discussed below) and luckily that contained everything that was missing. The post from infosec.exchange is there too, so that wasn’t affected by federation blocks.
lemmon.website isn’t running lemmy - the tails community is ‘virtual’ in that it’s just a bunch of static files pretending to be a real community. The main address 403s 'cos thats just a folder.
infosec.pub doesn’t have the community most likely because no-one who is logged in there has searched for it (instances won’t search outside their own database if the query isn’t from a logged-in user). lemmon.website is in their /instances list though, so there’s no blocking.
An outbox on lemmy contains the last 20 or so original Announces that the main community uses to tell the communities on other instances about a new post. To illustrate:
curl --header 'accept: application/json' https://lemmy.world/c/microblogmemes/outbox | jq .orderedItems[0]would be for the most recent post on microblogmemes. (Op’s post is at orderedItems[6]).Fetching this allows a new instance to re-create recent posts, as if it had received them at the time.
Someone clicked !tails@lemmon.website, but didn’t go further (they probably got lemmy’s misleading error screen and gave up). As with midwest.social - no subscribers = no more updates.
Yeah, lemmon.website is mine. Not running lemmy means I fudge things a bit (including having posts from Mastodon users, of course)
Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: !microblogmemes@lemmy.world
Oh did tails go down two weeks ago?
No, it’s still running. I just got out of the habit of adding posts. I didn’t realise it’d been 2 weeks. I’ll start it up again in a bit.
What are we paying you for?! 😉
Finally got around to reading this, awesome explanation! Keep up the good work!
I might be that subscriber from justworks BTW 😎