The 403 was the planned response when you tried to DM any remote user, because federation of message was just not implemented. With v1.7.0 we implemented it and you will not get a 403 anymore
Apologies for having registrations closed. The moderation tools in Mbin/kbin are very very basic and I keep experiencing large numbers of spam signups, with no meaningful way to handle them until they sign up and start spamming
Hey! Thanks for the response and no worries I figured out spam was likely the reason behind he temporarily closure of new sign up's.
Btw let me know if you are in need of more admins, id gladly contribute to help the server as I have a long experience as mod already on reddit and the fediverse.
You generally seem to need to have at least 1 account from that instance subscribed to your magazine for federation to kick in (which then still can take a bit of time). Same works the other way around. The unfortunate thing is that you kinda have to use external community / magazine indexers to search for them, unless you know the exact name & instance domain they're in, since a search won't find non indexed ones by itself.
Imo one of the largest issues regarding the fediverse.
Yeah, I hope it gets "fixed" at some point ("fixed" because I guess it is by design). For now, I created an account to most large Lemmy servers and subscribed to the magazine so future users find a fuller community :P
Kbin and Lemmy don't seem to federate admin activity. I get a lot of spam from the various Kbin instances whereas Lemmy spam seems to be dealt with already.
I think fixing this requires dev work on both the Lemmy side and the Kbin side.
It was fixed a couple weeks ago but there hasn't been a tagged release in a while.
I'm not sure what the release plan is for 1.5.0, currently there's some very heavy migrations that require special upgrade instructions so I'd like to get a tagged release sooner rather than later to avoid instance admins running into issues, but I think there's still a lot of work in flight
Oh do you use compact mode? If so, sadly another thing that was fixed a while back that hopefully will be fixed for you next release https://github.com/MbinOrg/mbin/pull/544
The post you showed in the screenshot does look fine to me both in classic and compact view on an instance with latest.
But I'd agree not all of your concerns have been addressed. I don't believe redgifs work (well), so will try to look into that if possible, but might be out of my depth.
The playback continuing is interesting. I had made a change long ago to not download every time it was expanded / collapsed as before it would make a request every single time, instead I changed it to just hide and show it after the first load, so that sounds like a side effect of that. Perhaps there's some way for me to also indicate to pause media, I will check
To get to another instance there is the "Magazines" link at the top of the page, or just go directly to the one you want such as https://fedia.io/m/anarchychess@sopuli.xyz
To create a new one is under that '+' icon at the top of the page. Looks easy but I haven't tried it yet.
Oh, so I can get an existing community on another server to show up here by subscribing? That sounds ideal as long as the other server has decent uptime.
I'm not sure what goes wrong, assuming kbin.social didn't block fedia, then I suspect some kind of issue at fedia.io. I believe we need to debug this issue on the server-side. Hopefully @jerry can have a look at his logs when trying to execute the search query above and maybe find the root-cause that way.
ok - just looked through logs and I am not seeing anything that looks related to this issue. There are a good number of error 500's coming from kbin.social, but none appear to be around the time of these posts, nor associated with the referenced magazine.
I thought I was logged in but I can’t remember now. I don’t see a 404 now though, just “empty”. There are posts in that magazine though, on its instance.
fedia
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.