• 0 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle




  • Threads presents a serious danger to the long-term viability of the fediverse if we become dependent on it for content, and our best bet at avoiding that is defederation.

    If Threads federates… it’s part of the fediverse.

    Even if you don’t accept that tautology, sure, maybe the fediverse (not including Threads, which is also fediverse at that point, but ok whatever) doesn’t do great, but kbin will definitely suffer if it defederates from Threads, once Threads becomes part of the fediverse federates does whatever you think it’ll be doing that’s not exactly the same thing as joining the fediverse and therefore becoming part of the thing that you think will become non-viable after the most viable piece of it joins. Kbin will become an also-ran within the fediverse, because most users will want to use tools that allow them to interact with the most people.

    I guess what I’m saying is you can’t in one breath say that “Threads will join the fediverse” and then in the next breath say “the fediverse will become non-viable” as if Threads isn’t part of the fediverse in the second breath. Let’s not do “separate but equal” with social media, please. It’s silly.

    If Kbin defederates from Threads, it’ll be Kbin that suffers.



  • Duct. Duck is a brand name

    Yes. But also mostly no.

    Wikipedia:

    “Duck tape” is recorded in the Oxford English Dictionary as having been in use since 1899 and “duct tape” (described as “perhaps an alteration of earlier duck tape”) since 1965

    and:

    In 1971, Jack Kahl bought the Anderson firm and renamed it Manco. In 1975, Kahl rebranded the duct tape made by his company. Because the previously used generic term “duck tape” had fallen out of use, he was able to trademark the brand “Duck Tape” and market his product complete with a yellow cartoon duck logo. Manco chose the term “Duck”, the tape’s original name, as “a play on the fact that people often refer to duct tape as ‘duck tape’”, and as a marketing differentiation to stand out against other sellers of duct tape.

    People should really do the bare minimum double-check before showing their whole ass.

    As others have noted, “duct tape” is the last thing you want to use on ducts. Better to actually call it “duck tape,” as it was for the first 65 years of its existence.








  • Give Meta an inch they’ll take a mile. No quarter. No wait and see. No half measures. We don’t literally know nothing; we know Meta is involved. That’s enough for me to say no.

    They’ll follow the Microsoft route, pretending to be for open standards, then extending the standard for only their apps and sites, and with sheer numbers and money they’ll grab a bunch of users who will come to expect the features and implementations they provide and then bam. No more fediverse.

    Not. One. Inch.




  • For me, part of the reason that the concept of the fediverse is hard to grasp comes from there not being any good visual representation of how it works, like a “metro transit map.” It also doesn’t help that the way you “get to” other instances’ content is by using awkward @ notation. Kbin’s top left info next to Threads is handy but only if you know how to read it. I’d prefer to see something more like:

    Host: <instance name>
    Magazine: <magazine name>

    rather than the current cumbersome “/m/<mag-name>@<inst-name>”

    Also, and this may be a culture thing that I’m not privy to, but I find it weird that there’s no quick way to tell which instance a user is commenting from (without interacting with the page in some way) [1]. It seems that there’s this default intent to make the federated nature of the fediverse somewhat invisible, and I think the better option would be the exact opposite. By making the different instances (and their users) immediately and easily recognizable, it will condition new users to better understand what the heck is actually going on under the hood, and lead them to discover things about the fediverse that they wouldn’t otherwise have known was even stuff to know.

    [1] Right now I can hover over a username and get a pop-up card telling me what instance they’re from - indicated as @<user>@<instance>. I feel it would be considerably more helpful (and habituate new users more easily) if the username above the comment gave that info explicitly without having to hover over. Maybe something like “<user> from <instance>”.