bascule

16 ms·

121.
by bascule 10y ago
I think this is an area where functional encryption could help: https://en.wikipedia.org/wiki/Functional_encryption This would allow a client to combine a server-provided function that calculates a spam score with thei
122.
by bascule 10y ago
This is a standard operator found in many programming languages, including ones with GC: https://en.wikipedia.org/wiki/Safe_navigation_operator To the contrary of what you're suggesting, I think Rust has done a gr
123.
by bascule 10y ago
No, this is a standard operator found in many programming languages, including ones with exceptions: https://en.wikipedia.org/wiki/Safe_navigation_operator
124.
by bascule 10y ago
Let's see, what does the article say? - Telegram isn't end-to-end encrypted per default: true - Telegram uses homebrew encryption (MTproto): true - Telegram presence information, at one point, could be read by someone who isn&#x27
125.
by bascule 10y ago
Does your work predate Stanford PwdHash? https://crypto.stanford.edu/PwdHash/
126.
by bascule 10y ago
There was OStatus: https://en.wikipedia.org/wiki/OStatus https://www.w3.org/community/ostatus/ Never went anywhere though, AFAICT
127.
by bascule 10y ago
I guess you still don't understand where this falls down yet: > The contacts which would be shared would be Signal contacts, identified by some public identifier like their phone number If Alice and Bob are just comparing their dire
128.
by bascule 10y ago
> It solves the exact same problems the Signal contact-discovery protocol solves, without actually revealing all one's contacts to OWS. Except it doesn't. If you share your contacts with Signal, it can tell you which ones are o
129.
by bascule 10y ago
The protocol you describe is a synchronous online protocol where Alice and Bob have to be online at the same time (and if they're doing this at Charlie's behest, so does Charlie). Signal is designed for asynchronous communication
130.
by bascule 10y ago
Ever since I got the Minilogue, my MiniBrute has been sitting in a closet. At the same price point you can get a polysynth with all sorts of polyphony modes instead of a monosynth. Kind of a no brainer.
131.
by bascule 10y ago
I've made a concrete proposal for moving type signatures exclusively to a postfix tag on object keys here: https://github.com/tjson/tjson-spec/issues/30
132.
by bascule 10y ago
1) TJSON imposes precision requirements on parsers which JSON lacks. It gives you guarantees where JSON doesn't. JSON may or may not lose precision when you go outside the RFC 7159 range [-(2^53)+1, (2^53)-1]. This is a potential sile
133.
by bascule 10y ago
I've opened an issue about using tagged strings for floats here: https://github.com/tjson/tjson-spec/issues/32
134.
by bascule 10y ago
> Just adding some fixed types doesn't really help that much. It brings the set of scalar types you can express in a JSON message on par with other serialization formats like Protobufs: https://developers.google.com/
135.
by bascule 10y ago
The purpose of TJSON is to be self-identifying and schema-free. If you want a schema, use Protobufs or the myriad JSON schema languages.
136.
by bascule 10y ago
Padding is redundant when base64url is encapsulated in a quoted string. If you're writing a state machine-based parser which is processing a quoted base64url it will, in amortized time, be able to find a close quote token faster than i
137.
by bascule 10y ago
No, but it has a set of machine-readable examples which are intended to cover JSON's present underspecified edge cases: https://github.com/tjson/tjson-spec/blob/master/draft-tjson-...
138.
by bascule 10y ago
The main reason to prefer protobufs is GRPC: there is now a pseudo-standard HTTP/2-based RPC format with many robust language implementations. That's mostly to say: I think I've generally observed GRPC being embraced. My inte
139.
by bascule 10y ago
So it's possible to specify a rigorous set of tests cases that, ideally if all are passed, can be used to certify a conforming implementation. In other words, to solve this problem: http://seriot.ch/parsing_json.php Wh
140.
by bascule 10y ago
S-expressions are great, and I'm a big fan of SPKI/SDSI, which used S-expressions in a security context. However, they have generally not gained favor in the greater programming ecosystem, whereas JSON has. TJSON is trying to tap
141.
by bascule 10y ago
Also note that the sinister problem here is that implementations which convert numbers to floats will silently lose precision when they overflow the range allowed in RFC 7159. This leads to quite subtle errors, and is why Twitter moved to e
142.
by bascule 10y ago
JSON is not defined in terms of UTF-8. That would be patently ridiculous, since UTF-8 is a serialization. TJSON is defined as a serialization format on top of a JSON-like data model. The TJSON spec originally used the terminology "Un
143.
by bascule 10y ago
Please see this issue for homogenous typing of arrays: https://github.com/tjson/tjson-spec/issues/23 Also based on the feedback I've received, I'm putting together a full proposal for moving all typ
144.
by bascule 10y ago
TBD: https://github.com/tjson/tjson-spec/issues/23
145.
by bascule 10y ago
TJSON doesn't add any of the things you just complained about
146.
by bascule 10y ago
I am curious if you simply missed the numerous places this post refers to CBOR? Such as this: There exists a binary analogue of JWT called CWT which is based on the Compact Binary Object Representation (CBOR) standard. Unfortunately you ca
147.
by bascule 10y ago
The zen of JSON is it's a schema-free, self-describing structure. If people can be bothered to deal with schemas, they can probably also consume the Protobuf serialization of a particular object. JSON is targeting a market that doesn&#
148.
by bascule 10y ago
Yes, this is a very important point, (T)JSON is self-describing in ways protobufs or other similar on-the-wire formats are not. Making sense of a protobuf involves both knowing what type of protobuf you're looking at in advance (protob
149.
by bascule 10y ago
No, far from "inventing ASN.1 again", TJSON could potentially be a very useful format for representing equivalent structures to ASN.1, similar to: https://github.com/google/der-ascii
150.
by bascule 10y ago
Responding to: EDIT: Looking at the spec [1] it seems to address some of these, but still indicates a strong confusion between data types (Unicode, rational numeric) and data representations (UTF-8, IEEE double). The format is described i

More ›