New model comes out and someone says, "it can (or can't) draw ducks on bikes" or some esoteric thing. But it's not enough statistical power to claim anything other than a personal anecdote.
I got a flat tire in downtown today. Therefore, driving in downtown causes flat tires.
I have colon cancer. It's been a hell of a journey and my outlook is... not great. To me, this list seems practical but not profound.
It doesn't prepare you for all real stuff: you need to get ready to die. You need a plan for your trust, your estate, your funeral, and how your family will deal after.
You should have these plans in place before cancer because you could get hit by a bus. (I didn't because I'm stupid but maybe learned a few things the hard way.)
The fact that you’re commenting here tells me you have tremendous mental strength.
If I can add, for the benefit of other readers… One thing I learned is every case is different. Different cancer. Different body. Different support network. I’d suggest to anyone hit by this bus to never lose hope and keep an open mind about options (second opinions, calling in favours, moving, etc).
Wishing you all the best.
Most of the features are undocumented. I think because most of the behavior is not really defined and varies greatly between the different backends.
The backends are also not documented, you need to try out what's working and what isn't working. It doesn't explain the supported and unsupported features of each backend, neither their quirks.
A lot of behavior is surprising. For example if you have powershell in path on windows inside MXC it will just silently add the whole C drive with read-only permissions. Circumventing all other policies. https://github.com/microsoft/mxc/issues/1455
A lot of common error cases regularly happen and don't provide reasonable error messages. No documentation how to deal with them.
Check the issues on GitHub, there are many things that are expected to just work and they don't. One would at least expect some documentation why it doesn't work and where the limitations are: https://github.com/microsoft/mxc/issues
I disagree with that. MXC seems generally useful, but it's just poorly executed. I don't know about any cross-platform sandboxes that promise this kind of flexibility. There are always going to be differences between the backends, that's what makes it so complex, but equally useful if someone manages to deal with that complexity.
PS: velocity of the project is much lower than you would expect from a Microsoft project. It feels more like some hobbyist project, that deals with major bugs whenever the maintainer has time off.
Most importantly if the water table of the surrounding soil is high enough, it will lift an empty pool, even concrete. At most you would lower the water level below the lights. You’re likely getting wet either way.
Not necessarily, a non-SCUBA trained electrician may choose to bid the job with the condition that the customer drains the pool before the electrician starts their work.
I have some electricians that work for me with rope access training and certifications, sometimes we bid a job using rope access instead of a hydraulic lift if it’s cheaper to do it that way. It all depends on the project and your competition.
I use VPN most of the time. My work requires it, and I like Mozilla VPN for personal privacy. (Note: it has ad blocking DNS built in which is nice!)
I occasionally get blocked by websites or services, especially streaming apps, if I'm on VPN. I suspect they're just looking out for Amazon/Microsoft/etc IP address blocks. It's very annoying
That's not the same. You get blocked because the IP address you're coming from is associated with a VPN list, not because they're analyzing the traffic in detail.
The simplest methods block known datacenter IP ranges like you thought. More will score it based on several heuristics and a reputation over time. If you get 100 different users connecting from a single IP, it's probably not someone's home internet connection.
Mozilla VPN runs on Mullvad who are transparent and publish active server and IP lists https://mullvad.net/en/servers.so trivial to block them without blocking all of Azure/GCP/AWS[1]
There are also third party providers of IP annotations to classify known VPN address ranges that content providers typically subscribe to blanket block providers.
The reason for this aggressive approach is streaming apps all need your IP as core signal for tagging your region and all content licensing is region locked (even on YT).
Netflix are/were the most relaxed about it , and for long time would only buy content if they got global distribution rights, but not anymore. Many VPN ads specifically used to market that you can watch Netflix geolocked content.
[1] IME they block DC IPs too although not needed for blocking professional VPN, even self hosted OpenVPN on cloud box usually gets flagged.
That list is the IPs users connect to. It is entirely distinct from the list of IPs the VPN traffic egresses from. I doubt believe that they publish their egress ranges.
Don’t think there was ever a time since Netflix started streaming where they only licensed global rights to shows. For their own originals they get global rights but the majority of their content is licensed and has always been slightly different in different territories.
New model comes out and someone says, "it can (or can't) draw ducks on bikes" or some esoteric thing. But it's not enough statistical power to claim anything other than a personal anecdote.
I got a flat tire in downtown today. Therefore, driving in downtown causes flat tires.
reply