There are ways to tell if an image is real, if it's been signed cryptographically by the camera for example, but increasingly it probably won't be possible to tell if something is fake. Even if there's some kind of hidden watermark embedded in the pixels, you can process it with img2img in another tool and get rid of the watermark. Exif data, etc is irrelevant, you can get rid of it easily or fake it.
I understand there are nuances here, and I may be oversimplifying, but if part of the contract effectively says "You must act as a proxy for npmjs.com" yet the site has been returning 500 Cloudflare errors across all regions several times within a few weeks while still reporting a shining 99.99% uptime, something doesn't quite add up. Still, I'm aware I don't know much about these agreements, and I'm assuming the people involved aren't idiots and have already considered all of this.
This is weird - at this level contracts are supposed to be rock solid so why wouldn't they require accurate status reporting? That's trivial to implement, and you can even require to have it on a neutral third-party like UptimeRobot and be done with it.
I'm sure there are gray areas in such contracts but something being down or not is pretty black and white.
Maybe because in airports people are sometimes required to walk long distances to go from one point to another, while in a city there are public transport, bicycles, taxis, etc. plenty of other options so walking long distances is usually not required.
I noticed that some screenshots were from 2008 indeed, but back then Ubuntu for example looked better than this (and so did commercial OSes at that time). I wouldn't mind that it looks ugly actually, but if they are going to emphasize that it's beautiful they better make sure it looks at least as good as other OSes (that make no such claim).
It's surprising they emphasize that it's beautiful in the page title, when it's really anything but beautiful. Even the alignment of buttons and text seems random, and the dock bar looks quite ugly.
In this kind of setup, I'm wondering how you handle events that happen outside of the component?
Let's say you have a background function, created with setTimeInterval, which after some time update an item. With Redux, you could dispatch an action UPDATE_ITEM, which would modify the items, and in turn update the connected component.
However, without Redux how is your component going to know about this item update and update the list? Do you use some kind of event listener/dispatcher?
Perhaps look at it a different way. We all know people who are not good at math. Sure they could spend days, even years, trying to improve their math skills. But even with such a huge time investment, they might be only, say, 10% better at math than when they started.
Was it worth all this effort? Maybe. However most people will think that they should probably have spent their time on something else.
It's pretty much the same situation for socially unfit types - why spend so much time on something they'll never be good at no matter how hard they try. In the end they would just end up being both socially and technically mediocre.