Live data from Hacker News

Maigret: Collect a dossier on a person by username from thousands of sites

github.com

161–170 of 203 posts

Re: Maigret: Collect a dossier on a person by username from thousands of sites

#161

Earlier quoted context omitted.

What's the benefit? It sounds like you might have to explain yourself one day if someone posts something racist/horrible.

I look at it differently, even if someone isn’t going around posting racist/horrible things, people and tastes change over time. I’ve been a part of fandoms that are now seen as cringey or toxic. I’ve also grown up more as a person and I look back at a lot of my old comments as sophomoric. I write differently, and my opinions on things have changed as well. I’ve had people dig through my post history on sites like Re…

> I’ve been a part of fandoms that are now seen as cringey or toxic.

—BuyMyBitcoins

Joking aside, there's definitely value to rotating usernames frequently. I've started using random strings on various sites because I really don't see an up side (for me) to being trackable from site to site and definitely across time. (I use very long random strings for my banking usernames because I don't trust them to have enough bits of entropy in their passwords.)

Re: Maigret: Collect a dossier on a person by username from thousands of sites

#162
post #136
post #125

Earlier quoted context omitted.

Source: https://www.sistrix.com/blog/why-almost-everything-you-knew-... TLDR: on the second results page, each result gets So it‘s not nobody, but statistically speaking not very many.

That's not how statistics work. I consider myself a frequent visitor of the second results page, but even for me the CTR of the results on the second page are The question ought to be "conditional on not finding the result on the first page, how likely is the user to go to the second page versus balk, or re-try a different query?" I'm fairly confident that number is higher than 1 %, but I don't have the data.

Or alternatively, a number "significantly less than 1%" is still massive when multiplied by the number of searches google gets.

Re: Maigret: Collect a dossier on a person by username from thousands of sites

#163

Well, that is creepy as hell, but I guess it is obvious that such a tool could exist, and it is better not to have it exclusively in the hands of data-brokers, etc. I wonder how hard it would be to add the functionality: go back to the email address that has registered these accounts, find any other names they've registered, and search off those. (EDIT: err, wait, I bet that's the "recursive" functionality they menti…

You have probably already clicked ”accept”[1] on one of those ”cookie notices” which actually make you give your consent to having your data processed and all your profiles and devices linked by hundreds, if not thousands of companies all over the world. [1]: more accurately, you didn’t go through the list of all vendors and didn’t object to their ”legitimate interests”, if that was even an option.

If your point is that it is too onerous to use the modern internet without being spied on, yes I agree.

Re: Maigret: Collect a dossier on a person by username from thousands of sites

#164
post #23

Earlier quoted context omitted.

I intentionally steal nicknames I've seen. I'm an asshole as well, so sometimes it works out. I have 13 different nicknames so far that I use/have used since 1997, though I tend to rotate between all of them regularly. I DO hope they try to use "AI" to track me. That will be fun.

What's the benefit? It sounds like you might have to explain yourself one day if someone posts something racist/horrible.

Seems like the solution is built-in to their strategy. If you get accused of being racist because a racist on twitter uses the same handle, just make a new handle and start over.

Re: Maigret: Collect a dossier on a person by username from thousands of sites

#165
post #140

Earlier quoted context omitted.

You always need to balance Precision and Recall. For something like this, you want to be exhaustive. I've worked on search engines, and depending on who is using them, that balance gets struck differently on the ROC curve. For legal matters, for example, they want every record that might match. For ad-hoc (google style) queries, nobody reads the second page so you care more about Precision @ 20 (or really, at 3)

> You always need to balance Precision and Recall. For something like this, you want to be exhaustive. Respectfully disagree. You're right in principle if you build a tool like that for yourself. But since this is Open Source, you have to take into account that people who don't understand that will use the tool as well and then use that as "evidence" in whatever arguments they're having with someone.

> Respectfully disagree. You're right in principle if you build a tool like that for yourself. But since this is Open Source, you have to take into account that people who don't understand that will use the tool as well and then use that as "evidence" in whatever arguments they're having with someone.

Respectfully disagree with you respectfully disagreeing - this line of thinking can be used to argue against almost any information sharing.

i.e. Should we stop governments releasing statistics that might be misinterpreted by an uninformed press? Should we stop open access to medical journals because untrained readers might use them for incorrect medical advice? Should we stop companies releasing public annual reports, because investing consumers that are untrained in reading financial documents might misinterpret them?

Re: Maigret: Collect a dossier on a person by username from thousands of sites

#166

Earlier quoted context omitted.

Really, why is that?

because if you get your account compromised on one site/forum because of lax security on their end, you don't want all your accounts compromised.

How will your accounts be compromised if they are all different? A key is no good if you don't know which lock it leads to.

Re: Maigret: Collect a dossier on a person by username from thousands of sites

#167

Earlier quoted context omitted.

My Gmail is first.last name. I get very sensitive documents for a lawyer with my same name who resides in Texas. We've actually had some decent conversations over the years.

I had that happen once. It was a recipt for a medical purchase, at first I thought I was getting scammed. What tipped me off was the email was sent to firstnamelastname@gmail.com and NOT firstname.lastname@gmail.com. That was the day I realized google would even do that. I ended up using the phone number in the email to contact the person and forwarded the email. And yes, they had my first and last name :)

> What tipped me off was the email was sent to firstnamelastname@gmail.com and NOT firstname.lastname@gmail.com.

Dots don't matter in Gmail, so these email addresses are the same:

https://support.google.com/mail/answer/7436150?hl=en

Re: Maigret: Collect a dossier on a person by username from thousands of sites

#170

Earlier quoted context omitted.

You always need to balance Precision and Recall. For something like this, you want to be exhaustive. I've worked on search engines, and depending on who is using them, that balance gets struck differently on the ROC curve. For legal matters, for example, they want every record that might match. For ad-hoc (google style) queries, nobody reads the second page so you care more about Precision @ 20 (or really, at 3)

Somewhat offtopic, I'm curious about this "nobody reads the 2nd page" meme... I find myself reading pages 2-5 quite often, because page 1 just didn't give enough results, and I doubt I'm that much in a minority ? (I'm talking about actual generalist searches, not people that use a global search engine as a replacement to bookmarks or directly searching, for instance, Wikipedia.)

I always read the 2nd page because the 1st is all SEO crap.
Post reply on HN