Fuel goes bad mostly only when mixed with bio fuel, which allows bacteria to grow which does not happen for pure fossile fuel. Additives may degrade, too - but they can be mixed after long term storage. So jet fuel which is basically identical to diesel (except additives) can be stored unlimited.
The affiliate information shows that it the website shows mostly / only affiliate offers, and omits (intentionally?) much better a lternatives like posteo.de for email.
Listed vendors like OVHcloud must follow the US cloud act, so not really independent from US.
Does Ford now copy Tesla‘s tactic to over-promise nice cars for a specific low price to come much later (in 2027)? And then deliver much later and for higher prices?
Reads like AI generated bullshit overemphasizing on zero percent probable benefits and ignoring hundred percent probable damages.
Welcome in AI age.
developers have a specific skill set which gets 100% replaced by AI. The assumed skill set of „limiting AI damage“ is neither present or desired by stakeholders who push into AI (except alibi)
Yes, all packets get logged (metadata only). Otherwise we wouldn’t know there is an issue.
Those packets consume bandwidth and device utilization, too but this is flat fee, whereas log traffic is measured per GB so we investigated where an unexpected growth came from.
Microsoft InTune WUDO has a similar bug costing my department 40000 € internal charging per month for firewall log traffic of blocked tcp 7680 requests. 86000 requests per day per client, 160 million per day total. MS confirmed the bug but did nothing to fix it.
Wake up, American tech people (or anybody with remains of intelligence and humanity). Solve this issue from inside before the system implodes or sets the world even more on fire than it has done already.
While I appreciate many routine bug fixes and some longtime awaited features and UI improvements, Affinity apps still lacks general stability, UI consistency, and a huge number of essential features, making it hard to use these apps in professional context of for critical work.
The are no official statistics, but from own observation and counting the evolution of key indicators is very bad and going into the wrong direction:
Rate of solved long term issues (for basic/essential functionality) stays constant or going down. E.g.
Wrong handling of alpha channel adjustments layers
Rendering issues depending on zoom level
Merge down leading to blurriness
Handling of layer or position or size leading to blurriness
Unable to render 16 bit color depth within the app
Wrong CMYK color profile preview / soft proofing (paper simulation)
Rate of features implemented (based on user feedback in forum) low
(E.g. LTR writing, handling of 1-bit BW documents, missing vector trace, supporting functions for game devs like zero in alpha channel, PAR (pixel aspect ratio), blend tool, …
Instead Affinity often adds features which where never requested by users before and server only small very user groups (astrophotography stacking)
Countless regressions of UI bugs (UI elements not working/unusable)
Some „design decisions“ of the developers are insane:
- older releases unable to open files edited by newer releases (this effects almost every minor release), so all users working as team or family must always upgrade to latest
iPad versions lacks dozens of essential functions available on Desktop versions. Gap increases with every release
Instead of fixing bugs for existing functionality, Affinity introduces new functions, covering the use same use case by a totally different workflow. E.g. combining blend ranges and mask layers vs. Live mask layers.
If needed I can provide links to relevant posts in the official Affinity user forum proving these claims.
The Nazi term Gleichschaltung (German pronunciation: [ˈɡlaɪçʃaltʊŋ] ⓘ), meaning "synchronization" or "bringing into line", was the process of Nazification by which Adolf Hitler—leader of the Nazi Party in Germany—established a system of totalitarian control and coordination over all aspects of German society "from the economy and trade associations to the media, culture and education".[1]
There is no direct counterpart in Englisch Wikipedia for:
Machtergreifung
Mit Machtergreifung (auch Machtübernahme oder Machtübergabe) wird die Ernennung des Nationalsozialisten Adolf Hitler zum Reichskanzler durch den Reichspräsidenten Paul von Hindenburg am 30. Januar 1933 bezeichnet. Hitler übernahm an diesem Tag die Führung einer Koalitionsregierung von NSDAP und nationalkonservativen Verbündeten (DNVP, Stahlhelm), in der neben ihm zunächst nur zwei Nationalsozialisten Regierungsämter bekleideten (Kabinett Hitler); dies waren Wilhelm Frick als Reichsinnenminister und Hermann Göring als Reichsminister ohne Geschäftsbereich. Zusätzlich zur eigentlichen Ernennung umfasst der Begriff die anschließende Umwandlung der bis dahin schon seit 1930 durch Präsidialkabinette geschwächten parlamentarischen Demokratie der Weimarer Republik und deren Verfassung in eine nach dem nationalsozialistischen Führerprinzip agierende zentralistische Diktatur.
Nachdem am 1. Februar das Parlament in Berlin, der Reichstag, aufgelöst worden war, schränkten die Machthaber in den folgenden – von nationalsozialistischem Terror gekennzeichneten – Monaten die politischen und demokratischen Rechte durch Notverordnungen des Präsidenten ein. Als entscheidende Schritte auf dem Weg zur Diktatur gelten die Verordnung des Reichspräsidenten zum Schutz von Volk und Staat (Reichstagsbrandverordnung) vom 28. Februar 1933 und das Ermächtigungsgesetz vom 24. März 1933. Der Reichstag verlor damit praktisch jegliche Entscheidungskompetenz. Neben vielen anderen wurden nun auch Parlamentarier ohne Gerichtsverfahren in Konzentrationslagern eingesperrt und gefoltert.
Most DB systems allocate memory pools for specific purposes, and do a better job in managing RAM vs OS because the DB knows which queries will be processed and can optimize RAM usage accordingly. Using virtual memory (paged out to disk) would spoil the DB optimizations and should be avoided in general.
But the more important part is managing disk IO, as permanent storage is far slower, but magnitudes larger than RAM (except for memory DBs which depend on special RAM with battery backup). Even in times of SSD.
This applies for dedicated DB servers.
If you have a server with mixed workloads and other apps beside DB, it becomes blurry.
