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

help-circle

























  • They are probably reusing a component that happens to sort its entries alphabetically, since that is most commonly the expected behaviour. If the form is configured in a CMS, whoever built it might not even know it’s happening and has entered the data properly, but it gets resorted in the presentation layer. It’s also not impossible that the behaviour of the component has changed at some point and this particular case didn’t have test coverage or wasn’t actually part of the specification.




  • So they have a bunch of users that have been freely paying them money for virtual coins that you can literally only use to display a few pixels of a gif next to a comment.

    Their absolute genius move towards profitability is then to forcibly stop making these people give them free money and also erase those virtual coins that they spent money on with absolutely no compensation whatsoever. Not even a shitty award or literally anything at all.

    It’s funny, I’m not sure if I should actually be impressed that they are not engaging in any marketing dark pattern whatsoever; they are just straight up alienating the people who were until now been practically giving them money for doing nothing.


  • I guess it depends on how this “Data Protection Review Court” actually functions in practice. What is written on paper doesn’t seem to really matter much to US agencies so we’ll see how strong these safeguards actually are.

    Nevertheless, it’s good to see that the new agreement is finally in place at least. We’ve had this legal vacuum for years now and it was completely unsustainable in the long run. Sans a complete legal overhaul of the nonexistent privacy laws in the US (hah good luck with that), this is probably the best we could hope for now.


  • I know that is a popular narrative in the Fediverse community right now, but I honestly find it unreasonable. Google and Meta didn’t kill XMPP, they abandoned it and without them it went right back to where it was originally: barely used whatsoever. The Fediverse already has a small, but relatively healthy user base. Meta can abandon ActivityPub or twist it into something unacceptable, but all that will do is bring us back to where we are right now.

    All that is irrelevant, though, because the difference is that Meta is legally required to incorporate interoperability with other services and that’s why they are going with ActivityPub. Not from the good of their hearts, but because they need to and is in their own self interest to keep alive.

    Right now, they are early adopters of ActivityPub and have a very early strong position there. When they federate they will be by several magnitudes the largest instance on the network. Whether we like it or not, they will inevitably be a major player in dictating the future of ActivityPub. Thus, they want to keep ActivityPub alive because they want to make sure that becomes the future EU mandated industry standard for SoMe. Otherwise, some other technology will be chosen, one that might not be lead by Meta, but by Google, Apple or ByteDance.

    Note, that I’m not arguing whether this is good or bad, but only what I predict is happening.



  • Meta has several billion active users across their platforms. 30M is nothing to them.

    Also don’t forget that we’re talking about a microblog, so it will inherently generate a large amount of individual posts, much more so than e.g Instagram. The quality is however likely very low initially and a lot of users are probably just trying out the current talk of the day.

    I do suspect that Threads will probably grow to a few hundred million users before the end of the year; anything less would probably be regarded as a colossal failure for Meta.




  • like this alternative sidebar which I unfortunately couldn’t get to work as intended.

    Oh, what problems did you run into? I haven’t pushed that many updates lately because I thought it was fairly stable, but perhaps there are still some bugs for certain configurations?

    Thinking out loud, there might be some compatibility issues with Greasemonkey specifically. I’m personally using Tampermonkey, but I know that Greasemonkey have a tendency of being a bit troublesome sometimes. I did have to fix a few bugs related to Greasemonkey for the Kbin Usability Pack a while ago.

    Anyway, please give me a shout and I’ll see if I can get a fix out.