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.
Direct quote from their joint statement: "Apple and Google have entered into a multi-year collaboration under which the next generation of Apple Foundation Models will be based on Google's Gemini models and cloud technology. These models will help power future Apple Intelligence features, including a more personalized Siri coming this year."
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.
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.
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.
But there's no way they can prove that it was actually the owner that did this. An argument could be that someone got access to the WiFi, either maliciously or otherwise.
It's not enough to be used as evidence in court.
Most likely did the majority of the bots use proxies and VPNs, which may or may not provide additional information about their customers, but even then it has to be proven that is was the same user that did the acts which is very difficult.
You can change modifiers for different inputs. If you have another keyboard attached, it will give you the option to choose between that, and other keyboards, such as the built-in. They can have different modifier overrides.
Most of the things I've seen people complain about being complex seems to be a lack of either understanding, proper tooling and in most times, the codebase itself.
Newer technology usually adds a ton of different patterns and abstractions that can hide a lot of things away from you, so it becomes hard to understand, unless this information is presented as a 101, or you invest all your time to read documentation about each individual part of everything. Which, to be frank, nobody has time for.
I have used GraphQL with Apollo and React for the last couple of years for different kinds of projects and what I have noticed is that the tools themselves, while quite abstracted, also try to support a lot of edge cases which can make it hard to apply to your project. I had to either use other libraries or build my own that helped me abstract some of the things that were most commonplace but required a lot of boilerplate otherwise.
I have found tremendous value by following the philosophy of not to pre-optimize for everything, until it becomes a burden to work with. Although, it can be hard to determine when something is going to become so big that it will be difficult if not impossible to refactor, but you learn that as you go.
I don't see how you can blame something for adding complexity based on what other people _think_ is an anti-pattern.
In fact, it's most of the times not desired to update your store before you know the data has been validated anyway. The store should always be the source of truth, but that also means that it should be valid.
That's the approach I am going with in any case when working with some kind of global state.
> There's no "show me these tips later" option either, so they never learn the new features.
There is a Tips app which is visible on the Home Screen that contains general information such as "Welcome to iPhone" and "What's New" that contains tips on how to use the new features.
The app sometimes even nags you with "Tip of the Day" notifications.