AT&T still does this, if you're using their (intentionally terrible) standard gateway device the default DNS will return a "search page" instead of NXDOMAIN which predictably has all sorts of negative impacts on non-browser devices but the wastes of oxygen responsible for this don't care as long as they see that delicious ad revenue.
If you're only willing to work 100% remotely then you are competing with everyone in the world. Melbourne, where OP lives, has quite a few developing markets within a few hours of timezone offset. This is especially true of MNC with a strong presence in APAC.
Then don't hit on people. Go there with no expectations other than enjoying the activity, it makes you a better and more interesting person anyway. The people who get banned are the creepy ones who go purely for the sake of hitting on people.
"steering rules" is a core feature baked into Kiro. It's similar to the spec files use in most agentic workflows but you can use exclusion and inclusion rules to avoid wasting context.
There's currently not an official workflow on how to manage these steering files across repos if you want to have organisation-wide standards, which is probably my main criticism.
There are many licenses with mortality clauses but they are general not popular because the ambiguity and "supply chain risk" of having such a license in a dependency tree tends to limit adoption of any projects that use them.
They could definitely add a maker-checker process (similar to code review) for new versions and make it a requirement for public projects with x number of downloads per week.
reply