This is what the actual marketing photo looks like btw Most other pictures of the inside also look like this, I think the other photo sliced them with a sharp knife

It had me until the flower button. Doordash would never

There’s a button “Show Bookmarklet and Settings Data” that saves all the settings to query parameters

No, those are known issues with Firefox for Android. They’ve been around for years now, but are not common enough for Mozilla to actually address them. The blank tab thing is what forced me to switch. Sometimes an existing tab would break permanently, had to close and undo close, lose all the page state.

And it’s slower, and it doesn’t have a tablet UI… sucks but it’s not an option for me.

Oops. I meant the modern method is better if network is reliable. Not unreliable

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.

WTF are you doing with 40mbps. Tone it down to like 8.

If the network is reliable but slow, just reduce bitrate and resolution. Don’t use JPEGs unless packet loss is the problem.

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.

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.

H264 is so 2003, ask the client if it supports AV1 or HEVC then use that, more data for free.

Use WebTransport when available, it’s basically made for live streaming

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

The modern method is more efficient if your network is unreliable.

Modern: I-frame (screenshot) then a bunch of P-frames (send only what changed). If a frame gets lost, the following frames aren’t really usable, frozen until next I-frame Old: Send only full screenshots. Each frame has all the data, so losing one doesn’t matter.

Why ipv6 only though? Is there something about it that makes it more resilient to DDOS? If a device on the botnet has both ipv4 and ipv6 I don’t see how it’s mitigated