fnky

He didn't say they made it, he said they _own_ it.

The issue was not that forking of ACF in and of itself was controversial. It was that they hijacked and repurposed the original WordPress Community page and distribution to point to their own, including any subscribers to the existing project in the name of "security".

One could argue that because WP Engine was banned from accessing the WordPress.org infrastructure, it could technically be seen as a form of supply chain attack and brought up questions about trust and possibly monopolistic and anti-competitive behavior.

The reason why these scripts are still active is because of EU courts' unwillingness to issue an immediate stop-order. Courts in Munich in the case of Teamfluence v. LinkedIn did not find the "urgency" or "irreparable harm" required for a preliminary injunction. So EU courts don't feel like this is bad enough, despite the fines that LinkedIn has already accrued from previous similar lawsuits.

This is the crux of every decentralized system. If there's no one there to host the data and make it available, you have to start somewhere.

The point of ATproto is that it gives you the option to move to your own, or someone elses. Bluesky is just a use-case which happens to provide a good enough platform that people don't need to host it. That's typically not the concern of most people anyway.

You know it's good when all the members have their home addresses listed on their personal websites.

Too bad there's no examples of how this looked like.

RA3 is where I started my interests in first-person shooters. My family and someo of their friends had a clan, and they would hold LAN parties, playing matches against other clans. Sometimes I was allowed to play a bit, and got instantly hooked.

When I got my first personal computer, I stated playing RA3 a ton–and Unreal Tournament on the side. Later on it became Quake 3 OSP/CPMA (as well as Freeze Tag and InstaGib) and Quake Live Clan Arena, but never really competitively.

At the same time I also discovered CS 1.6. It was sort of a relaxation from all the fast-paced fragging for me. I liked the slower pace and different skill it required. I eventually joined some tournaments and started playing more competitively, hooking up with people in IRC.

I try to seek out games every now and then, but unfortunately there's less and less communities around Q3 and the likes, so it's becoming increasingly harder to find fun matches.

First game, the places I got was:

- Argentina - Belarus – I guessed Poland, because the picture dipicted Polish soliders right after WII - Poland - France - Finland

I personally didn't have an overall problem compiling the project on macOS in the past. The only issue I ran into was not being able to get VGUI to work, so there were no HUD in-game. Last I did this was ~6 months ago, though, so it could be things have improved now.

I've had the encountered same problem when trying to just get the request path in order to highlight the current active page link in a navigation. It's simply not possible with Server Components only.

I ended up having to wrap each nav link in a client-side component, meaning the active state is lost in no-JS land (but will still render the nav on the server). The provider just wraps the link to provide a class, which can then be used to identify, with CSS, which link is active.

I really don't understand how cookies and headers can be provided, but not even just the requested path.

Yarn Plug n Play tries to address this and other problems with node_modules such as heavy and deep trees of dependencies that fill up your computer for each project. It generates a .pnp.js file that tells Yarn where packages are located, so they can effectively be installed once and used in multiple projects.

> I'm using a password manager and my password should be safe.

You may have forgotten that it doesn't matter how you store your password, but the problem is that it is a single factor. Once compromised, one can gain access to anything within that account. You may be compromised by phishing, keylogging or other means. 2FA can help with making these types of attacks more difficult, although not impossible.

But what if your relative suddenly pass away? Then you'd be pretty screwed, wouldn't you?

More likely that he didn't use the keys in a year and GitHub removed them for security reasons.

I'd love to hear of any solutions on this. The solution should, however, be insusceptible to remote attacks, that could put a user's account at risk.

2FA with SMS has the problem that companies offer support by human and don't have a tight system for changing numbers to another phone, as proven again and again, resulting in accounts being compromised.

While the current solution of MFA aren't perfect, it's hard to come up with other solution that would be as safe or safer and prevent most to all mechanisms used to compromise accounts, like phishing, social engineering and other possible remote attacks. Giving you the possibility to save the codes somewhere physical has its downsides, but an important upside is that it allows _you_ to keep in charge your own security in most cases.