You're talking about a subset of ASCII then. Unicode is supposed to support different languages and advanced typography, for which those characters are necessary. You can't write e.g. Arabic or Hebrew without those "unnecessary" invisible characters.
Most people using Slack, Teams etc. and especially those making purchase decisions have no idea what XMPP is and what it's capable of. Heck, even Facebook used to federate XMPP until they decided to go proprietary. Not in the interest of their users, but because it makes the most money for its shareholders.
Sales tax is actually very different beacuse it is usually either cumulative and added to each part of the chain, or only the last one; whereas VAT is deducted in all but the last part of the chain.
Yea, the idea is that the VAT effectively taxes the added value in each step of the value chain because there's a limit to how much you can charge for an item or service. E. g. a 25 % VAT does not necessarily mean the goods become 25 % more expensive; most of those 25 % would have been profit for the reseller, intermediates and manufacturer if it were not for the VAT. Perhaps a little contra-intuitively, a high VAT keeps prices down and business efficient because every intemediate is indirectly taxed even though the VAT is only charged to the final consumer.
Sure, I've managed both clusters and single node deployments in production until 2025 when I changed jobs. Elastic definitely does have its strengths, but they're increasingly enterprise-oriented and appear not to care a lot about open source deployments. At one point Elastic itself had a severe regression in an irreverible patch update (!?) which took weeks to fix, forcing us to recover from backup and recreate the index. The documentation is or has been ambigious and self-contradicting on a lot of points. The Debian Elastic Enterprise Search package upgrade script was incomplete, so there's a significant manual process for updating the index even for patch updates. The interfaces between the different components of the ELK stack are incoherent and there's literally a thousand ways to configure them. Default setups have changed a lot over the years, leading to incoherent documentation. You really need to be an expert at Elastic in order to run it well – or pay handsomely for the service. It's simply too complicated and costly for what it is, compared to more recent alternatives.
Used to be, but they're very complicated to operate compared to more modern alternatives and have just gotten more and more bloated over the years. Also require a bunch of different applications for different parts of the stack in order to do the same basic stuff as e.g. Meilisearch, Manticore or Typesense.
Fascinating, but the dataset is obviously incomplete – there's barely any traffic in Europe until mid april. January-march looks as if there's been a zombie apocalypse.
Agreed 100 %, but the snow kept me from reading the whole article. Would've thought the snow icon turned it off, but instead it changed the background color… Liquid Glass is bad, but not _that_ bad.
True, but the dishwasher should have its own firewall regardless, and assuming it'll be on IPv4 behind a firewalled NAT is by itself an implementation error.
It provides no security by itself. There have been (and still are) countless vulnerable Internet reachable NAT routers which can easily be exploited to provide access to the whole private network behind it. NAT by itself can't be relied on to provide any security – you need correctly configured firewalls for that. An ISP provider might provide a sensibly configured firewall with the home router, but they may also be operating an easily exploitable backdoor into your private network.
Unless the downtime was caused by something Cloudflare would've prevented, this downtime would've happened regardless of being behind Cloudflare. Cloudflare adds another single point of failure.
That's quite abusive behavior. I'm sorry for these wives, having to deal with this as it's probably not the only thing they have to endure. And how do the spouses "prove" they're not cheating when they're away - or is that not so important because they can choose to do whatever?
I guess it's partially because ISPs are perfectly happy selling crippled internet connectivity as the base service and charging hefty premiums for "luxuries" like static IPs. It has also become common to only offer static IPs to business customers.
It's useful when the client always has its own static IP that _doesn't change_ between sessions. In this case, where the public facing IP may be shared by thousands of users, it provides no real security. All you'd have to do to gain access would be getting the client IP and finding some way of getting on the same network. Which in many cases could be as easy as subscribing to the same cell network or other ISP, or connecting to the guest wifi network of an office building.
Nowadays public facing client IPs are often shared by thousands of users behind CGNAT. IP based firewall rules are useful when the peers have their own static IP address, but provide no real security when the IP address is shared.
This is vibe coded security through obscurity, i. e. quite useless. Use Tailscale or a self hosted VPN.