Post

Yeah the moment I saw that info in the reddit thread I was like "okay I get why people were concerned initially about the git history stuff, but this is several steps too far the fuck is wrong with you". Was sad but not surprised to see the follow-up.

0 reposts38 likes

If someone posts my real name on reddit, much less my address, my PARTNER'S NAME, because they don't like a decision I made with a library I wrote, even with good intent...I might well take it down permanently as well. Like come on, it's not *hard* to find out these days but I am pseud for a reason.

> Real names were posted, familial relations were posted and speculated on, home addresses were revealed. jfc. What a dumpster fire. and then theres people like: > Crate owner throws hissy fit and cries about being doxxed like being upset about that is somehow so outlandish...

I actually don't think the person who did it even intended it badly, they just did not think at all about the implications. But I could read between the lines as soon as bits of info started surfacing just why the author probably wanted privacy and then to see people just continue...blech.

yeah OOP has a chosen name too so definitely no bad intentions, just fully didnt know at the time that the display name that was still actively being used to publish the crate was supposed to be changed until OP said so, else i'm sure it would've played out a bit more delicately

yeah. I saw an apology from one of the people in a subsequent thread. was glad to see it. but god this all could have been avoided by reaching out privately first before enlisting reddit for OSINT.

I don't think they did not think it through. Hosting was moved and history on GH deleted to say FU to AI scraping. Project was considered "done" with no future releases. Rename happened for undisclosed reasons (but there were reasons) but was considered unimportant given no new releases ever.

Published crate stays as it is. The new repo head can be verified against cargo if one wants to fork. The version you or whoever uses can be pinned (and should if supply chain attack is part of the risk assessment).