I'm still getting this error. Seems to be related to how long the page is open before the error starts. I have to reload the page and like everything quickly, because after a few minutes it will take me to the error page.
As an added note to the development team @ernest and others:
This has worked pretty well and I'm now trying to clean up the areas I have ownership of now. However, I have a few notes:
I would like it if, in the case of a community ownership transfer happens, that the original "founder" account was noted on the right hand side with the panel details. It would be nice to know this as a moderator or owner of a magazine as, if the user ever comes back, they could reapply for moderation access and I could approve knowing that the person was actually the original founder. Right now, it would be hard to verify that the person submitting a mod request is actually the person who originally founded the community for example.
It would be nice if moderators had the ability to add badges to existing posts to help clean up communities that might have had a lot of content but not much in terms of badge management.
When ownership transfers, it would be nice to get a notification. When transfer of /m/manga and /m/bitwig came to me, for example, I didn't notice until a few days after since I didn't receive a notification.
Should these types of issues be posted as a "bug"? Or is it better to just leave feedback here?
Yeah I'm tempted to make a version of "newcommunities" for Kbin since MagHub just doesn't roll off the tongue (and is abandoned, although I doubt that is why it's so weak)
try this..
click 'magazines' at the top
then type in the name of the remote community you want, like 'funny'.. it should then show you all those remote communities and the local one.... click the community you want to post in
then you should see a banner at the top reminding you youre looking at a local version of a remote community, click the '+' sign and select the post type... this will initiate a new thread.
It's usually easier to search via external sites (https://lemmyverse.net/ and https://browse.feddit.de/ are the ones I've been using). You'll still have to manually copy over the magazine name in order to subscribe for it, but you'll get a wider variety of results without having to go to each instance individually.
I like to explore new/all sometimes to find new communitiies so that's unfortunately not helping. And it's really only a problem with hexbears, everything else blocks just fine.
Same experience here, blocking does not work, Ernest knows but I guess it's not priority number one right now. It's a deal braker for me. Thank you so much for the filter option!
Hello, I have added this feature to KES (third party extension) today. I believe it is working correctly based on your requirements:
Show an icon next to magazine names on the main thread index (https://kbin.social or https://kbin.social/sub if logged in). Click this icon to "softblock" threads from that magazine from appearing on your main thread index. This does not block the magazine outright: you can still go to the magazine directly, so it is less aggressive than a total block.
Show a Softblock/Unsoftblock button in the sidebar of magazines, as well as in the Magazines index located at https://kbin.social/magazines. As you would expect, this button has the effect of adding/removing a magazine from your filters.
Show a tab at the top of the Magazines index that you can use to centrally manage your softblocked magazines. For the time being, this is merely informational.
Full details can be found in the release notes here over at /m/enhancement.
Let me know if this gives you the functionality you wanted.
I think it'd be simpler to just change the block button so it does that. Adding a new "filter" button would lead to newcomers being confused on what the difference is. Besides, I don't think there's much benefit to being completely unable to view a magazine.
This is one of the biggest issues and barriers to discoverability with the Fediverse in my opinion.
As I understand it, unless an instance has already subscribed to a community (magazine in kbin parlance), then in order to make that community (magazine) appear in your own instance, you need to:
First search for the community (including the community's home instance) name in the magazine search function.
The search will come up blank, but the act of searching for it will trigger a backend request for your instance to start federating content from that community. However there's no message to tell you that it's doing that. It just looks like that community doesn't exist.
Further, it may take up to several days (in my experience) for federation to start, ie, you have to repeat the search for the community and only then can you subscribe to (follow) that community
And when it does start, it only starts grabbing new content. So first it looks like the community doesn't exist, then it takes a long time for content to appear, and then it looks like the community is sparsely populated unless you go back to the community's home instance, rather than staying in your own instance, to catch up on old content.
Further pinned posts aren't federated (at least between lemmy and kbin I believe), so you can't even rely on a "here's what you need to know" introductory post to orient new members.
Contrast this to reddit, where (because it's a centralised system) searching for a subreddit produces immediate results, you can join a subreddit immediately, and you can immediately see all current and past content for that subreddit. Much more intuitive and useful to users.
Unfortunately the activitypub protocol that underlies lemmy and kbin doesn't appear to have been designed for reddit-like communities in mind. Ie communities that tend to feature long-form content, posted relatively sporadically, and where having access to the community's archive is very useful to members. It works somewhat better for twitter-like communities where it's easier to jump in "mid-stream" and - because posts tend to be only a few words long - you're more likely to start seeing new content after only a short delay.
I wish that this is something that's addressed at the Fediverse level.
there actually is a way to "backfill" content, being the outbox. (although it was not meant to be used this way, from what i can see from reading what little documentation is out there)
lemmy uses it to federate about 10 or so (i think it was?) of the latest posts, and most microblog implementations use to federate the "pinned" posts of an account
activitypub has quite a lot of quirks, both spec-wise and implementation wise, and there are many reasons including an apparent near civil war inside the working group which resulted in this messy state it's ended up in
honestly the fact that this protocol works at all is a miracle
@Doll_Tow_Jet@kbin.social I don't know if that's the official word for it but I'm using "backfilling" to refer to loading the history of a person or group after first federating with it.
the outbox is a special collection (list in activitypub speak) that's intended to work kinda like an old school email outbox where you put messages to be delivered and it would deliver them to the inboxes of people (and servers that were offline at that time would later pull them in from the outbox)
or, well, that's what the spec says. nobody uses it like that in reality because activity pub was intended for a completely different kind of social media than how it ended up being used (it seems to expect more "everything apps", including an entire client api that would completely abstract away the instance into nothing more than a dumb pipe for activities unlike the current reality where instance software dictate what you can do)
this probably confused you even more but it's getting pretty late here so I can't words good, sorry!
kbinMeta
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.