The same thing seems to be happening with [email protected] and [email protected]. The former hasn't had a post show up on kbin since July 13th, while the later doesn't appear to have any posts at all. Initially I was thinking maybe it was due to the lemmy bug that mistakenly marks some connected instances as inactive and stops sending them updates. It may be specifically because these are bot accounts, though.
I believe this is specifically a bot account issue, because non-bot posts are still showing up as expected. On Lemmy, there's an option that toggles the visibility of bot generated content, but it doesn't seem to be a setting here.
Race was multiselect but picking more than one answer value did not display in the results. In that case it should've been radio buttons only for that question.
Usually when you see an uncomfortable bench it is made like that so people dont sleep on it. What could be worse than someone sleeping on a bench. Its called hostil design or something.
Hostile architecture, yup. Nothing better than the one-two punch of poorly accommodating people's sitting needs while simultaneously ensuring the unhoused have to suffer even more!
Not to mention what all these "creative designs" do in terms of making some of these benches basically unusable to people with certain physical or sensory disabilities.
I am not sure how to see the main feed of mastodon from kbin but you can use https://kbin.social/u/@USERNAME@INSTANCENAME to view posts from a specific user.
Kbin seems to treat individual accounts on mastodon as different magazines.
Also from Mastodon it will not appear in the main feed but you can use a fediverse link to view it and comment on it.
Next to comments and posts where it says more it will give you a fediverse link. If someone puts that in the search bar in mastodon they can connect to it.
Yeah, that’s a decent hack. Though it requires creating the same magazine locally (fair enough), but if there already is a local magazine that’s federated to that other instance, then it’s complicated.
I guess I’m not clear on how federated magazines work. Suppose we have:
domainX.social/m/immigration
domainY.social/m/immigration
domainZ.social/m/immigration
and someone locally creates a local.social/m/[email protected]. Does that mean we can still create a an unfederated local.social/m/immigration? Or can multiple federated magazines be combined in the same local mag?
And what if domainY has a right wing extremist anti-immigration slant which we don’t want. But we want domainZ’s version but domainZ has federated with domainY?
In your example, it wouldn't be local.social/m/[email protected]. If a user on local.social created a immigration magazine it would be local.social/m/immigration The @ part is only for remote magazines. So that same magazine viewed from domainX would be domainX.social/m/[email protected]. local.social/m/[email protected] is an immigration magazine hosted on domainX.social and accessed from local.social
Or can multiple federated magazines be combined in the same local mag?
Not currently. There are multiple proposals for grouping magazines that are being discussed.
And what if domainY has a right wing extremist anti-immigration slant which we don’t want. But we want domainZ’s version but domainZ has federated with domainY?
You can subscribe to whichever one you want. domainZ.social/m/immigration is not affected by whatever the users on domainY post to domainY.social/m/immigration. They are two separate communities.
/kbin
Top