2,167 karma · joined March 5, 2009
Former principle engineer working at the intersection of Network and Security infra at FB/Meta.
Former SysAdmin at a small dialup/wireless/fiber/colo ISP in the US Midwest. Full stack where the stack went from datacenter power and cooling, fiber in the ground, to BGP, database perf tuning, and dev on backoffice/accounting/billing systems.
https://jade.wtf / https://github.com/jda/ / jade@jade.wtf
[ my public key: https://keybase.io/jda; my proof: https://keybase.io/jda/sigs/-MAdRvws8lprdF6WKGMur4GHTbctlG5hOtJvctF_rWg ]
He gave demand signal so many times years ago and was mocked for it and now we have the consequences of industry not taking him seriously.
Where are the web server access logs with source IP addresses and timestamps?
That's the kind of evidence that is needed to go to a provider's abuse department or sue to unmask the user behind a given IP, not attacker controlled (and falsifiable) strings.
LOVEINT has been a thing for as long as electronic surveillance has existed. We fire and/or prosecute people for it. We didn't turn out back on those capabilities.
I'd like to see someone using systems not available to the general public to to look up info on people without a legitimate purpose be treated as a kind of aggravated stalking.
Government employees should be held to a higher standard because they are in a position of public trust, but TBH people at companies like Google, Meta, Verizon, Comcast abusing internal tools for this should be similarly held accountable because they have access to resources far beyond e.g. one hobbyist logging TPMS IDs on passing vehicles.
We now have the tools to increase trust in specific information, for example: by signing images that need high trust for things like news reporting using camera hardware root of trust with time and geo stamping. If signatures are removed, that's back to a default low-trust state.
This isn't a problem for the vast majority of datacenters, and won't become a larger problem unless the anti-civilization mindset blocks infrastructure investment that's eventually needed even if the datacenter isn't built.
From the 00s to mid 2010s I did fiber splicing in factories from Kenosha to Beaver Dam and even then they were fairly well-automated to the extent that I’d see just a few people on the factory floor moving carts of metal between machines or handling shipping and receiving.
I think this comes down to how you go about asking. You have to take the time to understand what is and how it's seen by others by being curious, reading docs, etc instead of rolling in making assertions disguised as questions to assert authority like so many are wont to do.
I suppose it's possible that I'm the designated court jester and that's why I can get away with questioning, but I don't think that's the case :)
The answer can't be to put our collective heads in the sand.
E.g. I was able to get a /24 in the ARIN region in 2021 and could justify 2 more for a _logical_ network topology similar to what NK presents to the world.
APNIC similarly has a pool available for IPv4 allocations: https://www.apnic.net/manage-ip/ipv4-exhaustion/#the-situati...
Debian has docs on installing on at least one model of their arm boxes: https://wiki.debian.org/InstallingDebianOn/Synology
I run Debian on a few different models of qnap because their hardware occupies a niche of compact enclosure, low noise, and many drives.
You could have 100s of people who have a business need to look at syslog from a router, but approximately nobody who should have access to login creds of administrative users and maybe 10s of people with access to automation role account creds.
LFS does break disconnected/offline/sneakernet operations which wasn't mentioned and is not awesome, but those are niche workflows. It sounds like that would also be broken with promisors.
The `git partial clone` examples are cool!
The description of Large Object Promisors makes it sound like they take the client-side complexity in LFS, move it server-side, and then increases the complexity? Instead of the client uploading to a git server and to a LFS server it uploads to a git server which in turn uploads to an object store, but the client will download directly from the object store? Obviously different tradeoffs there. I'm curious how often people will get bit by uploading to public git servers which upload to hidden promisor remotes.
It would be more accurate to compare that side of Reuters to LexisNexus, Wolters Kluwer, or perhaps Bloomberg.
The statement that Anduril sponsoring a NixOS conference was inherently damaging as opposed to the reaction causing the damage, "When did defense work stop being taboo" etc.
I've worked in the US Midwest->SFBay->US West and defense work never seemed particularly taboo in my circles, moreso that the work was boring and constricting.
Traditionally cautious sectors adopting a particular technology seems like a sign that a technology is viewed as having a particular level of dependability. That's a good thing.
This is Tailscale's intended behavior, not a matter of how homelab folks like to implement it: https://github.com/tailscale/tailscale/issues/659#issuecomme...
Summary of thread: Society doesn't handle 2nd order consequences well. NK cryptolocker attack on healthcare-involved systems in British hospitals disrupted treatment to the extent that hundreds of people died who probably wouldn't have.
Expanding on that: Organized crime groups located in and sometimes tasked by RU SVR & GRU (not to mention NK state groups) have caused sufficient disruption to US healthcare systems to have indirectly caused more US Citizen deaths than the Sept 11 attacks. Right now cyber that does not directly cause destruction such as making buildings blow up or poisoning water supply is treated as just an annoying white collar crime.
I don't think anyone wants the US Government to be in a position where their options are to admit powerlessness or get proportional against nuclear armed states.
Somewhat related: https://blogs.icrc.org/law-and-policy/2023/10/04/8-rules-civ...
We're already well into causus belli territory with NK, but nobody wants to go there: https://x.com/tarah/status/1798036415932187127
For example: https://github.com/meta-llama/llama3/blob/main/MODEL_CARD.md
The fact that she did that on top of basically starting life over at 30 due to the constraints around transition at that time? That's winning a marathon with a cinder block chained to your ankle.
As far as the concentration of trans people in computing, AFAIK there are two predominant theories: First, survivorship bias involving careers that are often non-customer-facing and well-paying. Second, that there's common cause or comorbidity with other developmental differences (like ASD or 2SD+ IQ) that are unusually common among people who end up in computing.
Across ~4 doctors (1 PCP, 3 pysch), none have titrated up. They've ballparked and said things like "let me know and we'll reduce if you can't sleep and increase if it doesn't work. If you want, try doubling up or cut it in half (for non-XR)".
Given the variation in dosage visible in the literature (such as this case report of megadosing: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3407707/ ) I'd suggest that there are multiple underlying physical causes for the condition described as ADHD to the extent that sweeping statements like that aren't accurate. E.g. my (very different) experience and your experience being different indicates that we probably have different underlying causes, not that one is a myth or misperception and the other is the real take.
They are so unaddictive to people with ADHD that remembering to take them can be challenging.
With properly constructed automation and modern* hardware, you don’t need to do any manual config on-box for automation to be reachable. Zero-Touch Provisioning is a wonder to behold.
Modern being relative. I saw this work on routers terminating telco circuits nearly 20 years ago and had servers netboot and install the OS with basic config before that (though automation was far more tedious back then)