janpio

What would you consider appropriate action for their incident team to be able to mark the incident on their status page as resolved?

Are you sure it is not just a AI authored rehash of the thousands of articles online that make the same points already?

Do the caveats mean that it could _not_ actually have had fast builds on all the platforms it supports? (Honestly asking if I connected the dots correctly here, this is not a snarky "actually" rethorical question...)

I like your optimism.

20 or so years ago him and czottmann wrote a nice little wiki software that I used, WakkaWiki. Following him/them and their work ever since. Crazy.

Isn’t Figma actually the tool used to plan and design the “airplane” level app? (Which of course does not mean it can not be airplane level itself…)

So what did Nexi really want, and how did it get mangled so badly that it came out as "specifically the usernames and passwords of our supporters"?

I would instantly install and sometimes choose this over the Youtube app.

https://addons.mozilla.org/en-GB/firefox/addon/window-titler... works great.

External source with some additional information: https://www.rubynewbie.org/ruby-newbie-is-joining-the-ruby-u...

Motivation for rename: https://x.com/moltbot/status/2016058924403753024 https://xcancel.com/moltbot/status/2016058924403753024

Clawdbot is the software, they installed their own instance of it and named it "rei". So an instance of Clawdbot named rei helped them to fix a problem in Clawdbot/rei they observed.

That's quite an interesting approach. Any information on how it works?

App doesn't load for me. One error in console:

> 20:39:02.367 Content-Security-Policy: The page’s settings blocked a script (script-src-elem) at https://www.google.com/recaptcha/api.js from being executed because it violates the following directive: “script-src 'self' https://js.stripe.com https://www.googletagmanager.com” 2 firebase-vendor-Cs-2scbC.js:1:431979

Not sure if that is the cause of course.

:shrug:

https://x.com/jaredpalmer/status/1998833736218271927

Seems fixed now:

https://huggingface.co/collections/mistralai/mistral-large-3

https://huggingface.co/collections/mistralai/ministral-3

Great job.

I was hoping this was a unification of the both layouts as well, that would have been really impressive. The mobile version of the article pages is great, but getting both versions from the same frontend would be an amazing case study.

Great idea.

Any plans for a Firefox extension?

What does "adopt #ChatControl negotiating mandate" mean?

So why? The link just goes to the project GitHub repo, and README does not explain as far as I can see.

Also includes news about a new Appstore, which can probably be seen as a reaction to the stories from last week:

    We’ve created our own Pebble Appstore feed (appstore-api.repebble.com) and new Developer Dashboard. Our feed (fyi powered by 100% new software) is configured to back up an archive of all apps and faces to Archive.org (backup will gradually complete over the next week). Today, our feed only has a subset of all Pebble watchfaces and apps (thank you aveao for creating Pebble Archive!). Developers - you can upload your existing or new apps right now! We hope that this sets a standard for openness and we encourage all feeds to publish a freely and publicly available archive.

https://ericmigi.com/blog/pebble-watch-software-is-now-100pe...

Supposedly resolved now: https://status.supabase.com/incidents/h0d0cp971rpy

Not accessible for me:

   Web sites prove their identity via certificates. Firefox does not trust this site because it uses a certificate that is not valid for docs.qalam.dev. The certificate is only valid for the following names: *.github.io, *.github.com, *.githubusercontent.com, github.com, github.io, githubusercontent.com, www.github.com
   Error code: SSL_ERROR_BAD_CERT_DOMAIN

I understood this to be related to this section:

> As well as returning HTTP 5xx errors, we observed significant increases in latency of responses from our CDN during the impact period. This was due to large amounts of CPU being consumed by our debugging and observability systems, which automatically enhance uncaught errors with additional debugging information.

(Just above https://blog.cloudflare.com/18-november-2025-outage/#how-clo...)

This other study looked a bit at the impact on the code longer term: https://news.ycombinator.com/item?id=45968758

The paper: https://www.science.org/doi/10.1126/sciadv.adw6833

Probably that it's a decent first step, with a well defined feature set and user expectations, so a nice thing to try before they figure out what to do next. And the article this comment thread is about is a reaction to one of their announcements in that regard: https://blog.mozilla.org/en/firefox/ai-window/

No, they used Claude Code as a tool to automate and speed up their "hacking".

As it is not directly clear from the title or abstract:

> This paper analyzes adoption, usage, messages, and output related to Cursor Agent — a coding agent that converts natural language instructions into generated code.

It took me far to long to understand your pun for (8)... :)

Out of curiosity: How does this deal with referential actions? (See https://www.prisma.io/docs/orm/prisma-schema/data-model/rela...)