8,274 karma · joined August 27, 2020
It's complex.
Generate a long-lived root keypair (SC/C), the public key of which you add to the forge. You never sign directly with this. Instead you routinely generate new signing pairs. If compromised you hopefully only need to revoke the subkey so the blast radius is a lot smaller.
You could even do a three-tier one where you can keep the root key dead cold and literally lock it into a vault.
Last time I looked, this was not supported in GitHub, though; it only recognized signatures by explicitly trusted keys, not their signed subkeys.
1. Versioned export/backup which will be guaranteed to work with current Colanode version
2. ..., well-documented
3. ..., with migrations so it's always future-compatible
4. ..., human-readable
I think integrations with any specific other tools should be ezpz if the fundaments are solid!
For import/insert, I guess some cli API with similar properties would be a nice fit.
(Coincidentally I think the above is also what would facilitate LLMs to do a decent job for anyone trying that)
Calling out a dupe comment[0] in this context is noise - no need for that either.
[0]: It already seems established that we don't do that for dupe submissions to avoid polluting the thread, which I guess is why you sniped the comment instead of the submission itself?
So Hegseth BYODd. Is that better?
So he BYODd. Is that better?
That's a separate legal argument and as I understand it not necessary to qualify a as monopoly.
The article says FTC is in a bind here.
IMO it's veey simple: Yes, FB shifted their focus and are now a content hose. They still have monopoly on some market(s) - not where they are competing with e.g. TikTok. Local events, marketplace, genuine personal social networks.
That doesn't mean that they don't also compete with TikTok elsewhere, where further market consolidation could be a concern.
Context matters. Population density of Japan makes it a different game.
> Writing the address on the envelope was awkward, as I haven’t used a pen in several years; it took a few attempts and some wasted envelopes, printing the address would have taken less time
Figuring out how to extract the GPS coordinates for a location (without having to deconstruct the URL or delve into devtools) after the latest UI rearrangement in gmaps has been turning into a regular a scavenger hunt...
This isn't complex stuff. With some regressions it's hard to tell what's negligence and what's actively user-hostile. My Occam's Razor is growing duller by the quarter.
For completion I think "cease to insecurely extract, aggregate and abuse all that user data" should also be mentioned as an alternative to the different ways they could skirt regulation.
Who knows what MCP looks like in a decade?
This is incorrect.
MCP is Model Context Protocol.
You didn't "build an MCP", you implemented an MCP server. Lighttpd is not "an HTTP", it's an HTTP server. wget is also not "an HTTP", it's an HTTP client. Lighttpd and wget are different enough that it's useful to make that distinction clear when labeling them.
dnsmasq is not "a DHCP", it's a DHCP server.
This distinction also matters because it is certain that we will see further protocol iterations so we will indeed have multiple different MCPs that may or may not be compatible.
I do not believe that corps make rational decisions around these matters.
There's a new kind of coding I call "vibe coding", where you fully give in to the vibes, embrace exponentials, and forget that the code even exists.
...
I "Accept All" always, I don't read the diffs anymore. When I get error messages I just copy paste them in with no comment, usually that fixes it.There's still some severe selective bias going on with what matters, what probabilities are discounted as insignificant, assumptions on cause and effect, etc.