• 0 Posts
  • 57 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
    ·
    2 months 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.











  • Yeah, it’s unclear to me at the time if the dialogue box in the screenshot appeared when doing a select all operation, but it reads as though the OP dev didn’t understand git, discarded their work, and got upset that it was an option.

    Realistically if the dialogue box appeared, I’m not sure there would be anything else the IDE could do to prevent the dev from themselves. Perhaps reject operations affecting 5000 files? But then you’ll just have someone with the same issue for 4000 files.


  • reading through it, it sounds like they opened a project in VSCode, and it saw that there was a local git repo already initialized, with 3 months of changes uncommitted and not staged. So the options there are to stage the changes (git add) to be committed or discard the changes (git checkout -- .). I guess they chose the discard option thinking it was a notification and i guess the filename would be added to gitignore or something? Instead, it discarded the changes, and to the user, it looked like VSCode did rm -rf and not that this was the behavior of git. Since the changes were never committed, even git reflog can’t save them.