Asternova @ultranova@cybre.space

It is hell.

Work offered to buy us a laptop. But I don't FUCKING know which one to get. All of the suggestions this far either do not fit our aesthetic goals or do not fit our price goals (sub-1k) or do not fit our performance goals. Or have weird fucking issues.

Are there any good new Thinkpads

My computer is always slow and sleepy after waking up from a nap :((((

> The tables necessary to do full and proper unicode case folding are larger than the whole SQLite library.

lol

What I haven't seen thusfar is an assessment of the types of bit rot on storage mediums. What form does bitrot take? Literally nobody knows

LDPC is actually perfect because it gets as close to the Shannon limit as is possible (there's still room for improvement)

To expand on that last point: The pinnacle of anti-corruption software consists of both turbo encoding and LDPC encodings. But the problem with that is if you have a huge single chunk of the data wiped out, those codes fail. They're designed for variable errors in a bitstream, if someone runs a pin down a strip of the magnetic tape or whatever you're using, you're stuffed

And because each individual byte only contains a blisteringly small part of the overall structure, it's resilient to certain types of corruption (There is actually no 'one size fit all' corruption mechanisms)

This is why plain text is actually the best *in general*. Although corruption is difficult to spot, it's blisteringly easy to repair by hand because our entire mind is built to recover context from partial-context situations

Arguably you want the least amount of data per byte, because then when Corruption shows up, it has less of a chance of removing information :V

I'm still not really sure if I should archive to a database or archive to just plain text. I'm more experienced with the latter, but it seems frustrating to lookup with these at least

Well that works :)

Needs a better name tho

Does this even take max_id? According to the documentation, no. But WHO KNOWS because the documentation is LYING

If you add a feature please add it to the documentation at the same time. Please for the love of god do that.

Added: min_id

*does not have min_id in the list of valid arguments to the request*

??

> Because the id of a favourite is not public, an HTTP Link header can be parsed for next and previous pages.

What the fuck

Seriously. What the FUCK