bananapub
bananapub on Hacker News
> April 28, 2026
> GitHub Enterprise Server customers should upgrade immediately - at the time of this writing, our data indicates that 88% of instances are still vulnerable
> Upgrade to GHES version 3.19.3 or later
https://docs.github.com/en/[email protected]/admin/rele... :
> Enterprise Server 3.19.3 - March 10, 2026
88% of on-prem customers haven't applied a critical security fix from 7 weeks ago, that seems ... bad.
I'm asking about the infrastructure, obviously they chose for some reason to make my computer fans turn on to show some red and green lines on a text file.
> Git is pretty simple internally, and its ui is just knobs and levers to reach into that simple reliable internal structure.
that's not true either. originally it was simple internally - it was mostly shell scripts! writing text files! - but now it has all sorts of complicated optimisations.
the "middle" is somewhat simple for CS people, though - a graph of commits, you can put labels on them, you can send and receive strict appends to the graph to another repository. both the stuff under and above that is quite complicated in practice, but the UI does continue to improve - e.g. editing a past commit message until the release last week was ... complicated.
anyone who's actually worked there, could you explain why they're finding scalability and reliability so hard? naively it seems like 'repo groups', ie clusters of repositories linked by being mutual forks, would be fairly isolated for the whole git storage layer, and everything else feels pretty easily parallelisable (issues, actions, etc, modulo taking locks now and then to submit results or whatever). and given that, surely you can incrementally deploy changes across those many shards to avoid most big outages?
are there big conceptual serialisations that I've missed? is it just not well factored? was the move to Azure just a catastrophically bad idea? some other thing?
why did you make it so complicated? magit has a `magit-wip-mode` that just silently creates refs in git intermittently so you can just use the reflog to get things back.
would diffusion models benefit from things like Cerebras hardware?
of course not, but it can often give a plausible answer, and it's possible that answer will actually happen to be correct - not because it did any - or is capable of any - introspection, but because it's token outputs in response to the question might semi-coincidentally be a token input that changes the future outputs in the same way.
> Do you get updates to the proprietary software stack if you go without a subscription license?
what proprietary software stack? they just publish it all on https://github.com/oxidecomputer/ .
ipv4 space is scarce, people who have it want money to let other people use it.
it's definitely not $US10 000 for a /24 anymore, though, more like $7000.
you can also lease one for $100/month.
or just stick with ipv6 which is approximately free.
something like ~100eur/year to have an AS via a sponsor with RIPE + whatever compute and network you want to use with it, ranging from 3eur/month VPS to renting your own racks or whatever.
incorrect.
- you can get an AS with RIPE by being sponsored for ~100eur/year, which does require you to be multihomed since an AS is no use without that
- you can lease IPv6 space for < 10eur/year from someone and then get someone else to announce it for you
- you can get PI space from RIPE for ~100eur/year but that's not very useful without an AS and not anymore useful than the leasing above for 1/10th the price
it's simpler than that - making it faster means it becomes less of an asynchronous task.
current speeds are "ask it to do a thing and then you the human need find something else to do for minutes (or more!) while it works". at a certain point at it being faster you just sit there and tell it to do a thing and it does and you just constantly work on the one thing.
cerebras is just about fast enough for that already, with the downside of being more expensive and worse at coding than claude code.
it feels like absolute magic to use though.
so, depends how you price your own context switches, really.
which won't be surprising if you think about a little bit - 8.8.0/24 is anycasted, which just means that multiple independent locations around the world announce the IP range, so that your requests broadly go to a nearby instance of it. that's great for your inbound requests, but if it
originated it's own DNS queries from that IP, then the replies would also get attracted to whatever instance of 8.8.8.0/24 is near the authoritative DNS server it just queried,
not the instance of 8.8.8.0/24 that sent them.
also, even aside from that, having some large fraction of the entire world's DNS requests coming from one IP address would trigger everyone's anti-DOS filters and probably lead to some extremely funny router catastrophes as all traffic hashes to one bucket or whatever.
yes, OPs one has strictly less listings (diskprices.com does multiple countries).
why would you look at the "front page" if you only wanted to see things you subscribed to? that's what the "latest" and whatever the other one is for.
they have definitely made reddit far worse in lots of ways, but not this one.
> I have ADHD. I think.
then think about talking to a medical professional, and a therapist, and coming up with your own coping strategies.
> How do you manage the constant stream of thoughts and ideas?
take notes of ideas and come back to them later when you have time.
Someone should IARC the internal one.
anything critical of the US regime is almost immediately flagged and downvoted.
it's uh pretty confronting!
I mean, yes, you should do things you enjoy as a hobby? and not do them if you don't?
it's very silly to analyse trivial hobbies this much; if you want to write a thing, do so.
yes, obviously?
anyone who is doing serious enough engineering that they have the rule of "one human writes, one human reviews" wants two humans to actually put careful thought in to a thing, and only one of them is deeply incentivised to just commit the code.
your suggestion means less review and worse incentives.
just another happy customer, from so long ago I can't find my signup email anymore. very glad there are still companies who just do a thing well without trying to tie me up with them further or cross-sell or sell themselves or make the product worse.
keep up the good work!
if you want anything other than "switch to another full terminal window, no splits, no status bar" then you want tmux or screen or zellij - this tool and the others like it are explicitly avoiding becoming (nested) terminal emulators like tmux and screen and zellij.
at least I think it would be possible to do "switch to another full terminal window, no splits, no status bar" without being a terminal emulator, I haven't tried.
for those looking for a simple and reliable self hosted S3 thing, check out Garage . it's much simpler - no web ui, no fancy RS coding, no VC-backed AI company, just some french nerds making a very solid tool.
fwiw while they do produce Docker containers for it, it's also extremely simple to run without that - it's a single binary and running it with systemd is unsurprisingly simple[1].
0: https://garagehq.deuxfleurs.fr/
1: https://garagehq.deuxfleurs.fr/documentation/cookbook/system...
it's not interesting at all - the comment is very stupid (jacobin is not "whole journal on literal communism") as well as such lazy both-sidesism everyone is dumber for having read it.
there's lots of stupid brigading on HN, but sometimes dumb comments get the downvotes they deserve.
you should care, he and his fellow nutters have siezed control of the USA and most tech-mega-corp leadership either agree with them or will go along with them.
a perhaps non-obvious option is to CNAME (or NS) the `_acme_challenge` record from your main zone to another zone you can control better and can't affect production traffic the same way the main zone could. `acme-dns` is a neat little tool for exactly this, that has an https api for your ACME client to request a cert from, and a dns server to respond to dns-01 challenges from your provider.