this post was submitted on 08 Jul 2023
1 points (100.0% liked)

/kbin meta

639 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’m on kbin.cafe. Let’s use the top post of kbinMeta as an example.

https://kbin.social/m/kbinMeta/t/86614

When I access this same post from kbin.cafe, the link is instead

https://www.kbin.cafe/m/[email protected]/t/2219/PSA-Upvote-is-not-an-upvote-like-you-are-used

So I can’t just change the kbin.social link to kbin.cafe and append an @kbin.social to the magazine name. I have to search for the post on kbin.cafe, which often won’t succeed if the magazine the post is on didn’t start federating over until after the post was made. I care about this because I would like to be able to interact with posts with my current account.

I can always just have a sock puppet account on kbin.social that I follow with my kbin.cafe account, and use the sock puppet to boost the post so I can access it on kbin.cafe. For me this is actually realistic option given that I made a kbin.social before I found out about kbin.cafe. But it feels dirty, and I would like to not have to constantly switch accounts to access one post or interact with it.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago

It would be lovely if posts had a unique ID (UUID of some sort) that was shared between instances. That way, rather than using the thread ID, a unique ID is used that points at that particular thread, comment, or microblog. But alas, this doesn't exist, and we're here.