• 0 Posts
  • 21 Comments
Joined 1 month ago
cake
Cake day: August 17th, 2024

help-circle

  • I mean sure…but essentially you’re using the facts as they stand as justification that it will never work

    More or less.

    when my whole point is that these facts as they stand need to change because they will never work unless we change them.

    I think to make that argument you’d have to first argue that this works elsewhere. But we see warnings like this, https://web.archive.org/web/20221104001618/https://old.reddit.com/r/TaylorSwift/comments/yljj15/swifties_be_warned_that_this_is_a_fake_account/ or like this, https://www.instagram.com/czaronline/p/CvAts_9MFDf/

    then I’m not at all convinced that this is the case.

    You can tweet at celebrities, and you can follow celebrities on instagram, and all the other services, but you generally can’t email them.

    Perhaps it’s a generational thing? Back in the day you could. Bill Gates used to be reachable at [email protected] and Jeff Bozos at [email protected]

    On the flip side, just because a celebrity has a handle on a particular social media service doesn’t guarantee you can reach them. Taylor Swift has a tumblr but she hasn’t publicly used it in years.

    People keep using email, and domains as reasons for why it’s not an issue, but there’s a reason celebrities aren’t known for their email.

    What’s the reason? Two things come to my mind: first, Bill Gates supposedly said he had an entire team whose job was just to read and respond to his public email.

    Second, email is direct contact, like a DM rather than a tweet (that everyone sees). The email equivalent would be a mailing list. If you want that, you can join Taylor Swift’s mailing list over at https://www.taylorswift.com/#mailing-list

    you wouldn’t want a second abff08f4813c to exist.

    I wouldn’t mind that much, tbh. Though considering the username in question, it’s very unlikely.

    Even if you don’t use tiktok, you would want to make sure nobody else has the name abff08f4813c on tiktok.

    Much harder with a name like Taylor Swift. How many other people have the same name? Even on twitter there’s a different taylorswift - so the famous singer is taylorswift13 there.

    now suddenly 300 more abff08f4813c on 300 different instances all pop up.

    My username is probably the wrong one to use for this example.

    But more generally - does anyone want to be [email protected] and [email protected] and [email protected] and [email protected] all at once? (Well, okay, yes there probably is someone who wants that, with bad intentions, but practically speaking it’s kinda obvious that these aren’t all official email accounts by the singer.)

    Because if you try to sue one person on one other instance that has abff08f4813c,

    But Taylor Swift may not be able to sue the other person - she’s not the only one named Taylor Swift after all.

    What I’m suggesting is, no matter which instance you’re on, if you search abff08f4813c, the search should find that username, and direct you to the profile that corrilates with you. And even though that profile is only on one instance, it would make it so if I tried to make abff08f4813c, on another instance, I would be told that username is already taken.

    And then someone tries to be abffo8f4813c or abff08f48i3c.

    I don’t see any celebrity who values their own brand on an international scale, be willing to publically announce they are on the fediverse,

    uh … https://joinfediverse.wiki/Notable_Fediverse_accounts

    and their fans can migrate to the fediverse to follow them.

    I mean, there’s no accounting for the fans, sure. If anything, celebs seek out platforms that have lots of people to connect them with fans, rather than them bring fans to a platform, I’d guess.

    From there, you could absolutely create an old twitter style verification system.

    Sure, but it’s not a required step.

    Mastodon.social could implement a mimic of the old twitter style verification system for folks who join that particular instance - and those joining another instance simply wouldn’t have the guarantee.

    And then threads can implement the verification system for folks joining directly through threads - and again those joined on another instance simply wouldn’t have the guarantee.

    And then Bluesky can …

    I don’t really see anyone but a commercial company even trying to do this - it’d be a headache - and probably expensive - in terms of the requirements to protect the data used (such as identify card verification).







  • I can’t ask, because years ago I watched a video on twitter. It was funny. I tweeted “That killed me”. I was banned
    youtube doesn’t seem to have a direct messaging system.

    Does this person have a patreon or something similar? Could sign up and then ask there. Or leave a youtube comment on a recent video sharing your email address.

    Heck, I might risk creating a new youtube account over VPN just to ask in a public youtube comment for peertube (so if YT bans the account for mentioning peertube, it’s no loss to me, and the creator has still gotten the message).

    They’ve never heard of mastodon.

    Makes sense if this was years ago, back when it was younger and less wide spread… I also imagine you just heard and saw this, but didn’t directly ask because, well yeah.












  • Depends on your POV.

    In one sense, if ActivityPub can be a bridge between two protocols (e.g. RSS vs email) then it’s always technically possible to cut out the middle man. In that sense, no not really.

    From my POV though ActivityPub shines because it’s more content agnostic. RSS is specific to feeds and posts, while email is for email, Bluesky is Bluesky (twitter), etc, but ActivityPub can handle video (peertube), images (pixelfed), forums - including likes and downvotes (Lemmy), microblogging (Mastodon), etc. (Note that the ActivityPub to email implementation I mentioned currently doesn’t handle likes/downvotes for example.)

    With the possible exception of email, I’d also say that ActivityPub has something these other protocols do not - ownership over your own data. If you run your own instance for yourself, you always retain a copy of your content - you don’t have the situation of ello.co where if the site suddenly goes down without warning you lose years of work. Even if you use someone else’s instance, if that goes down you may be able to recover your content from another instance that was federating to it (retrieving content posted to kbin.social from the copy at fedia.io for example). That’s the beautify of federation.

    (This is also true of traditional email, but things like gmail and Outlook - where the email is simply hosted on someone else’s server - are moving away from that.)