4,270 karma · joined October 15, 2012
Because there is a ton of work that people tend to perform that falls out the scope of that 'some'. And a lot of work requires alignment with other people, and so on. LLMs don't have agency, despite people hyping 'agents'.
I think what you hear is never the whole story, there is much more going on.
They may have shared a love for technology, what they also shared is a deep immaturity.
The immaturity of a person not wanting to acknowledge and cary any responsibility for other people, for the consequences of their work, for any kind of accountability. Just play with their toys without any concern for the external world.
'I'm just here playing with tech and code'. Sure! but that stuff you're building is being weaponised by other (the venn diagram unfortunately overlaps) tech bro's so men can film women with their glasses in public like the little sick creeps they are. Or steal all their data. You can't pretend you are not responsible and complicit.
They want "what's theirs" and anything in their way - including people - have to comply or be destroyed.
Lawmaker Cifrová Ostrihoňová said that, from a gender-based violence perspective, it is "simply unacceptable for any woman to worry about being filmed in public secretly and then worry about those images being shared online.”
100% thisWhere are all these machines from? Who owned them, and why? Why were they all there in storage, in a hangar. Would have been even more interesting.
How a new device bootstraps on the network without DNS? Depends, on the device, but a physical server doesn't need DNS, only PXE boot / TFTP / HTTP as usual and maybe a proxy to access an update server if you don't run one yourself.
That is absolutely true. I believe that a solution where you provision a text file with an updated ip address or /etc/hosts file is inherently simpler, less risky and easier to recover from, although I admit I don't explicitly state this in the article.
And I explicitly argue within the section about egress filtering that allowing systems access to public DNS is a security risk.
Yet, I'm not arguing for Facebook or similar size companies to ditch DNS internally. I'm making the argument for much smaller organisations to pause and think where their own risks lie and if it would make sense to cut out DNS to reduce risk. Whatever process you used as an organisation to update DNS in a safe manner, you still use with the alternative solution, that doesn't change.
That said, even an broken update to /etc/hosts is probably easier and faster to recover from than a broken DNS service that everything is tied to and due to TTL caching, can take much longer to resolve.
- DNS load balancing is not that important for internal services in most Cases? Would only use it if alternatives won’t work.
- the virtual host issue is really adressed by /etc/hosts, I thought that was obvious, I now regret not explicitly adressing it.