Annoyingly, mailop.org list archives are member-only (free to join however).

Mail Archive has the content, though I never much liked their UI. Link to the first message of the most interesting (IMO) thread, though there were others around the same time: https://www.mail-archive.com/mailop@mailop.org/msg26087.html

edited to add: this was a general MS issue and not necessarily senders having spam/dns/domain issues, which I suppose it why it annoyed mailops so greatly! and of course the long tail of the wider internet

That would be nice, they'd be able to get their history back!

  After waiting for a little while, the program terminated with the following output:
  
  astrid@chungus infra  gzip -vc result/nixos.img | ssh root@myhost.example -- bash -c 'gunzip -vc > /dev/sda'
  root@myhost.example's password:
   77.8% -- replaced with stdout
  
  What happened here?

I do like this idea - with sufficient prep of the system before writing the image, namely stopping as many processes as possible especially those that might do some writing, it's a quick and dirty way to replace a stock OS with a ready-made image. Could perhaps be safer doing it twice, once into a minimal image that does very little beyond network bringup & runs ssh, followed by final OS replacement in a (more) controlled manner.

It's a little HTTP proxy that your application can route requests through, and the proxy is what handles adding the API keys or whatnot to the request to the service, rather than your application, something like this for example:

Application -> tokenizer -> Stripe

The secrets for the third party service should in theory then be safe should there be some leak or compromise of the application since it doesn't know the actual secrets itself.

Cool idea!

How sure are we the aliens aren't trying to dial in?

https://www.jeffgeerling.com/blog/2025/digging-deeper-youtub...

I particularly enjoyed the gentle exposition into the world of cgroups and how they work, the levers available, and finally how Ubicloud uses them.

Looking forward to reading how you handle burst credits over longer periods, once you implement that :)

Lovely work, Maciek!

Development evidently happens in the traditional sense with the project in a nicely defined tree.

The build process looks pretty gnarly, but it works! https://github.com/vrana/adminer/blob/master/compile.php

The discussion about Rules for Writing Software Tutorials had a lively discussion here not too long ago - https://news.ycombinator.com/item?id=42574641

I, for one, am hoping the Kickstarter succeeds and we get to see the finished book. Please support if you're in the target market!

The LA9310 has incredible specs, too, what a beast.

Have you done anything with its Network Listening feature? I'm curious if that's frequency flexible or if it's limited to a specific handful of common bands.

How have you found the NXP SDK, is it reasonably decent to work with?

Interesting subject matter, novel technical problems and solutions, story narrated at speed and with just enough information to fill in typical knowledge gaps, and on top of all of that there's slides and answers ready to go for random questions from the audience.

Wonderful job, PistonMiner!

    I'm writing a book on computer history. You can look at my mirror of stuff I found elsewhere on the web, or the scans of stuff I found at garage sales and such.

Apologies for those who lose hours if not days to the rabbit hole therein.

It's a rare project that a rebuild succeeds!

My experience is with Laravel, so not too far off your ideal of using Symfony, though I wouldn't let minimalism cause you to avoid Laravel and end up having to do more work. Whether you use Laravel or Symfony alone is probably negligible compared to the application itself.

For such a large application - in keeping with avoiding rebuilds - I'd be looking at ways to subsume parts of the current application into (say) a Laravel application, with glue code at the edges where necessary to paper over differences between the legacy code and the framework-backed code.

Continuing on that path with parts of the system - while (crucially) keeping it up and running for existing users - slowly replacing/enhancing existing code to work in a more coherent fashion with the guide ropes of a framework.

Eventually you ought to end up in a position where you can pick up speed and tap away at the legacy parts.

Ref: your final paragraph, in a decent framework you can quite easily scope queries to restrict the data queried via SQL. Particularly if you have a strong permission system this becomes easier! I like to avoid database-per-customer unless absolutely necessary, it has its own issues, like keeping all databases in sync and on the latest migrations.

Sounds like you've got a fun job ahead of you, holler if your org could use some help :) UK based.

You can ask the processor to send higher layer information via diag, including the messages the base stations send. There’s also commands to lock on to a specific base station so you’re not constantly moving from cell to cell.

There’s plenty of commercial devices that use this functionality to provide network monitoring and management capabilities for mobile network operators checking out base station functionality in the field. TEMS comes to mind for that but they’re certainly not the only ones.

It’s a deep rabbit hole :-)

  I think it's a bit discourteous to shoo Daniel away due to an out of scope
  report, then cry wolf when your clients do actually feel that this warrants
  a response. The fact that you made changes to your systems in response
  indicates that this wasn't as benign as it first seemed.

  IMO Zendesk should do the right thing and issue a reward. An issue was
  reported and ultimately resolved in some fashion. Continue to encourage
  researchers to bother reporting things to you. Yes, you have a little egg
  on your face due to the end-run via your clients, but that's life, Zendesk
  will survive.

Looks like the posts start at https://interdictor.livejournal.com/?skip=340 and newer ones can be found via the 'Next 10' link at the lower right.

Thanks Julian!

If I remember correctly it was someone called Usurper or The Usurper and they chronicled their journey at the time looking after a DC during Katrina. It may not have been a whole DC, possibly it was a business and their (smaller set of) servers, but my memory fails me.

Unfortunately I can't remember what medium it was written on - a blog of some sort? Heck, it could even have been on the Something Awful forums given the year.

I remember stories of struggling to find fresh sources of gas for the generator and all the fun involved in getting it from A to B.

Anyone else remember that? I'd love to have another read of it now, and I think some of you might too. It'll offer a bit of insight of what's to come this year too.

  print "{"
  print "\"some_state\": \"";
  print GlobalState.Something.to_text();
  print "\", ";
  print "\"count_of_frobs\": ";
  print GlobalState.FrobsCounter;
  print "}";