this post was submitted on 01 Aug 2023
3 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That's way more technical details than I expected! I really appreciate that as a developer!
I think in my mind moving a microblog to a thread was like copying the markdown text and pasting it into the thread container. And adding a link to the original micro blog post at the bottom of the markdown.
Maybe bonus if doing this also left a reply to the original post with a link to the thread so the original user is aware.
I think that's technically feasible right?
Ahh, that would make a lot more sense. Yeah, I'm sure something like that could be accomplished, similar to cross-posting.
There is definitely some cleanup work that needs to be done, in my opinion, to clarify the usage of microblogging vs threads. I feel like there's a lot of valuable discussion that gets lost in the microblogs. It's hard to have a single feed of both because microblogs don't have titles ("name" in the API), nor do they have any sort of summary that could be used as a title - making microblogs and threads just different enough from each other to be annoying.
Microblogs make much more sense on Twitter analogues such as Mastodon and Firefish where you follow people rather than topics, but I don't see a way to just follow a list of people via microblogs here - there is domain/sub/microblog (e.g. kbin.social/sub/microblog ) which follows your subscribed subs and people and maybe that's the best way to go here, but it still doesn't address the concern of "what is a microblog relative to a thread?"