Hi,
as already mentioned here, recently I ran into what has now been identified as a firefox issue.
Due to the complex relationship between the application, the web proxy, the authentication protocol software, various caching levels and a solid bunch of local modifications, it was rather difficult and time-consuming to identify the culprit, only that it somehow did appear around 2026Q1 - or more specifically maybe due to the upgrade of firefox 140.5esr to 140.7esr - but that being a maintenance upgrade only in an ESR and therefore (up to now, that is) extremely unlikely to insert breaking changes or remove vital functionality.
So, at first I asked at this place, in order to get info if there were any important modifications in the upgrade. But nobody even bothered to answer at all.
Then it appeared things would continue to work - but that was only because of caching, or other clients, where 2026Q1 was not yet installed, would periodically repair the cache in the app server. And I had other things to attend.
On wednesday or thursday. after the other clients had been upgraded, the trouble reappeared. I was able to do a bit more solid debugging, and in my perception it became difficult to imagine any other culprit than the firefox.
So I finally decided to no longer wait on nobody answering, and instead to really bother the firefox people with a bug report.
Within only half a day the bug was confirmed, and even identified with a change that introduced the problem.
But now comes the real absurdity: Me, the person who is actually suffering the malfunction, I am not allowed to know that change!
I probably (given I knew the nature of the issue) just want to fetch a reverse diff, drop it into my deploy chain, and be done with the issue - things will then repair themselves, and I have a lot of other matters to attend.
But instead, these people entertain themselves discussing on severity and whatever and operating their own self-made buerocracy, apparently thinking the users are just consumers, stupid sheep waiting to be fed with their advertisements while praising the almighty lord developer; with no need to know what these are doing.
There is a reason why running ESR release - it is because one cannot afford breakage. Sure, mistakes can always happen, and that is why I keep a full source codebase where everything is compiled locally, so it can be repaired rightaway.
But if now developers run their thing as a closed shop, where you're not allowed to know what was intended and why it failed, this gets difficult. Certainly I can download the full gitrepo, work myself thru the changes, and finally figure out what goes on. But why is that necessary, when somebody else already has the full details of the issue?
as already mentioned here, recently I ran into what has now been identified as a firefox issue.
Due to the complex relationship between the application, the web proxy, the authentication protocol software, various caching levels and a solid bunch of local modifications, it was rather difficult and time-consuming to identify the culprit, only that it somehow did appear around 2026Q1 - or more specifically maybe due to the upgrade of firefox 140.5esr to 140.7esr - but that being a maintenance upgrade only in an ESR and therefore (up to now, that is) extremely unlikely to insert breaking changes or remove vital functionality.
So, at first I asked at this place, in order to get info if there were any important modifications in the upgrade. But nobody even bothered to answer at all.
Then it appeared things would continue to work - but that was only because of caching, or other clients, where 2026Q1 was not yet installed, would periodically repair the cache in the app server. And I had other things to attend.
On wednesday or thursday. after the other clients had been upgraded, the trouble reappeared. I was able to do a bit more solid debugging, and in my perception it became difficult to imagine any other culprit than the firefox.
So I finally decided to no longer wait on nobody answering, and instead to really bother the firefox people with a bug report.
Within only half a day the bug was confirmed, and even identified with a change that introduced the problem.
But now comes the real absurdity: Me, the person who is actually suffering the malfunction, I am not allowed to know that change!
I probably (given I knew the nature of the issue) just want to fetch a reverse diff, drop it into my deploy chain, and be done with the issue - things will then repair themselves, and I have a lot of other matters to attend.
But instead, these people entertain themselves discussing on severity and whatever and operating their own self-made buerocracy, apparently thinking the users are just consumers, stupid sheep waiting to be fed with their advertisements while praising the almighty lord developer; with no need to know what these are doing.
There is a reason why running ESR release - it is because one cannot afford breakage. Sure, mistakes can always happen, and that is why I keep a full source codebase where everything is compiled locally, so it can be repaired rightaway.
But if now developers run their thing as a closed shop, where you're not allowed to know what was intended and why it failed, this gets difficult. Certainly I can download the full gitrepo, work myself thru the changes, and finally figure out what goes on. But why is that necessary, when somebody else already has the full details of the issue?
