Readit News logoReadit News
oehpr commented on Ask HN: Make Flagging Activity Public?    · Posted by u/Guid_NewGuid
Paradigm2020 · 4 days ago
Except for the highlight the text (think people on mobile, people with disabilities etc) it sounds like a good plan.

Than other random "judges" would be asked if the reason given by the "accuser" are correct. There would have to be some "cost" in karma to flag a post (or limit of X flags / day for X karma status or smth) and some reward in karma for being chosen as a judge/jury.

Also the need to have a minimum flagging weight and a minimum of judging weight and to reconcile conflicting votes.

Anyway would love to talk about it more but tbh it's probably not gonna happen also because most people don't like jury duty... Maybe when ai gets over the "hallucinations" but well at that point we can also get our individual ai's to read everything and judge for us

oehpr · 4 days ago
I don't find highlighting text on mobile to be too difficult, so I don't see that as a barrier imo.

for disabilities well... That one I dunno. I don't have a good concept of what kinds of UI are most convenient for each type of accessibility case.

And it's a little tempting to get lost in the weeds of who watches the watchers, but to be honest even if implemented in hacker news case, the mods themselves could vet flags for anomalies. Just this on its own would serve as a force multiplication for HN mods.

For more decentralized forms of moderation. One method might just be a simple flag appeal. Circles back to the community, they can discuss if the rule that is cited is fair, and if it wasn't possibly remove or limit flagging abilities of those who cited the rule incorrectly. And possibly some increased punishment if the appeal fails? There are lots of options there. Big wide design space.

I do think the direct text highlighting has a few important features. The Sybil attack resistance is one. That was one of the OP's primary concerns. Also, clarity on what rule was broken and why is very important, and a given rule can be verbose. It might not be obvious what specifically in a given rule was the reason for the violation. Direct highlighting lets flaggers more directly communicate what the issue is, without opening the communication channel up for a flame war.

oehpr commented on AGENTS.md – Open format for guiding coding agents   agents.md/... · Posted by u/ghuntley
dingnuts · 5 days ago
several ironies here:

1) an AI agent is less likely to notice than even a junior is when the docs are out of date from the code

2) AI boosters are always talking about using language models to understand code, but apparently they need the code explained inline? are we AGI yet?

3) I frequently hear how great AI is at writing comments! But it needs comments to better understand the code? So I guess to enable agentic coding you also have to review all the agents' comments in addition to the code in order to prevent drift

HOW IS ANY OF THIS SAVING ME TIME

oehpr · 4 days ago
Well... Yah. For the record I'm saying this to trick humans into making better comments for humans. It is very difficult to convince people to do this otherwise, in my experience.

buuut...

I will also mention that these agent files are typically generated by agents. And they're pretty good at it. I've previously used agents to dissect unfamiliar code bases in unfamiliar languages and it has worked spectacularly well. Far far FAR better than I could have done on my own.

I have also been shocked at how dumb they can be. They are uselessly stupid at their worst, but brilliant at their best.

oehpr commented on Ask HN: Make Flagging Activity Public?    · Posted by u/Guid_NewGuid
oehpr · 4 days ago
Just some food for thought: I was recently brainstorming ideas for building a more decentralized moderation system, and one of the ideas I arrived at was using the rules themselves as part of the flagging system.

It would work like this: When you flag a post for breaking the rules, the community's guidelines will pop up. You are then asked in this window to highlight the relevant section or sections of those rules that this post has violated. And I don't mean just "select which rule was violated", I mean "use your cursor and highlight the text of the rules that were violated." (with support for highlighting multiple sections if so desired).

This serves the following functions:

1. Communicates why something was flagged (obviously).

2. Forces the person who's flagging the submission to actually read the rules.

3. The subjectivity of the highlighting system is used to make Sybil attacks more obvious. I'll explain why after this list.

4. It differentiates flagging from downvoting. Downvoting is for saying "I don't like this". Flagging is for saying "This violates our community's rules".

As to why this helps reveal Sybil attacks: There are several subjective points on what, where, and how people will highlight rules. Should punctuation be included or not? Should the key word in the rule be highlighted? The key sentence? The whole section? What about examples? Should we include them? Or only highlight them? Users operating in good faith will cluster around common points in common areas, but will have different ways of doing so. So, if a block of users all have: the same input, in the same way, clustered around the same time, then it was likely a Sybil attack.

This system doesn't require that it de-anonymize the people who submit flags, but it does provide a form of publicly visible transparency as to why something was flagged.

Edit: I forgot to make clear, you would be able to see a heat map of the rules that were highlighted for a flagged post.

I'd be interested to hear any thoughts on this idea.

oehpr commented on AGENTS.md – Open format for guiding coding agents   agents.md/... · Posted by u/ghuntley
zimbatm · 5 days ago
This should have been CONTRIBUTING.md all along.

The content of the AGENTS.md is the same as what humans are looking for when contributing to a project.

oehpr · 5 days ago
The most effective argument I have for getting other developers to comment their code is "The agent will read it and it will give better suggestions".

Truly perverse, but it works.

I agree with you... but the reality is that there's a wide contingent of people that are not capable of understanding "people don't know the same things as me". So they need some other reason.

oehpr commented on Use Your Type System   dzombak.com/blog/2025/07/... · Posted by u/ingve
stillpointlab · a month ago
I've used the approach described for uuids on a project and I liked it. We were using typescript so we went further using template literal types [1]

    type UserId = `user:${uuid}`;
    type OrgId = `org:${uuid}`;
This had the benefit that we could add validation (basic begins with kind of logic) and it was obvious upon visual inspection (e.g. in logs/debugging).

1. https://www.typescriptlang.org/docs/handbook/2/template-lite...

oehpr · a month ago
I assume you used these against a relational database? Did you commit those ids with the prefix still attached? or did you `.split()[1]` or something?

I think it's a pretty good idea. I'm just wondering how this translated to other systems.

oehpr commented on Tell HN: Notion Desktop is monitoring your audio and network    · Posted by u/HoyaSaxa
Pi9h · a month ago
If anyone is looking for an alternative to Notion without the bloat, I’m building https://docmost.com.

It has a nice UI, real-time collaboration, diagrams support and more.

You can self-host it too.

oehpr · a month ago
I've been looking for a tool like this that can publish. I was thinking of some way to create a help doc system for end users, but interleaved with technical information and discussion for devs. IE to make the help documentation a single source of truth for application behaviour.

All this needs to work is the ability to mark blocks of the document as "public" so only that gets published properly. Any possibility of doing this currently or interest in supporting in the future?

oehpr commented on Bypassing Google's big anti-adblock update   0x44.xyz/blog/web-request... · Posted by u/deryilz
janalsncm · a month ago
“Sorry, we don’t support any browsers other than Chrome”

I agree exploiting a bug isn’t a sustainable solution. But it’s also unrealistic to think switching is viable.

oehpr · a month ago
Keep chrome installed and fall back iff forced to. That way the majority of usage statistics show up as other browsers so when developers are making guesses at which browser to support, those statistics will push them away from chrome.

Additionally: you would be surprised how infrequently you have to switch to chrome

oehpr commented on iPhone customers upset by Apple Wallet ad pushing F1 movie   techcrunch.com/2025/06/24... · Posted by u/ewoodrich
AJ007 · 2 months ago
Apple has lost the Google deal and the ability to force apps to pay them 30% of sales. Both were ultra high margin. Apple is going to replace that lost revenue by filling the iPhone up with ads.
oehpr · 2 months ago
So, hypothetically here, say Apple was still extracting extortionate rents: Why wouldn't they just choose to make more money with ads?
oehpr commented on iPhone customers upset by Apple Wallet ad pushing F1 movie   techcrunch.com/2025/06/24... · Posted by u/ewoodrich
matthewmacleod · 2 months ago
Given that it is currently now, that is all that matters.
oehpr · 2 months ago
...

help me understand that position.

oehpr commented on LLMs pose an interesting problem for DSL designers   kirancodes.me/posts/log-l... · Posted by u/gopiandcode
romaniv · 2 months ago
The title should be "DSLs pose an interesting problem for LLM users".

It is significant that LLMs in coding are being promoted based on a set of promises (and assumptions) that are getting instantly and completely reversed the moment the technology gets an iota of social adoption in some space.

"Everyone can code now!" -> "Everyone must learn a highly specialized set of techniques to prompt, test generated code, etc."

"LLMs are smart and can effortlessly interface with pre-existing technologies" -> "You must adopt these agent protocols, now"

"LLMs are great at 0-shot learning" -> "I will not use this language/library/version of tool, because my model isn't trained on its examples"

"LLMs effortlessly understand existing code" -> "You must change your code specifically to be understood by LLMs"

This is getting rather ridiculous.

oehpr · 2 months ago

u/oehpr

KarmaCake day957January 29, 2018View Original