setsubyou

I've noticed it too...

It's normal that there is a delay between posting a comment & and it appearing on other instances, since federation happens in a separate queue. But I wonder if lemmy.world has simply become so big that sometimes the queue worker(s) can't keep up anymore and then it takes forever for comments to get through.

Ich habe Ende der 90er und Anfang der 2000er so viel Zeit in MUDs verbracht. Statt kommerzieller Onlinespiele hat man sich einfach mit anderen zusammen getan und selbst was aufgebaut.

Außerdem das Usenet. Bis in die frühen 2000er habe ich sogar einen eigenen Server betrieben. Das war auch schon prima funktionierende föderierte Kommunikation, nur Spambekämpfung war schwierig und daran ist es schließlich auch mehr oder weniger gestorben.

IRC auch so ein bissel, vor allem als mein Arbeitgeber noch die ganze interne Kommunikation unter den Entwicklern über IRC gemacht hat und es Teil vom Job war nebenher in ein oder zwei öffentlichen Kanälen unterwegs zu sein. Aber im Gegensatz zu MUDs und Usenet war das kein so richtig großer Teil meines Lebens.

There is an effort (https://forgefed.org) but I don't think there's anything usable yet.

You can find yourself on lemmy.world by entering the full URL to your profile into the search field, i.e. "https://kbin.social/u/HamSwagwich". This should yield this user page: https://lemmy.world/u/[email protected] (Since I'm reading this from lemmy.world I can click on your name below the post title to get to this page, too).

Something similar applies to magazines/communities. Instances don't know about all communities everywhere by default, so the first time someone tries to access a remote community, it has to be a search by URL (at least on the lemmy side), i.e. "https://kbin.social/m/TeslaMotors".

Now that I did that once, that community in particular will show up in a normal community search on lemmy.world too. But no existing posts have been imported (yet).

There's peertube and pixelfed.

お入りください is a more respectful way to say 入ってください, but it needs the お.

としたら expresses a hypothetical situation, like "if it were the case that (person) took of their shoes". The other one sounds strange too though, and 家に入り下さい is wrong.

Maybe something like 靴を脱いでから家に入ってください would work better?

Oh, that could be it! The user who created it added themselves on two other instances as mods too. I can't find anything in the modlog though.

I thought maybe they just deleted it, since they're pretty restrictive. E.g. they ban Japanese instances too because "they can't moderate it". But I can't find anything, and it's odd that it would show up as a foreign community if it was deleted.

⚠️ CAUTION
Dear customer, please make sure to read this.
⚫︎ The target audience of this product is 15 years of age and above. Never give this product to children below this age.
⚫︎ Those with sensitive skin (allergies, babies, etc.) should avoid using this product.
⚫︎ Don't put the bag over your head or face. There is danger of suffocation.

《Precautions for use》
⚫︎ Wash once before using.
⚫︎ Initially, some fluff may come off.
⚫︎ When washing, avoid using bleach. Colors may change.
⚫︎ Some fading may occur. Wash separately.
⚫︎ When left wet for a long time, there is danger of fading.
⚫︎ When using a tumble dryer, there is danger of shrinking.
⚫︎ Avoid ironing the printed parts. Color may transfer to other parts.

[Product Materials]
Product: 100% polyester

[Packaging Materials]
Plastic: Protective polypropylene

Sushi has its origins in a conservation method for fish from outside Japan. Originally, fish was fermented in rice and the rice was thrown away. At some point, Japanese people started shortening the fermentation period and ate the rice with the fish. And then in the Edo period they cut out the fermentation altogether and just added rice vinegar to the rice instead. But it's still slightly sour so it still fits!

I don't think you need an optimal spanning tree. Proxying messages is basically just how Usenet works. You peer with a small number of other servers each party forwards messages in groups the other party is interested in.

As someone who used to run a Usenet server (20 years ago), I don't think it's a better system. The extra hops add a lot of questions related to moderation, filtering, censorship, trust, responsibility for forwarded content, and so on.