• 0 Posts
  • 174 Comments
Joined 2 years ago
cake
Cake day: June 20th, 2023

help-circle

  • Weird story, and I have to assume this is data entry error, identity theft, or something else: I couldn’t sign up for a hospital billing platform because my name and full birthdate (including year) conflicted with someone else in the system. I called the hospital billing department and they were very confused about the whole situation. It didn’t really get resolved, and I basically had to let it go to collections so that I could pay because of the shitty system. I don’t have a very common name, and never have had this problem before.



  • bamboo@lemmy.blahaj.zonetoOpen Source@lemmy.mlNew Awesome Windows List
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    1 day ago

    What I assume the commenter meant is that Beeper was bought by Automattic, which also owns Wordpress and whose CEO is Matt Mullenweg. Recently Mullenweg has been on a vendetta against WPEngine from benefiting from Wordpress, and basically sabotaging Wordpress to spite WPEngine. This article details the beef.

    That being said, I use Beeper (and Pocket Casts, also owned by Automattic) and enjoy them a bunch. I haven’t noticed any issues since April, and the whole Wordpress vs. WPEngine seems to not affect Beeper.












  • As others have said, using dd will be a bit for bit copy of the drive, regardless of the filesystem. If you were only using 10GB, and the rest of the drive was “empty”, the output of dd will still be a 256GB file. You could compress this file with gzip if storage is a concern.

    With regard to your plan with Windows, there is a hardware check that OS will perform and if the hardware drifts too much, the OS will not be activated anymore and will need a new license. I’m not familiar with recent versions of Windows, but if you have a Pro version of the OS, it might not work on new hardware.


  • While this is more an issue with compromise credentials and not a flaw in AWS exactly, I think AWS should just deprecate the use of IAM Access Keys altogether, and have newly issued keys auto expire after 90 days, requiring human intervention to extend the lifetime if absolutely necessary. Had these companies used IAM roles for their services, they would not be in this situation, but that approach requires more effort, so people go with the lazy access key solution.




  • Clearly you didn’t read the article. The first paragraph is about Meta censoring LGBTQ+ content

    On Monday, Taylor Lorenz posted a telling story about how Meta has been suppressing access to LGBTQ content across its platforms, labeling it as “sensitive content” or “sexually explicit.”

    Posts with LGBTQ+ hashtags including #lesbian, #bisexual, #gay, #trans, #queer, #nonbinary, #pansexial, #transwomen, #Tgirl, #Tboy, #Tgirlsarebeautiful, #bisexualpride, #lesbianpride, and dozens of others were hidden for any users who had their sensitive content filter turned on. Teenagers have the sensitive content filter turned on by default.

    When teen users attempted to search LGBTQ terms they were shown a blank page and a prompt from Meta to review the platform’s “sensitive content” restrictions, which discuss why the app hides “sexually explicit” content.

    People who comment on articles without reading the article itself should take a long look into the mirror before implying other people are advocating censorship.