Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)MO
Posts
108
Comments
2,085
Joined
2 yr. ago

  • The real reason is that they want to save money on the text messages (outside of the US they need to pay $0.05 each time), not because they actually care about user security.

    Like when xitter ran out of money and didn't pay their sms bills and people were locked out of their accounts

  • It's a weak defense because the clients still exchanged metadata with other clients, plus there's the big issue of using the copyrighted works for their own profit, and not just archiving/preservation/personal use

  • Where now are the copyright trolls that sued regular students for millions of dollars for downloading 30 songs?

    Under federal law, the recording companies were entitled to $750 to $30,000 per infringement. But the law allows as much as $150,000 per track if the jury finds the infringements were willful.

    Let me see:

    • At least 100 million of books pirated
    • infringements were willful

    So, a 15k billion dollars fine seem appropriate to give to Meta AND criminal sentences to all the c suite.

    Or: apply the same rules to regular people and allow unlimited copyright violations without consequences

  • Protect from accidental data damage: for example the dev might have accidentally pushed an untested change where there's a space in the path

    rm -rf / ~/.thatappconfig/locatedinhome/nothin.config

    a single typo that will wipe the whole drive instead of just the app config (yes, it happened, I remember clearly more a decade ago there was a commit on GitHub with lots of snarky comments on a script with such a typo)

    Also: malicious developers that will befriend the honest dev in order to sneak an exploit.

    Those scripts need to be universal, so there are hundreds of lines checking the Linux distro and what tools are installed, and ask the user to install them with a package manager. They require hours and hours of testing with multiple distros and they aren't easy to understand too... isn't it better to use that time to simply write a clear documentation how to install it?

    Like: "this app requires to have x, y and z preinstalled. [Instructions to install said tools on various distros], then copy it in said subdirectory and create config in ~/.ofcourseinhome/"

    It's also easier for the user to uninstall it, as they can follow the steps in reverse

  • Eh good luck selling it with a locked bootloader, lots of bloatware preinstalled, without Google apps AND an update planned for next month that will remove completely the possibility of running any android app

  • They're useful for printed media

    "Find more info at bitly/event" instead of "find more info at facebookcom/unnecessarilylongurlthatnobodyisgoingtotype"

    Or for a qr code where it needs to be small and somehow your URL is too long

    But yes, relying on a third party company for something that needs to last a long time isn't really smart. There are many books that have online content now inaccessible because they used a link shortener that's dead or that doesn't let you update the redirection without paying a ransom (need to pay $120/year to bitly if you need to change the redirection)

  • I remember blackberry using bitly links in their developer emails in 2013, and at the time it was possible to see the stats of any link by just adding "+" at the end of the link (now requires authentication or maybe only paid users can lock that page)

    It was dismaying to see that it got only 50 clicks or so lol

  • Well, they give the option to remove the ads altogether for just $120/year 😉

    Although literally nobody would pay that ransom (100000x the actual server expense) to remove ads from their own links