Editors using the visual editor will now see a warning when they paste text that is likely to have initially been copied from one of five external generative AI chatbots into Wikipedia. This feature is known as LLM Paste Check. It is a type of Edit Check that is community configurable. The check looks for markers in the copied HTML and is not using content watermark detection. Edits will also be tagged so that patrollers can review them more closely. The feature helps newcomers add content that respects Wikipedia’s policies and makes it easier for experienced editors to identify problematic edits. Communities with local policies about LLM usage can adjust the wording and policy that is linked. The team apologizes that this was rolled out without a delay for translations.

 

[!WARNING] This language server may not be the one you're looking for.

I personally use it and will continue to maintain it until I don't use it anymore. There are new and interesting open source language servers being developed that can offer far more performant capabilities. I think Phpactor still offers some great features, especially in regards to code actions and I genuinely miss some functionality when using servers for Rust, Go and Typescrript.

There are many parts of this project that I'm proud of but ultimately it has some major short-comings in regards to perforamnce, accuracy and scalability that I'm not capable of addressing at this time. YMMV.

Bridging on a budget (blog.anew.social)
 

Over the past two years or so, we’ve managed to cut our serving costs 5x, from ~$0.15 per active user per month to ~$0.03.

For who never heard Bridgy Fed before (source: The GitHub repository)

Bridgy Fed connects different decentralized social network protocols. It currently supports the fediverse (eg Mastodon) via ActivityPub, Bluesky via the AT Protocol, and the IndieWeb via webmentions and microformats2.

 

Instead of navigating to a separate page, your agent sessions now live alongside your code, pull requests, and issues. View all sessions for the repository in one place, create new ones, and switch between tasks without leaving your codebase. One-click links make it easy to jump straight to the associated pull request. You can also archive sessions to keep things organized and page through your session history.

[–] 8 points 9 months ago* (last edited 9 months ago)

After searching online, it seems everyone knows that "たけのこニョッキ", which was a game from a TV program aired Wednesdays at 11 PM from 2003 to 2005? It's a game where several people call out numbers in order starting from 1, and if they overlap, they lose. And judging by the name, that posture is a growing bamboo shoot. You mentioned it was a bar, and this does seem like a game suitable for a noisy bar, so it's plausible.

  • source
  • parent
  • context
  • [–] [S] 1 point 10 months ago

    Wait, isn't the link self-descritive?

    After over 1,000 commits, 13 release candidates, 34 betas, and 12 alphas, we are thrilled to announce Mago 1.0.0 - the first stable release of the Mago PHP toolchain.

    Mago is a comprehensive PHP toolchain written in Rust that combines a linter, formatter, and static analyzer into a single, blazingly fast binary. Whether you're working on a small project or a massive codebase with millions of lines, Mago delivers consistent, reliable feedback in seconds.

  • source
  • parent
  • context
  • [–] [S] 1 point 10 months ago* (last edited 10 months ago)

    Mago is a PHP toolchain. I guess it is something similar to ruff/ty/pyrefly in Python, oxc in JavaScript, or Lux in Lua because it emphasis its speed and it is written in Rust. The author is also a maintainer of psl[1] and listed in JetBrains' 2025-2026 sponsorship program.[2]

  • source
  • view more: next ›