💾 Archived View for idiomdrottning.org › threadiverse-tutorial captured on 2023-11-04 at 11:31:41. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-09-08)
➡️ Next capture (2023-12-28)
-=-=-=-=-=-=-
If you got an account on Mastodon, Homecamp, Akkoma, Misskey, Pixelfed or similar during the big Twitter migration and you wanna reply to a post on Lemmy or kbin, read on!
If you don’t have any Fedi account at all yet, you’re living the blessed life. Good on you!♥ Bookmark this page and return here once you’ve been on Fedi a few weeks and have gotten comfy and wanna branch out to the threadiverse. Or, if it's the threadiverse itself that's appealing rather than the seedy world of microblogging, just make an account on Lemmy or kbin instead and in that case you don't need this tutorial. You might need a reverse tutorial if you wanna interact with people from Mastodon or Pixelfed or whatever, but I don't know how to make one since I don't know how Lemmy looks from the inside!
For us in gemspace, there is actually a Fediverse on Gemini thing that’s awesome, it’s called Tootik, but this tutorial doesn’t apply to it yet since it can’t fetch posts by URL as far as I know. I don’t know for sure, but I believe you can still subscribe to Lemmy and kbin groups from Tootik. I’ll edit this section if I find out more.♥
hd.206267.xyz, a Tootik instance
Sometimes servers are unavailable, queues are filled, posts deep in threads don’t propagate properly. It’s a flaky, unreliable mess that’ll bring tears to us who remember the relative reliability of mailing lists.
Groups are called “communities” on Lemmy and “magazines” on kbin.
Subscribing to the groups as if they were users is the basic level of compatibility. In that sense, it works kinda like gup.pe did. Each group is associated with a username on a server, like for example if you have a server named bar and a group that’s https://bar/c/nitpicking the group’s “user name” is either !nitpicking@bar or @nitpicking@bar (depending on whether your own instance’s server software supports the ! thing or if it only supports @).
You can search for that user in the search field on your own instance in order to follow it (“subscribe to it”).
You can mention the user in order to post to the group, whether or not you’re subscribed. I haven’t figured out yet how to do it in a way that doesn’t look goofy.
This is what doesn’t work on Tootik yet, if I understand it correctly.
I don’t like to subscribe to things. I don’t wanna bring in a bunch of floods and must-check-must-check communities to my life. I try to keep my “daily torrent” pretty limited, and then if I do wanna spend some time browsing a little bit further, that’s perfectly fine, and that’s when I sometimes stumble over a comment or post I wanna reply to.
Let’s say Alice@foo has started a thread in the community nitpicking@bar and Bob@baz has replied somewhere in that thread and you wanna reply to Bob@baz’s comment. Since posts are federated, they are copied and show up in multiple servers; a post here might show up on foo, bar, and baz, for example. So the challenge for you is to find the right version. If you wanna reply to a comment by bob@baz, that means that the URL to the post you wanna find is the one on the baz server. It doesn’t matter that the thread is on a group on bar or was started by a user on foo.
You’re looking for an URL such as https://baz/comment/12345 if baz is a Lemmy server, and an URL that’s a li’l longer and more complicated if baz is kbin. Look for a “fedilink” or for the li’l rainbow-colored Fedi logo until you’ve made your way to the original post.
Then you can paste the URL of where you’re at into the search field of your instance. It’ll spin and search for a while, and sometimes you have to reload and try twice, and other times it won’t work at all.
The same basic idea can be used in order to reply to Mastodon comments from Pixelfed or whatever. On Mastodon, you can often find your way there by clicking on the date of posts (not sure why it is that way) until you’ve found the commenters home server. Pixelfed is even weirder since often they have turned off their web interface so you can’t even see the post without being logged into that specific Pixelfed server (I don’t know why they are like that) but you can past the URL into your own Fedi instance and then you can see the post there.
And from here you can reply, boost, or like the post, although your boosts or likes won’t show up on Lemmy at all, go figure; and Lemmy upvotes of your reply won’t show up on your instance at all; kbin upvotes will, though.
Now to the most frustrating part: sometimes your reply won’t even show up! You’ve spent all this time typing it and even then sometimes it just goes missing in the wind. And you won’t know for sure for sometimes it shows up right away, sometimes it takes a few seconds, sometimes a few hours, and sometimes it just never shows up.
The threadiverse is a flaky and dangerous ocean.
On Mastodon it’s good practice to not delete the username of the person you’re replying to. It helps make sure they get notified and that they can even see the post.
On Lemmy, that’s not the norm. Most replies on there from Lemmy users to each other do not include the username, and I’ve taken to deleting the usernames when replying to them on there. Works great, looks great on their end, awesome all around.
However, there’s a caveat here: If the person you’re replying to is on another instance, then if you delete the Lemmy username, the thread’s Lemmy instance won’t see it, it won’t be aware of it. Sometimes it shows up later, sometimes not. So in that situation it might be a good idea to keep the usernames in there.
I dunno! I don’t know how to find and browse and see individual posts, let alone reply to them; lemmy and kbin I can jam in any RSS reader but I haven’t figured out how to do that for gup.pe yet. Of course, the “follow the a.gup.pe user in order to subscribe to the group” method, as intended by gup.pe, works, but that runs into the whole “have to accept the entire firehose” problem as outlined above.