Readit News curl -s "https://hn.algolia.com/api/v1/search?tags=comment,author_sjs382&hitsPerPage=10000" \
| jq -r '.hits[].comment_text' \
| grep -o "—" \
| wc -la) exceed the likelihood of people doing this via commenting anyway
b) justify the opaque and powerful nature of flagging as-is
Perhaps you stopping flagging if you're not willing to justify a flag is a good outcome in aggregate? We have mods to kill threads which violate the guidelines already. But looking at the /active list there's certainly an amount of (probably organic) censorship of controversial threads in either direction (though my gut feel is it biases more towards censorship of articles about the latest outrages of US government).
I'm not really interested in say, Ruby, I think people should probably use languages which are type-safe if they want to avoid catastrophes in production and 1am pager calls. However if I see an article about Ruby I'm just going to not engage with it. Perhaps your existing interpretation of the unwritten rules is too broad and actually we ought to rein in the amount of flagging anyway?
I think a lot of us are generally happy with how the site operates—that's why we're here. I personally consider the moderation to be a feature—I think dang and team do a great job. I'm sure you could pick out some counterexamples but comments and posts that rise to the top tend to be thoughtful. There are exceptions. Nobody bats 1.000.
Posters don't have a right to be seen/read. That said, there are plenty of other communities that will embrace the types of posts/threads that would get flagged here.
If you have specific concerns about specific comments/stories getting flagged, it's reasonable to take each one up with the moderation team privately (there's a contact link in the footer). Just don't badger them—becoming a nuisance won't help you achieve your goals.
I often flag submissions or comments when they go against the rules (sometimes written, sometimes unwritten) of the site.
I'm generally not willing to:
* engage with someone who's demanding an audience for a post/comment (upset that their post/comment was flagged).
* justify these flags to a stranger.
* open myself to harassment based on what I flag.
And I can see her being really into this device as an idea, but I would bet all the money in my pockets that she’d never actually use it.
None of this is a critique on these individuals, or how well this PDA performs at being a productivity device. It’s just this meta layer of productivity I’m noticing around me more and more.
Maybe the workshop is what brings them the most joy about the hobby.
Maybe the recipe person appreciates their collection this way.
Maybe they don't frame things in terms of productivity, like you do (even if they do use that word).
Deleted Comment
It's not perfect but I know that I'm more likely to find a result that serves me, rather than a result that's optimizing for an algorithm. And if I do come across something spammy, I know that telling Kagi to adjust a site lower (or remove a site from results) is just 2 clicks away.
Even though it's a small thing, it's one I encountered with every Google search, manyamnymany times per day. Relieving that is worth more than $10/mo to me. I think that pricing is right, though—if it were more than $10/mo and I likely never would have tried it.
The only thing I use Google Search for now is hyperlocal stuff, mostly I expect to interact with Maps result. Kagi Maps isn't even close.
Technical decisions used to be in the daily-notes.org file, but keeping in a separate file makes it more accessible to LLMs. I actually started that practice before LLMs were in common use, I struggle to remember why.
Should that "why" be in technical-decisions.org or daily-notes.org?
Deleted Comment
You can totally change the license of already released code, if the change is compatible with the precious license or if you have permission from all the contributors whose code is still present in significant amount. (However, you can't prevent people from using the released code under the former license)
Android: long-press hyphen