HN user
Software has a dependency contract that is quite unique. We can't imagine the shelflife beyond the Bazaar or Cathedral. They seem ever lasting.
The myth of impossibility remains, because we can't imagine what it means to forever occupy those places, even when others rise past them.
Alternative to resolving an image via Einstein ring lensing?
I think social graphs are often pre-disposed to capturing strong interactions only—an email chain, a trace-able back and forth (just as this), friend degree networks—not the off-hand conversations you overhead on the coffee corner, a tidbit you saw on a documentary awaiting a doctor's appointment, a faraway poster hanging on a museum wall.. you get the idea. Weak ties are everywhere! (Just not always recorded)
The weak ties were strong all along.
As far as I understand it, the storage is the space, or rather, spacetime emerges from a system's informational capacity and the degrees of freedom along which information can spread. On the balance all information is retained but undergoes various phase transitions (the 'computations').
There are two very lonely trains departing from Stranraer and Kyle of Lochalsh
it cannot have any ownership rights
Actor network theory sheds a tear. And more promptly: ownership rights are enacted via tools. Whether agentful or non-agentic, listing them would in the very least be similar to disclosing funding bodies or agencies.
Depends on what we value, I suppose; a depth-first style that surfaces isolated chains or a breadth-first style that surfaces interleaved replies.
Some authors may even choose to leave syntactical errors as a tell for those self-authored passages; long-term, some interesting language drifts may come of it.
Just as with redacted documents (consistently blocked terms) or bad OCR jobs (wrong or missing characters), even if only a certain percentage comes out unmangled it is more readable than having no data at all.
A stable base corpus and some dynamic programming will allow you to clean up the remainder[0].
Hence the cooldown period? I think the mechanism proposed here should be perfectly fine for targeted PRs, while mitigating those that sit above baseline.
Don’t make yourself regret the things you didn’t do
Nothing to add, but it bears repeating. A shimmer of indie tech resilience
The real unc is non-trendy so therefore new balances are non-unc, which makes them unc
Looking forward to using this[0] with Pluto instead of repl! (They just look so cool)
Single solutions/solutionistic approaches will likely be incompatible with either goal; consumer needs are always changing and collection capabilities expanding. Data scope and retention also need not be counter to consumer wants, and in the very least requires a mechanism that allows consumers to 'dial in' their preferences rather than wholesale accepting/rejecting terms of usage (i.e. a gradient instead of a binary).
I've yet to encounter a service that has implemented this successfully.
They'll only get you so far
I saved my desk from curb side collection. My chair idem. My laptop battery died two years ago so my desk cannot be too far away from a wall socket.
Maybe one day I could face my desk away from a wall.
Observable Framework[0] attempted to fill this niche for a while as well, and we'll likely see some of the implementation details in the new Observable Notebook 2.0 format too.
- paged.js[0] heeds the slow crawl towards the CSS paged media module, eventually allowing some truly great page-setting DX out-of-the box which it currently polyfills.
Maybe something more like a concordancer that provides valid or likely next phrase/prompt candidates. Think LancsBox[0].
Think Xstate[0] machines are a little more intuitive than the conditional value structuring displayed here in the example, but it is an interesting idea indeed.
[0] https://github.com/statelyai/xstate?tab=readme-ov-file#super...
And still, we apologised ('I hope this find you well' and so on). It's cruft, it's slack, and it's social. We need some anchors to hang our message on. We know when it's necessary and when it isn't, and by breaking conventions we relay intent ('sorry not sorry').
Pair this with Unicode plots[0] and you're set!
It's waves all the way down!
That is not what I said. It is about signalling risks to developers, not criminalising them. And in terms of encoders, I would say it relates more to digital 'form' than 'content' anyways, the container of a creative work vs the 'creative' (created) work itself.
While both can be misused, to me the latter category seems to afford a far larger set of tertiary/unintended uses.
I would say a text-based model carries a different risk profile compared to video-based ones. At some point (now?) we'd probably need to have the difficult conversation of what level of media-impersonation we are comfortable with.
Which in case of digital replicas that can feign real people, may be worth considering. Not a blanket legislation as proposed here, but something that signals the downstream risks to the developer to prevent undesired uses.
And I am talking about user-facing app development specifically, which has a different risk profile compared to automative or civil engineering.
Not saying this would be the right way to go about preventing undesirable uses, but shouldn't building 'risky' technologies signal some risk to the ones developing them? Safe harbor clauses have long allowed the risks to be externalised onto the user, fostering non-responsibility on the developers behalf.