kroltan

The internet doesn't need to be the cloud.

Security cameras are the classic example of widespread self hosted but internet-accessible.

Even the ones that have proprietary apps are often just alternative frontends to a web server running on the home network.

If the time comes to discuss operating systems, I always suggest an exercise of downloading a Windows 11 Home ISO and installing it into a virtual machine, look at how much of it is installing an OS versus upselling into services using every dark pattern in the book. (With such hits as "the No button is hidden under a link-button called Learn More and only appears if you choose an advanced installation")

Once you're using it for >month, it's easy to see the BS as just an occasional inconvenience because saying yes is so much easier.

You would assume wrong, many (asshat) employers require them, so much that I actually have to screen that kind of sillyness when interviewing. Works a treat to filter out toxic workplaces, but exists nontheless.

As for leaking assets, maybe it does not affect the company at large, but that literally does not matter for this discussion. It will definitely affect your relationship, most often negatively.

And in any case, my usage of assets was clearly general, substitute the example for "clicking on the wrong stored tab while screensharing" can just as well lead you to leaking a plan.

And to spell it out:

- Stylesheet encoded as base64 in the Link header;

- Browsers always implicitly have at least the html and body tags;

- CSS cannot create new elements, but it does get 2 free pseudo-elements per actual element, ::before and ::after;

- CSS can set textual content for pseudo-elements;

So, it sets content to a pseudo element of an implicitly created tag, that's why the page is so minimal.

(Well, it could be up to 4 times as complicated I think, by using the other 3 pseudo-elements. Or cheat by using a big SVG as a background-image with more complex contents, but then you start running into header size limits and whatnot)

- Endpoint monitoring software may compromise more than it strictly needs to;

- If you're a contractor, risk of leaking other clients' assets (running `tree` in the wrong folder while screensharing or more subtle variations);

- Shredder policy, done with the work = destroy hardware (though I don't think companies with shredder policy would incentivise personal laptops, you never know)

The `field` keyword also already existed in C#, to add attributes to the backing field of automatic properties, so I think the argument was easier there.

I used it in Unity projects to have serialized/inspectable values exposed through properties:

    [field: SerializeField]
    public int MyProperty { get; private set; }

I think the issue with a very long line is akin to writing without punctuation because code is usually much more information dense than prose it becomes hard to follow what it is supposed to mean than if there were pauses for you to consider points in isolation but otherwise I don't see a problem with long lines if you have for example some very long silly OOP getter chain which is essentially one expression as for tons of nested blocks the general argument is it's a hint that your single unit of base indentation is doing too much and there is possibly something to be done about it though like everything it is usually taken to a unhelpful extreme.

Yeah, I've had to explain that a couple times already, usually when dealing with customer support or in-person registrations.

And a "malicious" actor can get away with pretending to be another company by spoofing the username if they know your domain works like that. I don't think this has reached spammers' repertoire yet, but I wouldn't be surprised.

Eventually I'd like to have a way of generating random email addresses that accept mail on demand, and put everything else in quaraintine automatically.

Not just CSS, it's used to set parameters but looks like the actual rendering is done in a <canvas> element controlled by JS.

Yeah I don't think I ever saw one either, but at least over here you can bring it over to a counter, or request an employee to turn it on and test.

Obviously not viable for evaluating continued operation for something like a fridge, but just turning it on for the panels is usually possible.

That's exactly the advantage of sneakernet shopping, you can ask to see the product in operation.

For e-mail addresses as an authentication tool, you don't really need to be able to send emails at all, just receive them, and I think that is pretty feasible to not run afoul of the usual shenanigans.