If she was within her allotted time for a comment that was completely off-topic but otherwise complied with the public comment process, and her flipping off the council was, as she claims, only after it was clear that she was going to be interrupted by the police, then that does seem different than actually interrupting the discussion or refusing to leave.

This restriction does not appear to actually be enforced, eg, if I recall correctly the VARA HF/FM modes do not have published specs anywhere near sufficient to decode them, to the point where there are projects trying to reverse engineer them.

And with that said, for experimental work, this approach does not make things fully reproducible; it only makes the analysis reproducible. There are always factors that influence experiments: research is by definition at the edge of our understanding, and reality has countless variables, including ones no one has thought of, known about or thought important.

Yes, that goes against most of Fairphone's own advertising, but it was consistent with my experience of the phone and discussions on the forum: security updates frequently so far out of date that some software could not be run, flimsy components inconsistent with advertising (yes, the battery was nominally swappable, but the snaps on the back would break easily, and support would claim that it was not intended to be removed regularly), parts that were frequently out of stock, and of course, whole new phone designs every generation rather than Framework-like component upgrades.

It seems like they may have improved since then, but those problems, along with the atrocious security (FP4 used AOSP's public test signing keys, with publicly-available private keys, for its firmware) and sketchiness around specs, standards and openness (especially for the camera), generally turned me off the company.

I know arXiv has taken some measures to combat spam like this, but it seems like they’ll need to do more. There’s just very little barrier now to creating giant slop papers like this and then dumping them anywhere that won’t reject them. It is an insult to everyone’s time, and I can’t imagine they expect people to actually read this. If the expectation is that everyone will use an LLM to interpret it, then maybe they should have at least had a few more rounds of tightening and polishing the paper, even via LLM, to save the redundant token use.

This is not just for security, too. Using Fable for anything that could be remotely construed as being connect to chemistry or biology was impossible until a few weeks ago. Now it is slightly better, but still fails on many completely innocuous projects.

So as other models advance, Anthropic's sole frontier offering to entire academic fields remains an Opus that seems to get worse in capability each release. They're starting to become a joke in my field: at a conference a few weeks ago, one presenter laughed when I asked about his use of Fable and pointed out that it would downgrade if the letters 'd', 'n', and 'a' were anywhere near each other, which is not that far from my experience.

[1]: https://arstechnica.com/information-technology/2026/08/pbs-s...

I certainly interpreted the response as meaning that anyone actually trying to implement the feature would find the PR an exercise in frustration. It may be there were some cultural confusions about context and implication, but considering that they locked the issue, people weren't exactly encouraged to ask for clarification. And the developers have a sketchy enough reputation already from other incidents.

https://www.btp.police.uk/SysSiteAssets/media/images/british...

Bans on unsolicited calls, or do-not-call lists, can be effective for the former, as it moves the behavior from being legal to being illegal, while for the latter, they are already breaking laws, often in a more severe way, and technical measures or enforcement are more important.

A phone company trying to trick someone into paying more per month for something they don't need is likely to be worried about being fined if caught calling a number on a do-not-call list. A scammer pretending to be the tax office and demanding payment of supposedly unpaid taxes is going to be in trouble if caught regardless of rules about what numbers can be called.

In doing so, the article perhaps obscures the point that business collusion, I expect, is more often built around legitimate reasoning taken to illegitimate extents and conclusions, than around outright fabrications.

Being a researcher somewhat connected to chemistry and biology, Fable has been the most useless model I have ever tried. Essentially all work has instantly downgraded to Opus.

Looking at community conversations, there actually seems to be little clarity over this, and quite a bit of confusion. Several established members of the community seem to be saying that the ToS actually only bans "cryptocurrency related projects" that "[harm] the reputation of Codeberg", and that direct cryptocurrency projects that don't harm Codeberg's reputation are actually allowed, saying that the current banner is a mistake and is in the process of being changed (while they have their own systems and are not on Codeberg, I'm guessing GNU Taler might be an example of a cryptocurrency project that would be allowed). In fact, this appears to be within the official interpretation used when locking the discussion thread on the change ([1] refers to [2]).

[1] https://codeberg.org/Codeberg/org/pulls/1254#issuecomment-19... [2] https://codeberg.org/Codeberg/org/pulls/1254#issuecomment-19...

While I can't find something specific about it in the new ToS, the new blog post notes that "side projects and experiments", and "specific tools and custom scripts that would be unlikely to find a community anyway" are "discouraged", but are "tolerated in practice" if they only use minimal resources. This is stated as being regardless of LLM use. So some of my repositories are apparently already borderline in the community's opinion (it's not clear how they judge use of resources, but I only use self-hosted runners).

But there also seems to be an increasing sense that many active members see Codeberg as a space for a particular type of FOSS, within a particular, normative view of what development and communities should look like. This ties into the "side projects and experiments" comment, and to the general tone of the AI blog post on what they want Codeberg to be and not be. The point about "projects with a single developer and virtually no users", about "large ghost projects", and so on, are within the context of AI, but are derided in a wider sense.

Some of my repositories look like single developer experiments with no users or community, but aren't. I'm ultimately a scientist, not a typical developer; users typically communicate by email and at conferences, and cite my software and associated papers in their papers rather than starring repositories on forges.

And yes, much of the discussion around these questions often falls into the argument that projects that are good will be fine, because they'll be accepted despite the rules, and that any concern about specifics is unwarranted. But I can't know that I won't be targeted by Codeberg having an increasingly normative view of what 'proper' community development looks like.

(Yes, I realize I'm free to use something else. I'll likely end up moving my repositories off Codeberg and onto some combination of my own Forgejo instance and Github. The lack of federation in Forgejo heavily penalizes not being on a major instance, however. Meanwhile, as much as I encourage using DOIs for citations rather than URLs, people often do the latter, so staying on an instance that might decide to ban my projects can create lasting problems: one of my whole reasons for starting to migrate to Codeberg was because it seemed organizationally stable.)

For clocks, however, there is the iconic Swiss railway clock [1], which dates back to 1944 and has a jumping minute. For those, however, the jump is actually meaningful in itself, in they're synchronized by a master clock that has a one minute impulse, and the jump is actually the moment of the impulse.

[1]: https://en.wikipedia.org/wiki/Swiss_railway_clock