FlyingMana

FlyingMana

@flyingmana.phpc.social.ap.brid.gy

#php #magento #community 🏳️‍🌈 also a lot of annoying random #stuff he/him - also https://www.huffpost.com/entry/understanding-introverts_n_5989656 🌉 bridged from ⁂ https://phpc.social/@Flyingmana, follow @ap.brid.gy to interact

24 followers4 following124 posts

FlyingMana reposted

Die JU interessiert es nicht, dass das Grundgesetz einen Einsatz der Bundeswehr im Inneren explizit verbietet. Im Chor mit der "Bild" nutzt sie die Angst vor Protesten wie in Frankreich, um einen Ausnahmezustand in Deutschland herbeizuhyperventilieren. Beobachtung durch den Verfassungsschutz wann?

FlyingMana reposted

Okay, I think I fixed the PECL load situation. Everything is now cached. It means nobody can upload any new versions as you can't log in, but at least the server is not dying now. It is deprecated, so this temporary measure is good enough for now. #php #pecl

FlyingMana reposted

FlyingMana reposted

3. Juni 1946: Die CSU in Würzburg wird durch die amerikanische Militärregierung verboten. Grund dafür ist die Weigerung der CSU, Nationalsozialisten konsequent aus dem öffentlichen Leben auszuschließen.

FlyingMana reposted

https://www.raphkoster.com/games/snippets/did-players-destroy-the-uo-ecology/ Ultima Online game designer Raph Koster posted in the 2020's about finer details like the original economy -- it's amazing that this stuff 'now' comes up after more than two decades of anecdotes and silence. Love it!

raphkoster.comDid players destroy the UO ecology?###### There was an article on GameTyrant that was cobbled together from anecdotes out of an Ars Technica video that Richard Garriott did, which gave some somewhat erroneous explanations for how some things in UO went down, particularly why the dynamic ecology resource system didn’t work out. I posted this to Hacker News to correct the record. I was the original lead designer on Ultima Online and the key designer of this system. A few notes, because this article has MANY inaccuracies. 1. Ultima Online wasn’t even in development for three years total. An early prototype was February to September 1995, done by Rick Delashmit. Starting late August and early September 1995, the core team showed up. We showed the game at E3 in spring of 1996 in alpha form. We showed it in beta form at E3 in the spring of 1997. And we launched on Sept 26th, 1997. The ecology was in the alpha test, and was removed during the beta after being rewritten by an engineer who didn’t really like or understand it. 2. “Not many players know about” this is false. The strategy guide published simultaneously with the game even lists all the resource values for how much meat, hide, feathers, whatever, each creature represented. All of those statistics remained in the game and still are there to this day twenty years later. What was disabled was the AI. The values are still used by crafting, harvesting, and lots of other systems in the game. 3. Said AI is exhaustively documented on my website here: https://www.raphkoster.com/2006/06/03/uos-resource-system/ (first article, there is a sidebar with links to the follow-ons) and also collected in my recent book POSTMORTEMS, which has a huge pile of historical info on Ultima Online as well as Star Wars Galaxies and other games I’ve worked on. 4. The reason the AI was disabled had nothing to do with why the ecology collapsed. The AI was disabled because of the cost of doing radial searches followed by pathfinding. “The way players fit into this equation was that the they would embark on quests to kill the carnivorous animals and the pelts that they gained from those quests would be worth more than those gained from the herbivores” doesn’t make any sense. 🙂 5. The ecology collapsed for a different reason: we had a closed economy loop at first, where everything was spawned from a fixed resource pool. It fell victim to player hoarding: when players killed sheep, they then made zillions of shirts from the wool to grind crafting advancement. Then they hoarded them or sold them very slowly. The result was the central bank ran out of wool, and then couldn’t spawn more sheep. This is documented in one of the earliest detailed analyses of MMO economies, Zach Simpson’s “In-Game Economics of Ultima Online,” a very influential piece which led to the widespread use of the term “faucet-drain economy” in online game design. See https://web.archive.org/web/20020730225856/https://www.mine-… 6. “This problem is also what spawned multiple instances of servers (or as they called them, “shards”) that people know and recognize from most MMOs today.” This is not why we ended up with shards, either. UO was originally designed for a concurrency around 250, much like Meridian 59 and other MUD heirs of the day. Its original lifetime forecast was only 30000 or so units, but we knew from early on we’d need multiple servers, even at that population count. Meridian 59 launched with a whole bunch of them, for example. After we got 50000 tester sign-ups, we were asked to hugely increase server size, which led to Rick inventing a server boundary mirroring technology we called “multiserver,” which allowed the map load to be shared across clusters of machines. The entire game was then rearchitected for that in between 1996 and 1997. The term shards came from the fiction of earlier Ultimas. 7. “At the time when 3D graphics cards were new” — they were nonexistent when we started. 8. The source for the article is a more accurate video at Ars Technica, which has war stories from Richard Garriott. But Richard’s memory is, alas, faulty on some of these finer details. 9. There are some great Quora answers on the tech stack for the game and whatnot which have been on HN before, but if you’re interested, you may want to check them out. I will say, it’s awesome and flattering and super cool that so many people still harbor so much affection and so many memories from this game. I was around 25 when I was leading design on it, and the early days when we were doing the impossible are still some of the fondest memories of my career. For lots more war stories, do check out either the book, my site, or this postmortem presented at GDC for the game’s 20th anniversary: https://www.youtube.com/watch?v=lnnsDi7Sxq0 ### Share this post: * Share on Facebook (Opens in new window) Facebook * Share on Bluesky (Opens in new window) Bluesky * Share on X (Opens in new window) X * Share on Mastodon (Opens in new window) Mastodon * Share on Threads (Opens in new window) Threads * Share on Reddit (Opens in new window) Reddit * Share on Tumblr (Opens in new window) Tumblr * Share on LinkedIn (Opens in new window) LinkedIn * Share on Pinterest (Opens in new window) Pinterest * Share on WhatsApp (Opens in new window) WhatsApp * Print (Opens in new window) Print * Email a link to a friend (Opens in new window) Email *

FlyingMana reposted

Wisst ihr noch, was für ein Wahnsinn ausbrach, als einige Westdeutsche forderten Sachsen-Anhalt das Geld zu streichen, wenn die Nazis wählen? (Bescheuerter Vorschlag, ja) Die Hölle der wütenden ,Man hat uns alles genommen und ihr werdet es nie verstehen‘-Ossis brach los. Nun drohen die…

FlyingMana reposted

Wenn eine Linke-geführte Rot-rot-grüne Regierung in Berlin entsteht, gäbe es eine Mehrheit im Bundesrat für die Prüfung für ein AfD-Verbotsverfahren. Wenn ihr wissen wollt, warum die rechte Presse so Panik schiebt.

FlyingMana reposted

https://linuxiac.com/lets-encrypt-certificate-rules-now-include-u-s-sanctions-warranties/ I didn't realize fully that Let's Encrypt would be affected by everything the US government currently does. Ugh! Hat tip to @yvg for the nudge

linuxiac.comlinuxiac.comLet’s Encrypt, the world’s largest free SSL/TLS certificate issuer and one of the key services behind today’s HTTPS web, has updated its Subscriber Agreement with new language requiring certificate applicants to confirm that they are not covered by comprehensive U.S. sanctions, export-control restrictions, or related prohibited-party rules. This update is included in version 1.7 of the Let’s Encrypt Subscriber Agreement, dated June 4, 2026. The agreement sets the terms for requesting, accepting, and using SSL/TLS certificates issued by the Internet Security Research Group, the nonprofit behind Let’s Encrypt. The key change is in Section 3.1, which outlines subscriber warranties. Subscribers must now confirm they are not located in, organized under the laws of, or ordinarily resident in a country or territory subject to comprehensive U.S. sanctions. > _“You are not a person or entity that is: (a) located in, organized under the laws of, or ordinarily resident in any country or territory that is the target of comprehensive U.S. sanctions; (b) a prohibited or restricted party under U.S. or other applicable sanctions and export control laws and regulations; or (c) owned or controlled by or acting on behalf of anyone described in (a) or (b). You agree to use Let’s Encrypt Certificates and any services provided by or on behalf of ISRG in compliance with applicable U.S. export control and sanctions laws and regulations.”_ The clause also applies to prohibited or restricted parties under U.S. or other applicable sanctions and export-control laws. It further extends to individuals or entities owned, controlled by, or acting on behalf of such parties. Practically, this update ties Let’s Encrypt certificate eligibility more directly to U.S. sanctions compliance. It covers both geographic restrictions for sanctioned jurisdictions and list-based restrictions for specific sanctioned parties. OFAC, the U.S. Treasury office that administers sanctions, classifies programs as comprehensive or selective, using measures such as asset blocking and trade restrictions. Its public search tool checks names against U.S. sanctions lists, including the Specially Designated Nationals and Blocked Persons List. Importantly, for Let’s Encrypt users, this change does not introduce a new technical certificate-validation process. The updated language is a legal warranty by the subscriber, not a public statement that Let’s Encrypt is automatically blocking all domains from certain country-code top-level domains. The updated agreement also impacts certificate lifecycle responsibilities. If any warranties in Section 3.1 become untrue for an existing certificate, the subscriber must immediately request revocation. ISRG may also refuse certificate requests at its sole discretion, for any lawful reason. For most users, this update will likely have no practical impact. For those connected to comprehensively sanctioned jurisdictions or listed parties, the new language makes the compliance requirement explicit in the agreement. **Update, July 22, 2026:** On July 6, 2026, Let’s Encrypt replaced Subscriber Agreement version 1.7 with version 1.8. The new version removes the previous wording discussed in this article and adds a wider section on compliance with applicable laws, including U.S. export control and sanctions regulations. Let’s Encrypt states that this revision clarifies its existing policy and does not affect where or to whom it issues certificates. The organization continues to serve permitted non-governmental users in sanctioned countries and territories where exemptions and authorizations apply.

FlyingMana reposted

RE: https://tldr.nettime.org/@tante/117269357701498157 But in short: "FLOSS without Antifascism is not even doing the job it was set out to do because having fascists around will ensure that many marginalized groups do not gain any of the potential benefits." (and the bar FLOSS sets itself is […]

tldr.nettime.orgOriginal post on tldr.nettime.org
tante@tante.tldr.nettime.org.ap.brid.gy

Omarchy is part of new fascism. But it's also a good case study about how little political resilience is built into FLOSS: The libertarian roots have not only made the whole movement ready for the taking by corporations but also by fascists. And sadly many influential organizations in that […]

Scheint als hätte der Internet anbieter DNS:NET heute eine größere störung. Hotline scheint berichten nach nicht zu gehen. Der Login ins Kundenkonto timed out. Authentifizierung des Modems schlägt fehl. Aber zumindest das TV signal kommt noch durch die Leitung

FlyingMana reposted

FlyingMana reposted

RE: https://mementomori.social/@juergen_hubert/117151722520990567 Update: One of the admins of this Facebook group apparently deleted all comments by myself and other authors who expressed criticism of this approach. One admin of this group also posted assorted comments which were strongly in […]

mementomori.socialOriginal post on mementomori.social
Jürgen Hubert@juergen-hubert.mementomori.social.ap.brid.gy

I feel triggered. #amwriting #translation

FlyingMana reposted

China joins Europe in scrapping Windows for Linux https://www.zdnet.com/article/china-drops-windows-for-linux/ • The Chinese government is dumping Windows for some desktops. • A Linux desktop version will replace Windows. • The most likely candidates are Kylin OS or UOS.

zdnet.comChina joins Europe in scrapping Windows for LinuxThe specialized Chinese version of Windows was already scheduled for retirement in February 2027, but now its end-of-life date has been moved up.

FlyingMana reposted

RE: https://mastodon.social/@sixtus/117065047913611409 Aus reiner Neugier: Wie ist denn so das sozio-ökonomische Gefüge der betroffenen Wohngebiete in #Berlin ? Bei sowas muss ich immer daran denken, daß in den USA die Highways oft bewusst so gebaut wurden, daß sie erfolgreiche Stadtviertel […]

mementomori.socialOriginal post on mementomori.social
Mario Sixtus 🇭🇰馬六@sixtus.mastodon.social.ap.brid.gy

Fakt: Die gleichen Parteien (CDU & SPD) die sich mit Klauen, Krallen und "Kommunismus"-Rufen gegen jede Idee der Vergesellschaftlichung von Wohnraum wehren, haben nicht den Hauch eines Skrupels, mitten in Berlin Wohnhäuser zu enteignen und abzureißen, damit sie ihre fucking A100 weiterbauen können.