motolov
Re:Asymmetric Content Moderation in Search Markets: The Case of Adult ...
on Thursday April 24, 2025 @02:17PM (#43785772)
Interesting abstract.
I can see similar concepts applied to eg govt regulation, censorship, etc (only one side monitoring, other sides absorb content of the monitored)
BTW, it looks like your PDF is missing figures/illustrations/etc (there is placeholder text) Not sure if this was a publishing tech issue or if missed in authoring
Re:Show HN: PGlite – in-browser WASM Postgres with pgvector and live sync
on Monday August 12, 2024 @02:18PM (#41227622)
IME, creating scaffolding to allow for a known, reproducible and clean state (of both DDL and DML) are wild systematic (eg across the team and the estate) productivity and stability boosts. Not having to be "connected to the shared dev DB frees engineers of latency (every ms counts) and also of mutulple pollutants to that database (eg Sally was writing protractor/cypresss tests and now the foo table has 3m rows, george was doing data exploration and manually entered records to the DB that now causes a runtime exception fot the team, etc)
If a shared dev DB is really what everyone wants, then at least having the scaffolding mentioned above to fix the DB state when pollution happens (it will) will help heal foot shots. In industrialized practice, what you are mentioning (a shared dev/env) is really the "QA"/pre-prod environment. Ideologically and personally (putting on down vote helmet) if you can't run the whole stack locally you're in for a world of trouble down the road.. local first, test extensively there, then promote changes.
Re:Decentralized Clearing Network: A Protocol for Hybrid Decentralized...
on Wednesday February 20, 2019 @08:40PM (#19213817)
FYI DCN is mentioned but in the header you state DNC