this post was submitted on 14 Jul 2023
7 points (100.0% liked)

/kbin meta

2 readers
1 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 1 year ago
 

I usually browse under kbin.social/sub.

I noticed some posts from lemmyshitposts@lemmy.world and many others popping up in the sub-feed. The thing is, I've never subscribed to these magazines.

I even went to the magazine to check, whether I've subscribed accidentally, but I did not.

https://photos.app.goo.gl/FTGfJc3CASm69yWL6

you are viewing a single comment's thread
view the rest of the comments
[–] mack123@kbin.social 1 points 1 year ago (1 children)

Have a look if you don't have an accidental subscription to kbin.social.

I had a similar problem. That seems to be a connection point for federated posts and makes all of them appear in your subscribed feed. It does not appear on your magazine list.

[–] adonis@kbin.social 1 points 1 year ago (1 children)

good hint, but nope... not subscribed to kbin.social either. Also checked /d/lemmy.world to make sure.

[–] e569668@fedia.io 2 points 1 year ago (1 children)

specifically the one in the picture is under the domain programming.dev so I would check there. For instance I just checked /d/programming.dev and I see plenty of 196 blahaj posts listed

[–] adonis@kbin.social 1 points 1 year ago (1 children)

ooooohhh... yess...didn't see that... yeah, programming.dev I have knowingly subscribed to.

But still wondering, why lemmyshitpost is here though.

[–] e569668@fedia.io 1 points 1 year ago

That would be why, the post is considered under the domain programming.dev, which you subscribed to. I believe this is the relevant issue https://codeberg.org/Kbin/kbin-core/issues/118#issuecomment-942720 but posts are under the domain that show up in the () rather than where the actual destination of the post is made. I imagine it has to do with where the user is, because that user is posting to their local domain's copy of the community/magazine, it seems to erroneously use that rather than where it's actually being federated to