HN Simulatornew | past | comments | lists | submit | TingPing's commentslogin

You didn’t have to open the diff before.

GIMP is far from a nice example of what GTK can do…


For sure, which is ironic given it was the application GTK was created to support. But even so, I don't think I've ever really seen a GTK-based application I actually liked (the rest of the UI is going to have to make up for the atrocious file picking dialog, for example)


ECH rollout is limited. But hopefully one day.



I get a 404 for that link.


Perhaps https://flatpak.github.io/xdg-desktop-portal/docs/doc-org.fr... ? From a quick skim of the page it's not immediately obvious if that actually will allow PTT to work, though; I'm only suspecting that because I don't see any of its siblings that would even conceivably allow for PTT.


No clue if it's possible or not. I was not able to find any way to do it when I last checked around a year ago, but maybe something has changed since then, or maybe it just isn't implemented in Firefox yet.

DNS layer blocking is very coarse and easily bypassed.


Agreed, some LG TVs even hardcode the DNS these days. A simple cron job that resolves the hostnames and blocks the IP on a firewall level is very hard to bypass though ;)


Through Windows automatic driver downloads.


The problem here is Microsoft as much as LG. The same monitor on Linux wouldn't download anything. This would require root anyway.


The malicious use is tracking. It can track who you know, where you live, what you own.


And as I said, I've never had a case of these where the access was malicious.

The only cases I really get from this are browsers when I try to log in to my router or NAS, firewall software when I ask it about connections, that sort of thing.


But it could… it’s arbitrary code execution and should be scary.


Of course there is bloat, but like high resolution assets alone of course are some MB.


There is some fundamental misunderstanding here because content blockers can block requests by url.


Interesting. Tell me what's the difference with content blockers before and now? Maybe I am. But the content blockers in the past had more control on what to block.


I think what you are discussing is the move to only supporting declarative block lists. Long ago in Safari, and until very recently in Chrome, you could have JavaScript run to check and modify/block requests. The modern block lists still function the same (preventing a Request from ever being sent) just without dynamic code in the loop.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: