motrm
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/[email protected]/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 [email protected] -- bash -c 'gunzip -vc > /dev/sda'
[email protected]'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!
<!-- from http://wrttn.in/04af1a -->
<title>wrttn:04af1a</title>
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 "}";
The first two parts were a really fun introduction into many aspects of how a text editor works, there's so much you don't even think about as a user of text editors, but Mihhail had to take care of.
I think my favourite takeaways were the bits of UI polish and thoughtfulness that are sprinkled through both pieces, and probably the third too.
Nice work Mihhail, you clearly care about not just making and selling a product, but making a wonderful experience out of something 'mundane' like a text editor. It takes a lot of care to go beyond just 'making it work' to 'making it work thoughtfully'!
As a competent programmer I've already got an idea of what I'm about to write in my head, yet having an immediate prompt suggest a "do you mean this?" turns that train of thought away from what I'm writing and instead to "is the suggestion correct and what I want?" before accepting or ignoring it.
It's not for me, I just want to get my brain waves into the IDE as quickly as I can.
That said I can certainly see how it'd be useful when working with a language you're not super familiar with, perhaps one you just dabble in occasionally, or where you're learning programming in general, or a new language, where these hints could save you a quick search for "for loop syntax in $LANG".
It's very exciting to see what will come out of AI. There's a lot of stuff not relevant to me, but in time far smarter people than I will conjure up ways to make my life easier.
As you know, the REST API will deliver a maximum of 2000 records per request, so beyond a certain scale it's not really tenable in terms of speed & consumption of API calls.
So yes, Bulk API is probably going to feature soon.
Cheers Ian!
Salesforce objects map quite nicely onto Laravel’s Eloquent models (and booleans work fine! ref @ianyanusko in a sibling thread)
On the Salesforce side we use triggers to send a summary of field changes to Laravel to apply to its MySQL database. These are very cheap in terms of Salesforce limits and consumption!
Changes originating from the Laravel side use Salesforce’s REST API. It’s handy taking the round trip through Salesforce when saving changes as it lets flows/processes run and formulas to do their thing before data is persisted in MySQL.
Syncing data from Salesforce (to seed a database for example) is done via REST too. It works OK.
I considered productising it at one point, but ideas are a dime a dozen, it’s a lot harder to execute well and Bracket is doing exactly that, kudos!
This has been a thoroughly interesting post, and I’ll keep my eye on Bracket. You are however out of budget for my client, we had to achieve syncing on a shoestring ;)
Late in August the reporting[0][1] said that Netflix DVD subscribers could keep any DVDs they have at the time of shutdown, as well as applying[2] to receive some extra discs
[0] https://www.businessinsider.com/netflix-customers-can-keep-d...
[1] https://www.businessinsider.com/netflix-mail-service-sending...
[2] https://twitter.com/dvdnetflix/status/1692240971659108448
Great article overall, thanks for taking the time to write it up.
Forgive me if I missed this being explained - I was curious what the reasoning for this was and I didn't see it! Could you elaborate? :)
It's been a thing as far back as I can remember.
The worst part is when you don't remember what the last thing you moved was. You know you've undone something, but you don't know what it is.
Is something going to be broken now?
Are you going to lose something that's now in a place where you weren't expecting it to be any more?
Good luck figuring it out!
- When approaching a Mongolian ger it is customary to say, “Nokhoigo Khorioroi” which means “Hold the dog,” even if you don’t see a dog. This is because guard dogs are common and a dog may be aggressive towards visitors, but it in general alerts the occupants to your presence so they can come out and greet you.
- Never knock on a ger door. It is considered rude. You simply enter.
- When entering a Mongolian ger, step with your right foot first and never stand on the threshold. The threshold is said to be the “neck” of the ger and standing on it tantamount to “strangling” the home.
- Mongolians don't chat to each other over the threshold. Step in rather than asking things through the doorway.
- To greet your hosts say, “Sain bain uu?” (pronounced “Sey-Ben-Oo”) – meaning “how do you do?” If you are entering for the second, third, fourth time, you can just say “Sen-ooo”, meaning “Hi!”.
Today we both learned :)
[0] https://notesofnomads.com/mongolian-gers/#Ger_etiquette_The_...