On both you have to search for a magazine handle (magazine@instance.tld) if the magazine is not yet on the server. And not the magazine search but the regular search. It can of course be blocked by the instance, but most likely just nobody searched for it before.
Most mbin instances are very small and even fedia only has like 4000 total users… Therefore not that many magazines/communities have been pulled in, yet…
I was mistaken - lemmynsfw isn’t bblocked. There are only 3 blocked: lemmy.one, lemmy.today, lemmy.froztbyte.dev. Are you proposing that lemmy.ml, lemmygrad, and hexbear get the block?
lemmy.froztbyte.dev is/was sending malformed messages that caused this the queue runners to crap out. The others were for persistent harassment of one of our trans members.
Removed by mod
On both you have to search for a magazine handle (magazine@instance.tld) if the magazine is not yet on the server. And not the magazine search but the regular search. It can of course be blocked by the instance, but most likely just nobody searched for it before. Most mbin instances are very small and even fedia only has like 4000 total users… Therefore not that many magazines/communities have been pulled in, yet…
Removed by mod
Yeah our user documentarion could need some inprovements. Though I doubt a lot of users would actually look at it…
The best way to link communuties is with the !community@instancs.tld which works on lemmy and Mbin, but not on kbin (I think)
It’s because I blocked lemmynsfw after it was reported for the 746272635th time.
Removed by mod
I was mistaken - lemmynsfw isn’t bblocked. There are only 3 blocked: lemmy.one, lemmy.today, lemmy.froztbyte.dev. Are you proposing that lemmy.ml, lemmygrad, and hexbear get the block?
Just curious, what was the reason for blocking those first three instances?
lemmy.froztbyte.dev is/was sending malformed messages that caused this the queue runners to crap out. The others were for persistent harassment of one of our trans members.
Removed by mod