toomim
In order to account for that, you need you know how many people who are less likely to respond are voting for that candidate. And then you're back to square one.
This is why professional polls have had a consistent bias over the last few years, as this hidden unobservable factor's effect has gotten stronger and stronger.
- https://github.com/aflin/iroh-webproxy
- https://github.com/n0-computer/iroh-proxy-utils
No port forwarding. No public IP required. No special proxy to set up.
Iroh already runs public relays. Your two computers will signal through those, and then port-knock and form a direct connection to each other, perfectly encrypted.
We just need to define a new https:// url, like ... let's call it "irohttps://" maybe, so then you could contact my laptop with "irohttps://<hash>/path?query".
The problem is that today's peer review, while better than nothing, is far from a perfect judge of research quality. If peer-review was a perfect judge of research quality, there would be no incentive problem. The incentives would be aligned.
I happen to be working on an improvement to peer review. An early prototype can be viewed at https://peeryview.org/about. Holler at me if you're also working on this problem!
It means AI that is General, as in it is not specific to one narrow task, like object recognition or playing chess.
This was a hard problem for decades. No AI was general, until GPT 3 or 4. Now we have General AI.
So we have AGI.
Yeah, right.
That's a threat to civilization.
Say this in a deep masculine dramatic voice:
One man. One gun. A story that would could never die.
Compare that with this Coldcard page: Two files, four lines, five years unnoticed. This is the COLDCARD
entropy failure
It's trying too hard to replicate a dramatic movie arc with every... single... sentence...Both drafts request a subscription with a GET plus a header:
Scroll Request:
GET /scroll/feed/customers
Prefer: stream
Braid Request:
GET /customers
Subscribe:
In both systems, the GET leaves its response open to stream events. SCROLL responds with application/x-ndjson. Braid subscriptions are a 209 Multiresponse, with content-type application/http-history. This lets them support more than just JSON. You can send updates to the state of CSV, or PNGs, XML, HTML, plain text, or any media type.The author noted that it's hard to get adoption. Well, the reason that Webhooks are so common is that they are bog-standard HTTP. For this to get adopted, we need to put it into bog-standard HTTP. So we need to go to the IETF, and and extend HTTP in a general way to support state synchronization. It should just work for any existing HTTP media type (not just JSON), and any resource/URL (not just special /scroll/* URLs), and any way of marking timestamps (not just the ordered strings proposed in SCROLL).
Then we can bake this stuff into HTTP, and thus into all our bog-standard libraries, utilities, and code, and you won't have to reimplement the same sync-logic-over-webhooks again, and again, and again.
Reach out if you're interested!
In BlueSky, there is only one single "AppView" instance in the entire network. There is one instantiated "Firehose". Each user can instance his own "PDS".
In ActivityPub/Mastadon, the instances are "sender's server" vs "receiver's server."
The difference isn't that there aren't "instances" in AT proto. It's just that the instances are segmented differently.
This is a M1 macbook air. I really want to try this.
1. WASM FFI has a big overhead when interacting with the javascript DOM.
2. Any DOM UI has a big overhead compared to a canvas.
I would be curious to see an actual performance evaluation. This looks like it was built for the wrong tradeoff otherwise...
Freenet seems to not interoperate with the existing WWW as much, while at the same time giving more specification on a specific routing and WASM validator. The existing WWW and Braid leave those decisions up to each particular host/authority to decide.
"Good designers will reject this."
^ Famous last words.
Look it up: https://pijul.org
It also makes cherrypicking and rebasing wayyyy easier. You can actually add or remove any set of patches, at any time, on any peer. It's a dramatic model shift -- and is awesome.