Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
bascule
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
22 ms
·
151.
▲
by
bascule
10y ago
1) Numeric precision of integers is (under)specified in RFC 7159 section 6: https://tools.ietf.org/html/rfc7159#section-6 Note that when such software is used, numbers that are integers and are in the range [-(2
152.
▲
by
bascule
10y ago
For anyone interested in further discussing encoding type information about object members in the names instead of the values, there's an open issue on the GitHub repo for the spec: https://github.com/tjson/tjson-s
153.
▲
by
bascule
10y ago
Putting type sigils on object keys does not solve the problem of typing arrays, unless the types of array array elements are always homogenous, disallowed as the root symbol (they are presently allowed), and are always typed by their member
154.
▲
by
bascule
10y ago
Binary keys are useful anywhere data is named/identified by a cryptographic key or hash, such as content-addressable systems: https://en.wikipedia.org/wiki/Content-addressable_storage A keyring where the object me
155.
▲
by
bascule
10y ago
Go's JSON parser parses all numbers as floats, for example
156.
▲
by
bascule
10y ago
From RFC 7159 section 6. Numbers: https://tools.ietf.org/html/rfc7159#section-6 Note that when such software is used, numbers that are integers and are in the range [-(2**53)+1, (2**53)-1] are interoperable in
157.
▲
by
bascule
10y ago
That is not the case. Binary data is also allowed as the keys of objects (see https://www.tjson.org or the spec). As noted in the "Content-Aware Hashing" section, an intended future feature is to support redaction, so
158.
▲
by
bascule
10y ago
Ion is a superset of JSON: not all Ion documents are valid JSON documents. TJSON can be viewed as a subset of JSON: all TJSON documents are valid JSON documents, and parsed by existing JSON parsers. Consuming TJSON documents as JSON will in
159.
▲
by
bascule
10y ago
Compactness. TJSON expresses in 2 characters what you're taking another roughly 24 to do (omitting the "validation", which I think is unhelpful and pointless)
160.
▲
by
bascule
10y ago
Did you even read the post? First paragraph: "Its primary intended use is in cryptographic authentication contexts, particularly ones where JSON is used as a human-friendly alternative representation of data in a system which otherwise
161.
▲
by
bascule
10y ago
Floating points already have a distinct type. Many JSON parsers already convert number literals to floats in all cases. For ones that emit a mixture of integers and floats, converting to a float consistently is a simple transform. Floats ar
162.
▲
by
bascule
10y ago
It would require the standard to be clear that the only way to indicate integers is via "i:288", though, or there will be ambiguity. The spec does this here: https://www.tjson.org/spec/#rfc.section.4.3
163.
▲
Introducing TJSON, a stricter, typed form of JSON
(tonyarcieri.com)
140 points
by
bascule
10y ago
|
129 comments
164.
▲
by
bascule
10y ago
Just in time for TLS 1.3!
165.
▲
by
bascule
10y ago
Actually there was a Capnproto project for Ruby GSoC project this year! https://github.com/nemoNoboru/capnp-ruby https://rubygems.org/gems/capn_proto-rpc
166.
▲
Automatic-selection mechanism for data structures in MRI (Ruby GSoC project)
(spinute.org)
11 points
by
bascule
10y ago
|
0 comments
167.
▲
by
bascule
10y ago
While the benchmarks are looking a lot better than many other similar Rust libraries in this space, I'm not sure the code is in a state where they're actually meaningful yet: https://github.com/alexcrichton/fu
168.
▲
A gentle introduction to nio4r: low-level portable asynchronous I/O for Ruby
(tonyarcieri.com)
6 points
by
bascule
10y ago
|
0 comments
169.
▲
by
bascule
10y ago
Despite all the claims in the README, Curve25519 has in fact been standardized (at least informationally) by the IRTF CFRG in RFC 7748: https://tools.ietf.org/html/rfc7748
170.
▲
A tale of two cryptocurrencies: Ethereum and Bitcoin’s ongoing challenges
(tonyarcieri.com)
144 points
by
bascule
10y ago
|
73 comments
171.
▲
by
bascule
10y ago
to handle it without every service having a database connection to every other service's datastore you end up with something like a conversion step from Magic Model Object to a PORO, and that sucks wind. I actually prefer the distinc
172.
▲
by
bascule
10y ago
Oh, so you're talking about SOA / "microservices" and Claims-Based Identity (or rather, Claims-Based Identity is what you should be using). Well, an ORM is totally the wrong way to go about expressing user identities in
173.
▲
by
bascule
10y ago
I've been using service objects / operations in my apps pretty consistently for half a decade, but that's a red herring. That statement is about using AR to query and manipulate data, which is orthogonal to a service layer. S
174.
▲
by
bascule
10y ago
I've been using Rails for a decade now, across many jobs, and one thing I've experienced fairly consistently is the worst Ruby web apps I have ever dealt with are the ones that weren't written in Rails. I've both seen
175.
▲
by
bascule
10y ago
Yeah, it's puzzling why SpiderOak persists in using the term "zero knowledge" to mean something entirely different from ZKPs. As far as I can tell they're the only ones doing this too. Especially with zkSNARKs and practi
176.
▲
by
bascule
10y ago
Deterministic password schemes seem to pop up pretty frequently. Here's one of the most famous: https://www.pwdhash.com/
177.
▲
by
bascule
11y ago
45 days is a pretty reasonable and standard amount of time to give them after you attempted to notify them: https://www.cert.org/vulnerability-analysis/vul-disclosure.c... You might give them that amount of time, infor
178.
▲
by
bascule
11y ago
No software updates mean your device is vulnerable to e.g. Heartbleed forever.
179.
▲
by
bascule
11y ago
Cryptographers are mathematicians working in a limited problem space. It should therefore be no surprise that they converge on similar solutions (e.g. both RSA and D-H were discovered at GCHQ years before they were independently rediscovere
180.
▲
by
bascule
11y ago
X25519 is an elliptic curve Diffie-Hellman function and doesn't take a nonce. If you're asking about ChaCha20... yes, which is why nonce reuse misuse resistance is an important theme of CAESAR.
More ›