100 karma · joined April 25, 2019
One would also want negative results for aids, Covid, herpes, and bunch of others!
To me this ambiguity leaves the door open for challenges to the label "mandatory spyware" as a blanket label. With the ambiguity open, a plausible scenario is this: Only banks enforce IPInside, and Koreans can access full banking services from their mobile Android and iOS devices (with IPInside installed), meaning their laptops and PC's wouldn't need IPInside installed. Meaning: the label mandatory would be an overstatement. I'm not against the label mandatory, if... These gaps in knowledge are filled in with more info (forgive me if I it was clearly stated in the article for all to see! I read it the best I could but on mobile so who knows what I missed).
A kid pushed his last coin into the slot, 30 minutes until his parents come to collect him; he will prolong this game for as long as he can.
To me this reads as not mandatory in the broadest scope, but needs to be on whatever device people use for online banking.
A bit harsh I thought!
I know for sure I cannot complete a full ishihara plate test though so this one is on me.
Change my perspective if I'm wrong, but I'm not unhappy if the ps5 jailbreak doesn't happen until the EOL for ps5 online servers.
I think you're underselling the difficulty of this problem by the adverbial just.
I'm thinking this might be aimed squarely at scenarios where the editor, designer and admin are all the same person.
HAProxy is also really useful for this purpose, I dare say more-so. For my use-case it solved this problem: "Using 1 port on the remote server (port 443), how can I serve HTTPS (serve a website) and SSH or SOCKS5 (use the server as a proxy)?". HAProxy was good for the task. It could be used to tunnel SSH through HTTPS too, in the case where a corp firewall is using DPI to block standard SSH. What I'm not sure of though... can it tunnel SSH through HTTPS, and, serve a website at the same time? That's a question for the reader.
The idea of serving a website at the same time was for the purpose of providing a plausible reason for traffic exists from that server. Like, you know, if the admin's see traffic on 443 from an ip/domain with no website, that's got to be a magnitude of suspicion higher than an ip/domain with an actual website being served on it.
For me the IP address has been the only significant factor in my email deliverability. I.e., emails sent from my mail server couldn't reach Outlook inboxes or even spam boxes. Straight-up silently rejected every time. If you look at the Outlook.com Smart Network Data Services (SNDS)[0], the terminology used is all about IP. That problem was resolved through a support ticket requesting a kind conditional white-listing.
That's been my experience so far, from the perspective of a low volume, personal email only. YMMV.
>I was actually amazed...
You countered your own argument there.
An obvious other counter would be 3D engine development (Unity, Unreal) where the developers of those engines will be employing some obscure seeming low level stuff to make this look good. Not to be unclear though I'm 100% in agreement that for most devs, those days are mostly over. [0] https://youtu.be/5XOV3pZj8rI
The words unblockable and uncensorable have been misused in the documentation.
Real-world example: 99% of my colleagues cannot bring their own devices into our corporate workplace to access torrents via DHT. There are some network rules and filters in place to block most non 443 traffic. Those 99% are effectively blocked.
Setting a remote HAProxy server to mask miscelaneous traffic as https was a practical way out through the firewall, which then exposed my HAProxy server to a block by IP rules.
This is an idea I'd love to be wrong about. Bock-resistant is the most appropriate statement for this project in its present form. Change my mind :)