

evolves robots.txt instructions by adding an automated licensing layer that’s designed to block bots that don’t fairly compensate creators for content
robots.txt - the well known technology to block bad-intention bots /s
What’s automated about the licensing layer? At some point, I started skimming the article. They didn’t seem clear about it. The AI can “automatically” parse it?
# NOTICE: all crawlers and bots are strictly prohibited from using this
# content for AI training without complying with the terms of the RSL
# Collective AI royalty license. Any use of this content for AI training
# without a license is a violation of our intellectual property rights.
License: https://rslcollective.org/royalty.xml
Yeah, this is as useless as I thought it would be. Nothing here is actively blocking.
I love that the XML then points to a text/html content website. I guess nothing for machine parsing, maybe for AI parsing.
I don’t remember which AI company, but they argued they’re not crawlers but agents acting on the users behalf for their specific request/action, ignoring robots.txt. Who knows how they will react. But their incentives and history is ignoring robots.txt.
Why am I is this comment so negative. Oh well.
Our migration was a mess. And took a long time. I don’t know how much our contracted company was at fault. They certainly didn’t do a good job. We have Jira extended for time management to billing and staff pay and whatnot.
I have some CSS Hacks to make the cloud version usable, but the DOM is a mess. Only test id attributes are reasonable, stable, and descriptive. Everything else is random in terms of class and id.
Occasionally, something changes. Despite a dedicated maintenance window by Atlassian, and marketing towards predictiveness and all that positive stuff, occasionally something changes without warning, without announcement. And you’re left wondering - is my memory getting that bad? Is this new?
My last highlight is that they converted migrated images in Jira ticket descriptions into some square image control. Something you can’t even use for new images. Pasting or dropping an image into the description will lead to something different. When it’s attached as an attachment, like it was in the past, you can only include it into the description as a fixed attachment either inline control or inline fixed preview control.
If you have an old description with rectangular screenshots, you know, possible because you have a widescreen monitor, or because we have width space and make use of it for content, the square adds a ton of whitespace. Make the image big enough to be readable, and the only thing on your entire screen is the image and dead space, half of the height dead space.
There’s many annoying and horrendous things.
Worst is we contracted some third party for a custom menu and whatnot. We have a browser extension for that, for Jira and Confluence. I have all three functionality sets disabled because it makes it even slower or broken.
It works for the most part, but man, there’s so many irritations and annoyances.