Stories

Comment by mostcallmeyt

Comment

Comment by mostcallmeyt

Direct quote:

> Hello! First time posting here. The other day there was this email, forwarded from a moot of mine which in turn came from a private investigator that did a deep dive on the Oberranks incident at Wikipedia, and made a private investigator report of it which is available for $2,800 from Aragon Investigations LLC in Arizona; you can phone call them and ask about that if you don't believe me. If the full story gets put in the press, expect it to become one of the "greatest news of the decade" like Jacob Coxon.

> TLDR: Wikipedia scandal where multiple powertripping admins gangstalked fed employees for more than a decade, which will trigger media storms and even congressional investigations if the full details get put on the news.

> Except here, quotes mine:

> "XXXX, Mother of God, what an absolute trainwreck. The amount of time and taxpayer money wasted on this internet turf war makes my head spin. And there's enough stupidity here to go around for everyone involved. First off, let's talk about the original beef and these Wikipedia guys. If XXXXXX was cutting corners on his citations, that's sloppy work. You slap the guy's wrist, tell him to fix it, and move on. You don't start a decade-long crusade over missing references about military badges. And then there's this whole angle with the Holocaust history, which is where this goes from petty to downright screwy. You've got this German guy going out of his way to attack a respected historian, trying to discredit his articles and claiming his published books are unreliable junk. It leaves a real bad taste in my mouth and smells like Holocaust denial. And throw that Canadian librarian in the mix - who has the time to call up libraries to try and tank a guy's career over Wikipedia references?"

> "But don't think for a second I'm letting the National Archives off the hook. This "OberRanks" circus? What kind of amateur hour were they running over there? You've got federal employees all sharing a single login to do "official" government work on a public site run by anonymous users. That is garbage operational security. And then they just hand the password over to some private Navy researcher who happens to be passing through. It's a miracle they didn't leak something classified. And let's not forget the Wikimedia Foundation and their so-called "Arbitration Committee." A bunch of volunteer hall monitors who let a dispute fester for a decade until women are getting stalked, federal employees are getting doxed, and the Army CID and the NSA have to get involved. If they had just booted the lot of them back in 2012 when the threats started, none of this would have happened. When you step back and look at it, you've got a tragic death, international police investigations, and ten years of harassment all because a bunch of grown men couldn't walk away from an internet dispute. There aren't any good guys in this mess, just ruined reputations and a whole lot of wasted time. Anyway, shoot me the invoice. I want to read the rest of the report. Stay safe out there. — Kevin"

> "From: Zeke Igtos Sent: Wednesday, July 28, 2026 09:39 AM To: XXXXXX@pd.boston.gov>

Subject: Wikipedia Case Summary

Kevin, thanks for reaching out about the Wikipedia case. Here is the report summary of the case file I drew up. I was contacted around four years ago after a friend of my ex-wife (XXXXXXX) began writing a story about the stalking of women on Wikipedia by a handful of prolific male editors. From what I was able to gather, XXXXXXX had briefly created an account on a website called Wikipedia Sucks to identify some of the men involved. One of them then attempted to have her removed from the site, claiming she was actually a banned Wikipedia account called "OberRanks". They ultimately succeeded in having her removed. By that point, she was preparing to move to Israel anyway and, sadly, lost her life in a terrorist attack shortly thereafter. As for the Wikipedia case I investigated, it primarily revolved around a long-running dispute between a prolific German editor named XXXXX and the United States National Archives. Around 2011, XXXXX was blacklisted from the National Archives after sending threatening messages to several members of its staff. The dispute centered largely on photographs of U.S. military awards, badges, and insignia that XXXXX believed violated Wikipedia's copyright policies."

Replies mostcallmeyt · 2026-09-14
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. Type a domain, or paste a link to block its site, and press Enter.

New collection

Delete this collection?

About YAVCHN

YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

Created by Paul Parks and built with PUDL.

YAVCHN source code on GitHub

Privacy policy · Terms of use

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Read the marked story in the article reader.
[ / ]
Read the story above or below in the list, in the same article reader. Back returns to the story you came from.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Previous and Next buttons read up and down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Previous and Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

Browsing view

View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.