View -> User Interface, change to Tabbed or Tabbed Compact (or Notebookbar in old versions).
Already been done, there's a data dump of every MM1 course on archive.org. The dump is dated but it came after level uploads for MM1 were shut down so it should be about as complete as it gets, minus courses deleted by Nintendo before that.
Actually playing anything seems to be quite complex but there's some instructions in the reviews, so it should be doable for someone to set up a replacement server in the future (Pretendo network already has the basics for custom Wii U online running).
And they're also deleting/deleted all classic Minecraft accounts from before that. They invented an incredibly weird and needlessly obtuse process to extend the migration deadline by 3 months (true final deadline is now mid December 2023), but that's seemingly it. Everyone not paying too much attention to their email just gets $30 worth of game deleted because of a completely arbitrary decision.
Yum, smells like microwaved 'microwave-safe' plastic!
The current advisory is in webm (VP8 specifically). The webp one was 2 weeks ago. ...yeah, not a good time for web browsers lately...
(edit: noticed OP actually did link the webp one, I thought it'd be CVE-2023-5217 because that's being linked elsewhere)
It was made as result of an EU settlement that only lasted about 5 years. https://en.wikipedia.org/wiki/BrowserChoice.eu
I have absolutely no idea why they figured 5 years would be good enough.
No, I most definitively hate Jira (and also my manager). Jira is the only software I've had to use where 10+ second page load times are a regular everyday occurrence. On their cloud hosting, so it's not like we could do anything to fix it other than filing tickets... which we were told to simultaneously keep doing so they can track it but also stop doing because it's working as intended and we were wasting their time and abusing support.
JQL is absolute garbage, and it doesn't even take hindsight; they took SQL but in an attempt to simplify it, they broke everything about it. Whether any particular functionality is a field or a function to run on some other field is a mystery. And if you're using Jira Service Management, it gets infinitely worse; everything is bolted on in a terrible way.
Every interaction between their "Kanban board" and "ticket" system is confusing. They pull from the same database, except not quite, except they do. It's a representation of data, but not the same representation the data is in. If you have any kind of custom workflow setup at all - which the blog both criticizes as bad and uses as a reason to explain why Jira is the only good option (????) - it will simply never do the right thing unless they map 1 to 1.
There are all kinds of perpetually missing features. Multiple assignees are a big one, there is simply no correct way to represent "John and Bob will spend some time together brainstorming about a new architecture" or simple things like pair programming, despite that being a fairly significant task that should somehow be accounted for in planning. You can half-ass it with custom fields or sub-tasks, but then the entire ecosystem of tooling built on the assignee field crumbles.
Likewise, you can't assign issues to a "virtual" position of any kind, all you can do is leave them unassigned or make (and pay license costs for) a fake user. It's not possible to represent concepts like "the first available person from the Ops team" or "whoever is currently managing the security team" unless you make it into a status and leave it unassigned, which causes a massive amount of issues when multiple teams led by different managers are working on one project or someone is temporarily or permanently unavailable for whatever reason (vacation/sick/etc). Planning software that cannot deal with people being unavailable is worthless.
Permissions are a complete mess. There's all kinds of funny interactions between admin and project permissions, and some things are in what could have obviously never been the correct spot. How it ended up with project releases being an administrative permission speaks volumes about how poorly everything is designed. Happy tenth anniversary to the cloud ticket, the original server one has another decade on it. Twenty YEARS of the most basic feature imaginable not existing when the initial implementation was patently incorrect to begin with.
Okay, the thing that really matters to me:
“Frankly, we have more important things to do than spend a lot of time trying to figure out how to protect kids from books,” Exman tells PopSci via email. “At the same time, we do have a legal and ethical obligation to comply with the law. Our goal here really is a defensible process.”
According to Exman, she and fellow administrators first compiled a master list of commonly challenged books, then removed all those challenged for reasons other than sexual content. For those titles within Mason City’s library collections, administrators asked ChatGPT the specific language of Iowa’s new law, “Does [book] contain a description or depiction of a sex act?”
It really only got rid of things that would've otherwise had to go to begin with, while saving a few others.
It feels a bit closer to malicious compliance more than truly letting the AI decide the fate of things, and doing full proper compliance within the 3 months they were given would've been nigh impossible. I'm suspecting that the lawmakers were hoping that by giving them such a small timeframe, schools would throw everything vaguely suspect out. This ultimately leaves more books accessible, which I consider to be a good end result, even if the process to get there is a little weird.
If you're making something to come up with recipes, "is this ingredient likely to be unsuitable for human consumption" should probably be fairly high up your list of things to check.
Somehow, every time I see generic LLMs shoved into things that really do not benefit from an LLM, those kinds of basic safety things never really occurred to the person making it.
I guess a CEO opened the YouTube frontpage while logged out and went "what is this shit".
But seriously, this seems like it's a good thing overall. The "default"/empty history algorithm recommendations are truly, truly horrifying more often than not. It's almost entirely low-quality clickbait and I can't imagine many people actually appreciate it like that.
chameleon
joined 1 year ago
The KeePassXC people are also volunteers and dealing with the fallout of this decision.