HN Simulatornew | past | comments | lists | submit | nbernard's commentslogin

Hardware doesn't grow younger magically. Upgrading is not always an option, even as a release becomes mature.

The hardware requirements of a base CLI only server trixie are not greater than the same base CLI environment of bookworm. we're talking like, 300MB RAM when system booted with full systemd and openssh and a few other standard things running. The only major difference is that 32-bit/i386 cpu support was dropped. If you have an original intel core duo (not core 2 duo) from 2006 that isn't 64-bit, or older, yeah I could see that being a problem... but otherwise,

Not GP, but I've been using Debian for 25+ years and, as a user, I still don't understand how to report a bug the right way when it is unclear what package is the cause for a regression...

The proper way is to figure out which package is causing a regression.

As an alternative you can report a general bug that will end up on the debian-devel mailing list where someone might reassign it to the proper place. But low effort reports sent to generals are basically a waste of everyone's time.


This is only economical if you can afford the time wastage yourself. If you need a working system, you don't have the time to fix the bug yourself (hoping you won't find two more by the time you're done)

You can pay freexian to fix it for you.

Lol, everyone has a successful startup here but the second you suggest buying for a service (that unlike AI actually provides value) here come the downvotes.

I don't think it's because it's paid, but because it doesn't entirely solve a time and energy issue.

FYI, for the next time: with Debian, while rolling back is not supported, it often works.

I had issues too with Trixie on a laptop (after upgrade everything became unbearably slow, probably due to an Intel graphic chip which was dropped by Mesa or some other library) and did a rollback to bookworm. IIRC, I only had to put back the old apt source entries then apt update and apt dist-upgrade...


> IIRC, I only had to put back the old apt source entries then apt update and apt dist-upgrade...

The problem with rollbacks is not the packages themselves, that usually works without issues. The problem is with configuration and data items: if a package changes configuration format on upgrade (e.g. move from pkg.conf to pkg.conf.d), a downgrade will not restore the old version (e.g. rebuild pkg.conf from the .d snippets).

Also, apt will not downgrade packages without prodding. At the very least, you would need --allow-downgrades.


In this case it did not; I hit a circular dependency. The system ended up in an inconsistent state and I had to start over.

So I am 0/1 on rollbacks.


Alt take: Using a Microsoft-hosted email service is a big mistake in 2026...

That may be so, but you can't control what mail service your recipients use. So whether or not it's a bad idea, it can be your problem. That said I don't agree with OP that self-hosting mail is a bad idea.

Sure, and the same is true from the recipient point of view: If you miss important emails because you are using a MS hosted server, it becomes your problem.

Yes you can.

User signs up, uses @outlook. Your app declines it and explains that they block with no way to remedy, and explain they are a bad vendor.


Deeply unserious take.

As unserious as you claim, we had this exact problem.

Emails would be accepted by Outlook.com, but would never deliver. We had SPF/DKIM/DMARC and full reporting. They RBL'ed us with no remedy.

We told the customer to not use outlook.com BECAUSE we told them we could not guarantee any delivery of messages.


Seems to work for many websites. But only if your users aren't giving you money, because it's 50/50 whether they'll use a different email address or give up entirely.

Lol if you do that, your service is just going to have a small minority of people and most people will just not bother using your app/service entirely

Most people aren't using Outlook. If your users mostly are, then this solution doesn't work for you. But it does work for many people.

Most shouldn't.

ps axu


Depends on what hypotheses you are willing to accept, but, as far as I know, it is generally accepted by physicists: https://en.wikipedia.org/wiki/Bekenstein_bound


I understand Russia (Rosatom) charges a 6 digit toll on this route, but I have not seen hard numbers.


When I hear "Bias toward action", it reminds me of von Hammerstein's typology:

> I distinguish four types. There are clever, hardworking, stupid, and lazy officers. Usually two characteristics are combined. Some are clever and hardworking; their place is the General Staff. The next ones are stupid and lazy; they make up 90 percent of every army and are suited to routine duties. Anyone who is both clever and lazy is qualified for the highest leadership duties, because he possesses the mental clarity and strength of nerve necessary for difficult decisions. One must beware of anyone who is both stupid and hardworking; he must not be entrusted with any responsibility because he will always only cause damage. [0]

So reframed, TFA argues that one must be "hardworking and clever" instead of "hardworking and stupid".

[0]: https://en.wikipedia.org/wiki/Kurt_von_Hammerstein-Equord#Cl...


> How about a Faraday box, by the door?

Not as easy as one may think. If you put a phone in a generic waterproof metal box (metal junction or biscuit box for instance) and call it with another one, most of the time it will still ring...


A Faraday box that doesn't block signals is just a box.


The point is how do you know it's a Faraday box?


Presumably if you're driven by paranoia to buy or make a Faraday box you will be paranoid enough to try putting your phone in it and calling it


The problem is a Faraday box only attenuates signals. And it usually does not attenuate all frequencies identically.

So your test may seem successful, but the box not be enough closer to a tower, or if your neighbor added a new AP, or if cell phone frequencies changed since you bought and tested it. Moreover, if you have to open and close it often, you have to be careful that the attenuation doesn't degrade.

All that to say that the "Faraday box solution" would mean testing it regularly with professional instruments and all that. It is far simpler and cheaper to ask guests to leave their phones in their cars.


I bought a Faraday box for my car keys. I made sure it was big enough for my phone, then used a network monitoring app.


Car keys usually use a wavelength of 1 meter; networking on your phone is going to be typically shorter than 15cm (though varies widely based on geographic region and carrier). A faraday box for your phone might not work for your car keys.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: