jeremie

5 ms·

1.
by jeremie 8mo ago
While did:plc was intended to be centralised from the start and under open governance ( https://docs.bsky.app/blog/plc-directory-org ), did: provided a framework to adopt other key resolution methods. As part of the IETF
2.
by jeremie 11mo ago
It was a different era 15 years ago, made some decent inroads on an API based approach with the Locker Project https://en.wikipedia.org/wiki/Locker_(software) but the platforms quickly started gimping the APIs and expo
3.
by jeremie 1y ago
I picked XML for Jabber in 1998, and at that time I think it was the best choice :)
4.
by jeremie 1y ago
I’m one of the (independent) board members of Bluesky and I can say with confidence that I don’t have any of these concerns, everyone involved is deeply aligned to the PBC’s purpose of “To develop and drive large-scale adoption of technolog
5.
by jeremie 2y ago
Great memories! Back in ‘98 I found a floppy with my original 1994 Netscape Mosaic v 0.93 Beta and shared a bunch of tidbits about it on my personal site (thank you Internet Archive!): https://web.archive.org/web/200104
6.
by jeremie 4y ago
I am also on the Bluesky board, and while the original funding did come from Twitter (at Jack’s direction), the company has no control over Bluesky and it is 100% independent.
7.
by jeremie 5y ago
> I do deny it; or to be clear, I think it is a story that we've been conditioned to prefer over the others Speaking personally, and perhaps it is indeed my conditioning, but at 25+ years of marriage I am living that beauty in 1 eve
8.
by jeremie 5y ago
This should be v0.1 based on the actual utility of the spec, just because it's been incubated for so long doesn't magically make it useful. DIDs are fundamentally antithetical to privacy and will only enable a deeper and more obsc
9.
by jeremie 8y ago
I’d say that it feels like just yesterday, but it totally feels like decades ago :) I’m very lucky to still be close with so may of the truly amazing individuals that helped build Jabber, and over the years deeply honored by all those that
10.
by jeremie 11y ago
As part of telehash v3, we've separated out most of the crypto/handshake packeting into E3X, which has a lot of similarities to QUIC: https://github.com/telehash/telehash.org/blob/master/v3&#x2F
11.
by jeremie 12y ago
I'm a big believer in a (local/p2p) transport encryption mechanism /in addition to/ one for auth, and for it to be transparent to any UX... that's very much our goals for telehash v3 :)
12.
by jeremie 12y ago
I've been on both sides of dizzyd's interview process and highly respect it, he should be a mentor to other software engineering managers on how to improve their hiring practices.
13.
by jeremie 12y ago
It would be nice if the README mentioned it was originally based on my https://github.com/quartzjer/js0n :)
14.
by jeremie 12y ago
I'm leading an effort for a pretty large refactor and cleanup of all of the existing telehash work (look at the commit history), honing in our mission and simplifying it's usability. We're trying to make it easy for any devel
15.
by jeremie 12y ago
It is indeed in the process of being refactored, to make it easier to adopt and use in parts.
16.
by jeremie 13y ago
A pretty relevant article about what myself and temas are working on now: http://www.theverge.com/2013/12/4/5173726/you-have-too-many-... IMO, interop/federation is going to be a tremendous long-ter
17.
by jeremie 14y ago
Pumped about this as well, it's the perfect packaging to quickly experiment with distributed sensor grids and be affordable to a hobbyist... pretty sure we'll see some cool "green" gardening (optimized watering), thermal/heating/cooling, po
18.
by jeremie 14y ago
Is there decent CoAP implementations? That's unfortunately one of the big stumbling blocks with universal p2p transport yet :/
19.
by jeremie 14y ago
With a telehash style distributed messaging bus you'd need to have clients opt in to centralized reporting and analytics providers, like the library of congress, internet archive, even commercial firehose companies like gnip, etc.
20.
by jeremie 15y ago
These are not my thoughts, but found them interesting and worth sharing...
21.
Bitcoin - implementation and protocol specs are a big problem(gist.github.com)
16 points by jeremie 15y ago|8 comments
22.
by jeremie 16y ago
It's a little on the young side yet, and I have to prove out some of the apps/demos of it at scale, but it's coming along very nicely and shows a lot of promise. Ultimately it's a public DHT that enables apps to punch through the NATs (to g
23.
by jeremie 16y ago
I've done my best so far to reduce it to it's most minimal required components to just get the job done, and in the last six months it's slimmed down significantly already, not sure much more can get cut out. My plan is to get some standard
24.
by jeremie 16y ago
Exactly, it's the only option left in order to let apps talk directly across the unwieldily myriad of network configurations (NATs).