2,154 karma · joined February 1, 2013
Well, in many such situations data is provided for free, putting huge burden on the other side. Even it it's a little bit less convenient it makes service a lot more sustainable. I imagine torrent for free tier and direct download as a premium option would work perfectly
than inconsistent but sometimes correct.
Braindead YouTube-solution would be to buy this device, connect to TV, wireless mouse and install Windows 10/11 LTSC, install firefox + favorite addons. N100 is barely enough for 4k@60, and Ryzen gets a bit more juice to live comfortably
Windows does a lot of useless crap in the background that kills battery and slows down user-launched software
P.S. Swift, anyone?
Many protocols can use https ports and packet envelope. Also, there's special censorship resistant VPN protocols, which work even in China despite its nigh-infinity money to block it via DPI
2) Plain old sqlite seems like a good idea, for a format (and also widely supported). Fast indexes included
3) combining (1) and (2) is probably a good idea as well
4) there's also Parquet
Most useful information would be to not confuse it. E.g. you see a event date 9/8/2025 and it's either tomorrow or a month from now. Perfect 50/50% chance to miss it or make a useless trip
The thing is, it's almost impossible to guarantee payments work as expected in decentralized system, see "double spend attack". Bitcoin was designed to prevent it but does it by having common ledger which is a bit too much for a chat
See various charts. For example, this table:
https://res.cloudinary.com/cloudinary-marketing/images/f_aut...
For decoding,
Webp - ~70Mpx/s,
jpeg - 100 to 300 Mpx/s
Jpeg xl - 115 to 163
Avif (single thread) - 32 to 37
Avif (multithread) - 90 to 110
> An obvious example of this would be incorporating a texture
Some random range of storage data is now the texture. It was used to process formatting logic but now also a texture
Or awful lot of text information (state of art compressors can do up to 1:10 ratio for plain text, decoder itself is rather small, 750MB compressed could potentially contain like 7GB of text data).
Also, look at demoscene. 4k (4 kB is the size of executable) can do crazy things, and 64kB can fit a lot of nice 3D objects, music, text, complex effects etc. weight less than any screenshot of any moment of running demo. In 95kB you can have full game (google kkringer)
P.S. better example: full snake game in 56 BYTES https://github.com/donno2048/snake
For comparation the link above is 34 bytes, whole sentence is 83 bytes. It's possible to do a lot if we're talking about code