Warning: Some posts on this platform may contain adult material intended for mature audiences only. Viewer discretion is advised. By clicking ‘Continue’, you confirm that you are 18 years or older and consent to viewing explicit content.
I think that’s a kbin thing, where any time you reply to a comment, your comment includes an @ to that comment’s author. I think the only one they intended to “ping” was butterface
Oh, interesting! Thanks for pointing that out. Side note: entries… I hope kbin adopts better language for what to call Reddit-like posts (articles), Twitter-like microblog posts (posts), and comments (entries?). I never would have guessed entries == comments. Maybe this is ActivityPub-specific naming? It reminds me of a past job where we surfaced internal technical names as the names of products and features… it just confused customers.
Yes, there needs to be a glossary somewhere to get people up to speed, or some kind of on-boarding process. It’s also plausible that some of the naming conventions are from translation weirdness, and, as you say, backend Activitypub naming conventions that frontend users don’t normally see.
I made a magazine (aka a community, aka a sub[reddit]) specifically so I could play around with kbin to figure things out. Right now, trial and error is all we have, as I imagine all the devs are more busy with more technical issues than naming conventions.
I think that’s a kbin thing, where any time you reply to a comment, your comment includes an @ to that comment’s author. I think the only one they intended to “ping” was butterface
Buttercheeks!
Not a kbin thing… might be an extension though. I’m on kbin and no automatic mention was added to the top of this comment when I replied to you.
It’s a setting (default off) called
Add mention tags in entriesunder the “Writing” subsection.Oh, interesting! Thanks for pointing that out. Side note: entries… I hope kbin adopts better language for what to call Reddit-like posts (articles), Twitter-like microblog posts (posts), and comments (entries?). I never would have guessed entries == comments. Maybe this is ActivityPub-specific naming? It reminds me of a past job where we surfaced internal technical names as the names of products and features… it just confused customers.
Yes, there needs to be a glossary somewhere to get people up to speed, or some kind of on-boarding process. It’s also plausible that some of the naming conventions are from translation weirdness, and, as you say, backend Activitypub naming conventions that frontend users don’t normally see.
I made a magazine (aka a community, aka a sub[reddit]) specifically so I could play around with kbin to figure things out. Right now, trial and error is all we have, as I imagine all the devs are more busy with more technical issues than naming conventions.