Understood. I've skimmed over the thread and I admit I was wrong. For what it's worth, thank you for convincing me to take a second look and remove the flag.
Because it invites people to game the system. There are plenty of free lists and they overlap significantly. I'm pretty sure their intersection is also very similar to the core of the HN list.
You can do A/B tests to figure out what sorts of behaviors ride the line of triggering bans vs what kinds of behaviors result in an outright ban. It lets you optimize for just-trash-enough to not get banned, which is not a desirable end state for users.
> pretty easy to see when they don't get traction / get flagged automatically.
or they may think the content itself is the problem and spend resources trying to tweak it.
I think an analogous situation would be saying if the username/email is valid when there is a failed logged in attempt. Its a very minor thing but why give someone who is trying to abuse the system any help?
>or they may think the content itself is the problem and spend resources trying to tweak it.
A spam site knows it's a spam site. It's already tweaking domains and thats why the list is so big. It's relatively easy to buy new domains.
For the remaining 5-10% of legitimate sites I imagine HN isn't enough of a draw to care about tweaking content. They will save that level of curation for the Twitters, Facebooks, and maybe reddits in some cases.
>I think an analogous situation would be saying if the username/email is valid when there is a failed logged in attempt. Its a very minor thing but why give someone who is trying to abuse the system any help?
It does bring up the honest question of "how much do you inconvinence honest users in order to punish dishonest users"? And honestly it's a bit tiring to keep being assumed that I'm a dishonest user. If you trust me so little as to give an IQ test just to let me post a link (reducto ad absurdum), why would I bother as an honest user? Meanwhile the dishonest users will simply work around that or hire some cheap labor.
I think they just don't check. They just post to as many sites as they can. It's high volume, low reward. HN also has a small readership with a limited interest, so it's not likely to be a spammer's top priority.
The vast majority of all posts get ~0 traction. Even prolific posters of highly-upvoted links like todsacerdoti* are probably only getting around 1 in 10 to the frontpage at all, let alone for a meaningful period of time.
Have you ever checked /new? Not getting any traction is the default, not an exception. Plenty of submissions end up with no upvotes and very few clicks, hence plausible denyability.
I did this when I was a kid, decompiling a flash game client for an MMO (Tibia).
By itself a single decompile was hard to parse, but if you do it for each release, commit the decompiled sources, and diff them you can easily see code changes.
So you just run a script to poll for a new client version to drop and automatically download, decompile, commit, and tag.
I'd have a diff of the client changes immediately, allowing insight into the protocol changes to update the private game server code to support it.
these newly announced features are all inside the CLI, so i'm not how else to show an example project. After installing the CLI, you can run `supabase start` and it will pick up all the Migrations[0]. The CLI starts a local dashboard to see the logs[1]. After pushing to production you can run a backup[2], etc.
from your edit above, perhaps you were just looking for the docs but let us know if there is anything else you need
That's awesome! Thanks for sharing. I'll definitely use that from now on, great work.
One thing I noticed after creating a simple button component was that it does not export the font family of the text within but that might be a Figma limitation.
I don't see any arguing going on here, just a healthy debate about free speech balancing while still deploying spam blocking techniques.
This is a political and a technical issue. It's a fascinating problem with no perfect solution (yet?)