• 0 Posts
  • 44 Comments
Joined 1 year ago
cake
Cake day: July 12th, 2023

help-circle






  • Definitely shield dropping in smash bros melee. Seemed like an essentially impossibly difficult skill, and nearly made me stop playing because I don’t have the time to invest into that kind of tech skills just to be competitive. But then I had my eureka moment when I learned that you can get your shield up and not roll if you just have the stick to the right or left when you press shield in the first place. After that it’s just dropping the stick down one notch and you’re dropping like no tomorrow. Bit of practice to get the timing down and now I’ve unlocked an entirely new dimension of my play.

    Yet another reason I cannot stop playing melee. Every time I think I’ve figured that game out, it reveals an entirely new level of depth that was invisible before I had the tech to see it.








  • In my mind, they should be paying the actor the same for the new lines regardless of whether they opt for them to come back in and re-record or use AI to generate the new line. The actor’s product (their voice) isn’t worth any less, but the company could save money by streamlining the creation of a new line through simplified logistics. This way the company has some benefit while preserving the actor’s livelihood.

    Of course there’s no way these companies are going to want to pay full price for these new lines, since it’s an obvious point where they can pressure performers to accept a lower rate.






  • My objection with federating with Threads has nothing to do with privacy or data access, it has to do with keeping the ActivityPub protocol alive. Embrace, extend, extinguish is a much more legitimate threat to the fediverse than data scraping ever will be. No, the danger is that Meta will begin to contribute to the protocol. At first, contribution by a corporate actor would seem like a fantastic boon to an open standard that we wish to see grow, that’s the embrace phase. But it would not be long before Meta began adding features that are exclusive to a Threads user - they’ll extend the protocol to better accomplish their ends. In this way, they seek to bring more and more users into their platform in order to take advantage of these exclusive features while maintaining compatibility with the larger Fediverse. The end goal is to have enough users that when they decide to break that compatibility, they will make off with the majority of the users from the open community; that’s the extinguish part.

    This is a well-established strategy that large tech companies have employed with open standards in the past (see XMPP). I strongly believe it is in the Fediverse’s long term interests to remain defederated from Threads, and any other large corporate player. Better to have fewer users and grow organically than to federate with Meta; we may see a short term boost to the fediverse, but the long term risks outweigh any benefit.

    That being said, the nice thing about the fediverse is that I can just leave this instance for another if I disagree with the admin’s decisions.