Spyke

Replies

privacy

Comment on

Proton getting big encourages centralization

The average person is not going to sign up and pay for 10 different things, even if it's slightly more private. Proton is similar to Google in that it's free and has a lot of things with one account, but vastly different in the way the data is handled, probably the most meaningful difference. I mean the best thing you can do is self host but it's obviously not something everyone can or wants to do. So there's nothing wrong with taking the next best thing.

Comment on

*Permanently Deleted*

Reply in thread

No, it's expensive to comply (at a massive scale), but easy to avoid. Just change the user agent. There's even a dedicated extension for bypassing Anubis.

Even then AI servers have plenty of compute, it realistically doesn’t cost much. Maybe like a thousandth of a cent per solve? They're spending billions on GPU power, they don't care.

I've been saying this since day 1 of Anubis but nobody wants to hear it.

Comment on

We Mass-Deployed 15-Year-Old Screen Sharing Technology and It's Actually Better

This seems like a silly workaround at first but it's really not. If the network is unreliable, you can't really use normal video streaming, you need to send full screenshots. Probably still a better idea to use only I-frames than a bunch of JPEGs but whatever.

But they did make some very silly mistakes. Par for the course of an AI coding company I guess.

  1. WTF are you doing with 40mbps. Tone it down to like 8.
  2. If the network is reliable but slow, just reduce bitrate and resolution. Don't use JPEGs unless packet loss is the problem.
  3. WTF are you doing using a whole game streaming server for? It's meant for LAN, with minimal latency. Just capture the screen and encode it, send via WebSockets. Moonlight is completely unnecessary.
  4. Only keep the latest frames on the server. Don't try to send them all immediately or it'll fall behind. Wait for the client to finish receiving before sending another one. This way it won't lag behind increasingly. This should have been extremely obvious.
  5. H264 is so 2003, ask the client if it supports AV1 or HEVC then use that, more data for free.
  6. Use WebTransport when available, it's basically made for live streaming
  7. Why are you running a screenshot tool in terminal then grabbing the jpg... Unnecessary file overhead & dependency

I probably missed some but even for an AI company this is really bad

Comment on

MSNBC to rebrand

This looks like a fake TV station they'd have in a movie or something. Especially the logo...

If I had a nickel for each time a major company changed their logo from a recognizable bird to something completely generic, I'd have two nickels, which isn't a lot but it's weird it's happened twice

android

Comment on

How Android handles Hi-Res audio: An audiophile's guide to the best sound

Reply in thread

https://www.researchgate.net/publication/304572591_A_Meta-Analysis_of_High_Resolution_Audio_Perceptual_Evaluation

"Results showed a small but statistically significant ability of test subjects to discriminate high resolution content, and this effect increased dramatically when test subjects received extensive training."

Basically, people can just barely detect high res audio but it's not much better than a coin flip. If you have lots of experience you're more accurate but not by a whole lot.

Anyway 48kHz sampling can produce up to 24kHz and the human limit is like 20kHz. Most songs don't have 96db of dynamic range, and 120db is hearing damage, so the idea that the average person can easily hear the difference is not true.