Why just catch the ones ignoring robots.txt? Why not explicitly allow them to crawl everything, but silently detect AI bots and quietly corrupt the real content so it becomes garbage to them while leaving it unaltered for real humans?
Seems to me that would have a greater chance of actually poisoning their models and eventually make this AI/LLM crap go away.
I wonder if there's a public repository of the kernel source deployed on the helicopter. I'd love to see if any of the code I've contributed just flew on Mars
Using only plain-text emails solves the problem nicely.
Who'd even want to ever use HTML mail other than shady or clueless or annoying people?
Just use plain-text only and the problem is solved.
"Yep Confluence is an amazingly overly complicated thing" - yeah,with an incredibly slow editor that screws up even simple page edits constantly. It's a complete shit show. There's a reason we call it "cuntfluence" at my workplace.
"Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues" - Their ToS may prohibit it, but that is in no way going to stop me from doing it - I don't give a shit about some document they write. Atlassian products suck hard and their performance characteristics are horrible. I hate being forced to use their crap at work.
"What's another good email provider?" - an alternative is to run your own mail server. I used to do that and the harddrive with all the mail (and a backup copy) is not going away because some company changes policy..
I've upgraded both RAM and CPUs on IBM RS/6000 machines (pSeries these days I believe) while the system was running. Very nice capability to minimize downtime.
The procedure is 100% supported. You start by telling the OS (AiX in the cases where I did this) that you are going to remove these RAM modules or these CPUs and the OS let's you know when it has moved everything off of those. Then you remove them and plug in the replacement, then tell the OS that the new hardware can be used. Very smooth process.
If your connection can be tapped it is not end-to-end encrypted, obviously. If it is possible for anyone to tap into your communication it is not encrypted (properly).
What you are saying makes no sense. Either the channel is encrypted and safe from being listened in on or it is not. You cannot have both.
I once worked on an application where we (in one common situation) had to sort an array that was always <= 5 elements and in 90+% of cases was already completely (or mostly) sorted. I got a lot of heat from co-workers when I used bubble sort for that task, since "bubble sort is terribly inefficient" (and it is for large random datasets). But, given the actual data in question, no-one could actually make any other sort perform faster.
When will all this political correctness and social justice warrior nonsense stop? Just because a word can be used in a way that causes offense, doesn't mean that it's always used that way. Also, people need to relax a bit and not hunt down things that could potentially offend so aggressively. Take it easy, if something offensive was intended you'll probably know from the surrounding context - stop shooting down individual words.
If you are actually on the team, you shouldn't be reading HN or any other random internet forum to try and get accurate feedback on your work in the first place.