It took 2-3 hours, not 19. The first version was a static index.HTML file and was not exploitable. People found out and contacted the challenge author. After the fix was public it has been exploited in a couple of hours.
Padding is typically part of the hitbox, margin is not. What you are describing sounds like margin to me. Especially for Firefox since their UI is made with web tech.
But besides being overly pedantic I agree with your general point. If their is a small gap between hitbox and edge of the screen it is very annoying.
But the worst thing IMO is Windows 11 windows which you can grab by the titlebar but not the content area. However often there is no visual indication of where the titlebar starts/stops.
True, but considering that the extension was bought in 2022 by Avast, maybe it has its own tracking built in by now or will have something concerning done to it in the future. So even if the user does not care about cookies that much I would still recommend this new extension over "I don't care about cookies"
For panning you don't need a 3D view/reconstruction. This also allows translational camera movements, but only for nearby views. Maybe I am overly pedantic here, but for HN I guess thats appropriate :D
The problem is content exclusivity. It would be great if all the content or at least most would be available on all platforms. At least eventually. That would be great for consumers. Mergers like this typically not.
Another reason I can think of is the requirement not to introduce a breaking change. It is very frustrating if the codebase has a lot of hacky/bad code in it but a lot of it can't be changed...
Because updates don't just include new features but also bug and security fixes. As always, it probably depends on the context how relevant this is to you. I agree that cooldown is a good idea though.
I think the problem is that they cannot communicate that they don't know something and instead make up some BS that sounds somewhat reasonable. Probably due to how they are built. I notice this regularly when asking questions about new web platform features and there is not enough information in the training data.
A couple of years ago I played PUBG which crashed occasionally. I rarely submitted bugs, even if it was as simple as pressing a button in the crash reporter. This is because sending the bug report took a while and blocked you from restarting and rejoining the ongoing game. This applies mostly to multiplayer games but if your app has a crash reporter, give the user a chance to restart the app and report the bug later.
It's always impressive how far people can take TypeScript and even build parsers with it. But this is limited to inlined string literals and cannot read files (a TS limitation).
I wonder if the author has a use case in mind for this that I don't see. Like if you are only using TS, what's the point of protobuf? If you are exchanging data with programs written in other languages why avoid the protobuf tooling that you need anyway?
Maybe this is just a fun toy project to write a parser in TS?
In Germany LRAD systems have been used to deliver Covid 19 information, not against protesters. Used by the fire brigade. I haven't checked uses in other countries.
Why do we need tracking for advertising though? I wouldn't mind ads based on the page content (as much). Social media websites know their users anyways, no need IMO to track users across other websites.
You can use Google Play services on Lineage os. IIRC they are installed by default though there are ways to use it without them (doing that right now). About banking apps idk.
The Android App as well. I have a slightly older phone (Fairphone 3+) and it takes 10-15s for a song to start playing after tapping on it. Even if it's offline available. Didn't use to be that way. Also the app is basically the opposite of offline-first. Terrible UX.
Sounds like an interesting project, but I think it's important to find a good way to interact with browser APIs. They all work differently, like rAF, geolocation, pointer lock, camera access and so on. I think relying on the unsafe mode for all that could lead to a frustrating experience but also implementing those APIs in a different way would be weird and you have to keep up with new APIs and changes browsers introduce. I suggest having an idea on how to solve this before spending a lot of time developing the actual language. If it limits what I can do with JS I would not use this and just stick with Typescript.
IIRC extensions cannot access any URL that hasn't been specified in the manifests permission section. I think Firefox shows those URLs in the permission prompt. Those URLs can contain wildcards though and I even think there is a special value for all URLs but only few extensions should require that permission.
It's not quite that simple. For example the button doesn't necessarily have to have an aria label. Could be the (nested!) content. There could be multiple candidates (buttons). The speech recognition thing is also not trivial. Yes there are WebAssembly based solutions but those have to be properly integrated and tested (not sure how good they actually are)
Assuming this does not yet exist: If anyone is interested in building something like this (that works offline) please let me know, I'd like to join. I have some experience building web extensions but unfortunately not the time to develop & maintain this on my own right now.
I assume you are referring to the SpeechRecognition interface of the Web Speech API. Unfortunately this is not supported by Firefox and even for Chrome it doesn't work offline.
I'd also be interested in details on this but I assume the gl.enable() API changes fundamental things about the rendering pipeline. It allows enabling things like depth testing and stencil (both involve an extra buffer) and face culling (additional tests after vertex shader). For blending in particular I think it requires the fragment shader to first read the previous value from the frame buffer.
Changes this stuff is probably not a trivial operation and requires a lot of communication with the GPU which is slow (just a guess).
If you want to change blending for each draw call you can change the blending function or just return suitable alpha values from the fragment shader.