emseetech | 3 months ago | on: JSDoc is TypeScript
emseetech's comments
emseetech | 3 months ago | on: JSDoc is TypeScript
emseetech | 3 months ago | on: JSDoc is TypeScript
Code written for a web browser 30 years ago will still run in a web browser today. But what guarantee does a build step have that the toolchain will still even exist 30 years from now?
And because modern HTML/CSS is powerful and improving at a rapid clip. I don't want to be stuck on non-standard frameworks when the rest of the world moves on to better and better standards.
emseetech | 3 months ago | on: JSDoc is TypeScript
emseetech | 3 months ago | on: JSDoc is TypeScript
Do you have anything specific in mind?
emseetech | 3 months ago | on: JSDoc is TypeScript
Modern HTML/CSS with Web Components and JSDoc is underrated. Not for everyone but should be more in the running for a modern frontend stack than it is.
emseetech | 3 months ago | on: Ask HN: How can I get better at using AI for programming?
This is the pattern I settled on about a year ago. I use it as a rubber-duck / conversation partner for bigger picture issues. I'll run my code through it as a sanity "pre-check" before a pr review. And I mapped autocomplete to ctrl-; in vim so I only bring it up when I need it.
Otherwise, I write everything myself. AI written code never felt safe. It adds velocity but velocity early on always steals speed from the future. That's been the case for languages, for frameworks, for libraries, it's no different for AI.
In other words, you get better at using AI for programming by recognizing where its strengths lie and going all in on those strengths. Don't twist up in knots trying to get it to do decently what you can already do well yourself.
emseetech | 3 months ago | on: Kidney Recipient Dies After Transplant from Organ Donor Who Had Rabies
emseetech | 3 months ago | on: 100k TPS over a billion rows: the unreasonable effectiveness of SQLite
And now that there are solid streaming backup systems, the only real issue is redundancy not scaling.
emseetech | 5 months ago | on: Why the open social web matters now
Payment processors underpin ad systems and they have strong leverage to pressure ad buyers and can pull your ability to make those sales. That's on top of the advertisers themselves having strong positions on what kind of content they want to advertise beside.
Everyone has to pay for servers somehow. Especially at scale. And doing that without payment processors is difficult. Crypto has not proven itself to be something consumers will use.
In all reality, the solution to as much free speech as possible on a social platform is to limit reach. If people want to broadcast to millions or even billions, then of course that will come with limitations and restrictions. Everyone has to balance the varied interests required to achieve scale. Limiting individual reach means more potential freedom for users.
emseetech | 5 months ago | on: Why the open social web matters now
Especially when engagement is the primary metric, which incentivizes our worst attention-seeking behavior. Well thought out, nuanced posts get lost in the ether. Hot takes, trolling and extreme positions get pushed to the top.
Reddit and HN mitigate this somewhat with the downvote system, which is hardly perfect, but at least means negative feedback is not given a positive weight in rankings.
emseetech | 5 months ago | on: Why the open social web matters now
And maybe users have a right to not be deleted without cause, despite it being a private platform. Maybe scale means that they have to play by different rules.
But what if the answer is reducing reach so only explicit followers can see what's posted? Do users have a right to being algorithmically boosted? Do they have a right to a wide audience? People who have had their reach reduced on instagram or twitter don't seem content to accept that but I don't see an argument against it.
In a federated system, spam and bots are a huge problem. One way this is handled is a shared blocklist. Something I toyed with was a propagated list like DNS to handle this problem, which would go a long way, but would also mean that being blocked by a highly trusted node could mean being blacklisted by the fediverse. This has already happened in a soft way when Gab was mass defederated. As the fediverse grows, automated tooling is necessary. Even if people have a right to contest being blocked, what's the reasonable mechanism for getting unblocked in a massive federated system?
emseetech | 5 months ago | on: Why the open social web matters now
But even then, that means there's resistance, but that's not the same as things being technically impossible. In federated systems, a delete is not a delete. It can't be because there's no way to confirm deletion on nodes you can't control.
And I understand your perspective as a realist on deletion generally, but that's not most social media users understanding when they're told they can control their own data, which is a common selling point of federation.
A centralized system which is properly incentivized to completely wipe all data associated with an account will be able do so, but a federated system can't.
emseetech | 5 months ago | on: Why the open social web matters now
And even if it works, there will still be carry-over of many of the problems we've seen with centralized social networks.
emseetech | 5 months ago | on: Why the open social web matters now
Even in a federated system, you can be blacklisted although it does take more coordination and work.
i2p and writing to the blockchain are an attempt to deal with that through permanence, but those are not without their own (serious) problems.
emseetech | 5 months ago | on: Why the open social web matters now
If I have 100 followers on 100 different nodes, that means each node has access to (and holds on to) some portion of my data by way of those followers.
In a centralized system, a user having total control over their data (and the ability to delete it) is more feasible. I'm not saying modern systems are great about this, GDPR was necessary to force their hands, but federation makes it more technically difficult.
emseetech | 5 months ago | on: Why the open social web matters now
| if you don't like the way Zuckerberg and Musk run things, too bad
It's important to note we're optimizing for different things. When I say third-order social effects, it means the way that engagement algorithms and virality combine with massive scale to create a broadly negative effect on society. This comes in the form of addiction, how constant upward social comparison can lead to depression and burnout, or how in extreme situations, society's worst tendencies can be amplified into terrible results with Myanmar being the worst case scenario.
You assume centralization means total monopolization, which neither Twitter or Facebook or Reddit or anyone has been able to do. You may lose access to a specific audience, but nobody has a right to an audience. You can always put up a website, blog, write for an op-ed position at your local newspaper, hold a sign in a public square, etc. The mere existence of a centralized system with moderation is not a threat to freedom of speech.
Federation is a little bit more resilient but accounts can be blacklisted, and whole nodes can be blacklisted because of the behavior of a handful of accounts. And unfortunately, that little bit of resilience amplifies the problem of spam and bots, which for the average user is much bigger of a concern than losing their account. Not to mention privacy concerns, which is self-evident why an open system is more difficult than a closed one.
I'll concede that "worse" was poor wording, but intractable certainly wasn't. These problems become much more difficult to solve in a federated system.
However, most advocates of federation aren't interested in solving the same problems as I am, so that's where the dissonance comes from.
emseetech | 5 months ago | on: Why the open social web matters now
If I were to build something like this, I'd use a services non-profit model.
Ad-supported apps result in way too many perverse economic incentives in social media, as we've seen time and time again.
I worked on open source decentralized social networking for 12 years, starting before Facebook even launched. Decentralization, specifically political decentralization which is what federation is, makes the problems of moderation, third order social effects, privacy and spam exceedingly more difficult.
emseetech | 5 months ago | on: Why the open social web matters now
I've also come to the conclusion that a tightly designed subscription service is the way to go. Cheap really can be better than "free" if done right.
emseetech | 5 months ago | on: Upcoming Rust language features for kernel development