fnky
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 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.
Too bad there's no examples of how this looked like.
Source: https://blog.google/company-news/inside-google/company-annou...
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.
- Argentina - Belarus – I guessed Poland, because the picture dipicted Polish soliders right after WII - Poland - France - Finland
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.
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.
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.
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.
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.
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 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.
Take for example a senior using an iPhone:
My grandmother, 77 years old, has had her iPhone for 2 years. Prior to that, she had no mobile at all and has not used a ton of technology through her life.
She learned to use her crucial apps: Mail, Safari, Notes, Calendar and Contacts by herself.
She will only ask if there are different ways of doing things if she can't figure it out by herself—which is very rare.
I agree that Settings can be cluttered to navigate, but it's also assumed that it's not an app that people use every day. Taking that into account, the General tab is usually where you find what you need when it comes to changing most settings anyway.