Firefox+PlasmaWayland+SystemD+portage+GNU+Linux
Keyoxide: aspe:keyoxide.org:KI5WYVI3WGWSIGMOKOOOGF4JAE (think PGP key but modern and easier to use)
Firefox+PlasmaWayland+SystemD+portage+GNU+Linux
Noone noticed because noone reads the articles.
We really need an autodr bot that justs pastes the text verbatim like:
This is the best copy I could come up with:
[…]
The original article contains 568 words, the copy also contains 568 words. Saved 0%. I’m a bot and I’m open source!
More so, if it is easily sandboxed, it should just be a webapp. Which discord already is.
Just use the website.
Browsers are already easily themed, have plenty of tools to change deeper functionality, and are way more sandboxed than any other app packaging ecosystem.
PHP has ben JITed for a while now too.
I don’t recall it being known as slow compared to python even before that.
I think the correct tool for my purpose would be something like Popup window, if you care about that part.
SSB is still around, but also not what I was looking for. I just wanted a frameless window (and no other pwa functionality).
Fullscreen I disabled using my window manager. Under Linux you can commonly use alt+F3 to bring up the “right click on titlebar” menu, then disable fullscreen there. Generally ever window manager can disable fullscreen for windows, in a more or less accessible way (cough ms windows dll calls cough).
As mentioned below, This is recovery. I could ban kiosk mode to a separate profile, but unless you invent a time machine this won’t undo having opened kiosk mode in an in-use profile.
Yes, this is more of a recovery operation. Whatever the fix may be, modifying the browser itself to open a window without decorations would be easier.
There are some usecases in which you really don’t want to restart your browser.
The easiest way to update your kernel is to restart your pc, yet there is a market for live-patch kernels.
If someone accidentally infects their instance with kiosk, it may occasionally be preferable for them to follow a complex procedure to recover the instance, rather than doing the “simple” thing of restarting it.
Restarting may solve many problems, but there is a more difficult but less invasive solution almost every time.
Much like reinstalling may solve even more problems, but you can see that doing a reinstallation is not usually the right course of action.
Kiosk mode doesn’t just force fullscreen, it disables right click, the tab and title bar, …
Basically the browser is close to unusable until kiosk mode is ended, which I currently only know how to do via restarting Firefox.
And F11 is also disabled by kiosk mode. Interestingly, on the windows that were started before kiosk mode, it puts them into proper kiosk mode (after which F11 stops working of course).
I had the same on revanced, thought they found a new way to fight adblock.
Turns out if you clear the cache occasionally it goes away. The youtube app is a piece of trash.
I would switch, but I only use it for music and I haven’t seen another frontend support mixes, which I rely on
Electricians will deny this is true but then just make up a new word for it (inductance)
This really seemed like a good simplification until you threw in that d’Alembert operator at the end
Default linux works too ofc, I didn’t know they took that route.
Most other browsers have very specific useragents, so the main pool of same useragents will be hardened browsers anyway.
Thank you for checking
edit:
https://github.com/TheTorProject/tor-messenger-build/blob/581ba7d2f5f9c22d9c9182a45c12bcf8c1f57e6e/projects/instantbird/0001-Set-Tor-Messenger-preferences.patch#L354 would indicate it should be Windows, Ill check later.
Try it with high security settings in tor, it might be something like canvas. Did you enable any permissions for the website?
That would be a fail of the fingerprinting protection. A properly set up TOR browser for example should not allow that detection by any means. If you know how to detect it, please report it as a critical vulnerability.
I could think of maybe some edge case behavior in webrenderer or js cavas etc., which would mainly expose info on the specific browser and underlying hardware, but that is all of course blocked of or fixed in hardened browsers.
Further, if you have a reliable method, you could sell it off to for example Netflix, who are trying to block higher resolutions for Linux browsers but are currently foiled by changing the useragent (if you have widevine set up).
That can’t have been the reason, rather the fact it could tell.
Your browser sends information about its version and the os in the useragent string. It is supposed to lie and say it is a very commonly used useragent, specifically for purposes of fingerprinting. That would be windows, default configuration, firefox version something not you firefox version
To be able to catch that, you need tracking. Some identifier to determine if you had 1000 authentications from the same source or different ones.
Neon Genesis Sonic