HN user

CasperDern

35 karma
Posts7
Comments22
View on HN

They used a fixed size transformer, where the vocab determines the functions and input/output range. So unless the model needs more 'memory' for your class of expression there wouldn't necessarily be a big change in performance. They have experiments in the paper with bigger/smaller vocabs.

UI looks nice but is janky. Documentation is lacking, but sufficient. Longhorn works great (if you ignore CPU usage due to syncing when there's a lot of IOPS). Overal though self-hosting it has been pretty great for us from a usability perspective. Not sure if it's as enterprise-ready as they say though. Also haven't had to deal with their sales/support (yet).

IANAL, but I think "to the extent allowed by the law" is a way to allow an overreaching (doing more than the law allows) contract to not be fully voided. It effectively allows you to specify ideals, but also means that the license my not work fully as intended.

Unsigned does not mean "not negative", it means "modular arithmetic".

Unsigned does mean non-negative (or rather no indication of negatives) as the sign of a number is just the positive or negative factor of a number: 1 or -1.

It's actually an interesting discussion. After thinking about it for a bit, it seems like Google is a search company fronting for it's own ad business. In the early days their core technology probably was search but at this point it's likely adtech. At this point it doesn't matter if their search is bad (it's probably better if it is bad, as more time is spent seeing ads) as long as they are the dominant/default search engine for the general public.

There are a lot of opportunities for a better search engines but very little incentive invest into making it so.

I recommend watching this interview with the creator of NFTbay, there are a lot of misconceptions on it's current usage.

TL;DW: it's an immutable representation of some data (usually a hyperlink), put on to a public blockchain such that ownership of this representation can be verified.

Not much different to a regular certificate just different trust assumptions (certificates use a trusted party, while NFTs use a "trusted" technology).

HTTP/3 Is Fast 5 years ago

I do not know about cloudflare's internals, but I believe the 6 connections limit is purely a browser thing. So it should be able to do as many connections as it's able to handle.

Not an expert, but I don't think it's necessarily a weakness in the current applications of cryptography. In something like RSA a typical key is >=1024 bits, which is 1.7e308 possible number so even though primes are more "limited" the actual reduction in security (if non-primes could have been used by magic) the primes that are left are still plentiful. One reason RSA is not really used anymore is because other algorithms such as elliptic curve cryptography provides much better efficiency (partially due to it not requiring primes keys). So it's less efficient than more modern technologies, but not necessarily weaker.

It's been a while, so I'm not sure if it will work on the newer models, but I used to use the xtensa-lx106-elf (patched from crosstool-NG[0]) toolchain to build my ESP8266 project and then upload it wil esptool.py. There was also esp-open-sdk which was an installer for that toolchain and some additional libraries[1].

[0] https://github.com/i404788/crosstool-NG [1]: https://github.com/pfalcon/esp-open-sdk

The customer scans the code, sees the amount to be debited, and presses OK. The amount then moves from one phone to another without the need for WiFi or another wireless network

How does the business verify a transaction was successful? It seems like information only flows one way.

RSA is pretty easy to implement, but hard to get right, PKCS#1v1.5 can be broken using padding attacks, and should not be used. OAEP is generally recommended.

The entire RSA suite (keygen, encrypt/decrypt, padding) can be implemented in about 300 loc[1]. Which is probably why there are so many of these 'walkthroughs'.

[1] https://github.com/i404788/tiny-rsa