rmccue

It's often used as a tone signifier: https://www.theguardian.com/society/2025/feb/18/death-of-cap...

What do you see as the benefits over Nightjet’s Mini Cabins?

Also, interesting to see just after the launch of https://noxmobility.com/ which is targeting the same market.

TSC co-chair here - one of my fellow co-chairs (Mika Epstein, aka Ipstenu) was the lead of the plugin review team for a long time, and several other contributors have been very involved in the plugin review processes, so definitely something that’s top of mind for us.

The contributors who worked on this project (including myself - I'm one of the TSC co-chairs) are very familiar with the internals of WordPress - we were the ones who wrote them :)

Blocking the way that FAIR works would break the way that premium plugins work, which would break a huge amount of the ecosystem, so we think it's unlikely - WordPress core would need to be patched.

The protocol repository [1] has more documentation on how to implement your own repository and we expect there’ll be many implementations of it over time - for launch, our proof-of-concept repo is built on WP since it integrates with Git Updater which is already widely used. (We’ll try and publish to Packagist now that it’s public too!)

[1]: https://github.com/fairpm/fair-protocol

Indeed, Mozilla only recently allowed Debian to use the brand for their modified version: https://en.wikipedia.org/wiki/Debian%E2%80%93Mozilla_tradema...

The library I was maintaining (SimplePie) was an RSS feed parser which supported every flavour of the RSS/Atom specs. Because of the history of those particular formats, there were a huge number of compatibility hacks necessary to parse real-world data, and cases where the "spec" (actually just a vague page on a website) was inaccurate compared to actual usage.

This was a while ago (10+ years), but my recollection is that someone presumably had reported that parts of the library didn't conform to the spec, and Debian patched those. This broke parsing actual feeds, and caused weeks of debugging issues that couldn't be replicated. Had they reported upstream in the first instance, I could have investigated, but there was no opportunity to do so.

As someone who maintained a (PHP) library that Debian distributed, it fucking sucked that they made source modifications. There were a number of times where they broke the library in subtle ways, and there was little to no indication to users of the library that they were running a forked version. I also never had any contact from them about the supposed "bugs" they were patching.

Seems reasonable to have the most frequently used numbers close to the user; I wonder if there might be something of Benfold’s law involved, where lower digits are more frequently used. https://en.wikipedia.org/wiki/Benford%27s_law

Ben Thompson is working on Passport, which seems to be a self-hosted (WordPress-based) Substack: https://stratechery.com/2021/passport/

He gave a talk on it at WordCamp Asia at the start of last year, although I haven’t heard of any progress recently on it.

Yeah, agreed! I titled my guide "Practical IMAP" for reason (and almost called it "IMAP As She Is Spoke"). The standards are useful to a point, but actually to jeffbee's point the internet has evolved a lot since then, and how to actually work with modern email is a pretty underdocumented - including by Google themselves on the Gmail-specific parts.

My memory is hazy on it, _but_ from memory, there were some issues around IDs and persistence which don't occur on other servers, as well as the auth being a bit funky. (Gmail also uses its own extension to the protocol for IDs instead of using eg OBJECTID.)

To be clear, I have no opinion on IMAP or what things _should_ do; I certainly was not using IMAP software in the 1990s :) However, trying to implement a client that works across providers does mean trying to operate per the standards, which was a struggle and why I started documenting it :)

I started writing a guide to IMAP back when I was working on an email client: https://github.com/rmccue/griffin/tree/master/docs/imap

Pulling large amounts of data for things like threading can be difficult on certain servers; my preferred approach ended up being to pull every ID and thread ID to maintain an in-memory tree. (This was, iirc, partially because Gmail’s implementation was slightly crippled with relation to threading.)

(I never finished the guide because I stopped on the project, alas - if IMAP were easier to work with, I might have finished it! And sadly, no JMAP support on Gmail, and the gateway was broken.)

I’d recommend adding your first (and maybe second) paragraphs directly to your readme - this is a much clearer description if you don’t know what landlock is already!

That might not be the only reason: https://www.theguardian.com/us-news/2025/mar/19/trump-musk-f...

> France’s research minister said a French scientist was denied entry to the US this month after immigration officers at an airport searched his phone and found messages in which he had expressed criticism of the Trump administration.

Annoyingly, they no longer show your IP on their web homepage.

Nit for schacon: in the "Listing branches" section, you say branch.sort + column.ui and talk about these as first/second options, but the commands are in the opposite order so it reads a little confusingly.

> That's a USofAian "suburb" .. not a well designed suburb.

If you don’t want to say “American”, you could use Usonian, a term coined by Lloyd Wright himself: https://en.wikipedia.org/wiki/Usonia

> Started/founded are basically the same, no?

My point was that his name is Mike, not Mark :)

The value of WordPress is in the brand, the ecosystem, and the community, and we’re all trying desperately to hold that together.

> Him and Mark Little started WordPress

Nit: Mike Little was the other cofounder - you might be confusing him with Mark Jaquith, one of the lead developers and largest contributors early in the project.

Also, with regards to contribution count, it’s important to look at “props” which are the credits given for commits. WordPress has a contribution system that predates things like git’s multiple author support, so users are given props via commit messages, and a system tracks this for attributing credit for each release.

This isn’t unexpected; I’ve been deactivated on Slack since very early in this dispute, and later banned from the issue tracker as well. I’ve been contributing for 20 years to the project, am a committer, and built several large parts of WordPress including the REST API.

Matt is banning anyone who speaks out at all, even when they agree with points he’s made. A large group of contributors felt they had to make an anonymous statement from fear of the same retribution I suffered: https://www.therepository.email/core-contributors-voice-conc...

(I am a less active direct contributor these days, so I’m still able to contribute even while blocked - but many people’s livelihoods depend on it, as sponsored contributors.)

I’ve been deactivated on Slack since very early in this dispute, and later banned from the issue tracker: https://journal.rmccue.io/468/on-contribution/

The only potential cause of this were some posts discussing the arguments behind the original lawsuit - they’re written in my personal capacity, and I’m not a partner of WP Engine. Matt is simply banning anyone who speaks out at all, even when they agree with points he’s made - it’s nothing to do with their partnership status.

(I’m not a WP Engine partner, and my day job is running a competitor to them. Aside from that, I’ve been contributing for 20 years to the project, am a committer, and built several large parts of WordPress including the REST API.)

> The ILS are supposed to be built on level surface or "frangile" structure

Nit: I think the word you want is “frangible”, easy to break.

It would be great to have a reverse sort; if I’m sorting by cost of living, I’d like the cheapest first.

> I have money and I have a URL, how do I send money to the publisher of that URL?

This question could easily be “I have money and I have a person’s name and address, how do I send money to them?”

The only way to do this consistently would be to mail them physical cash, since there’s no way to consistently send money electronically across the world (and you’d have a currency conversion problem too - if someone mailed me US$0.23, it’s not worth exchanging it).

Building micropayments infrastructure requires building broader financial infrastructure, not just adding a meta tag. This can use existing infrastructure to some extent, but it’s a pretty big challenge.

(For example, in Australia, you can send someone money if you have their email address (via PayID), so you could bootstrap that part - minus the international part.)

As far as I've seen, it was only sold in the US, so EU regs wouldn't apply.

Also: WP Engine Must Win -https://news.ycombinator.com/item?id=41653480

(Disclaimer: my submission and post. I am a WordPress core committer and built the REST API for it.)

WordPress cannot relicense; it’s a fork of a GPL project originally (b2) and there is no copyright assignment, so you would need explicit permission from every contributor including the forked project’s.

The advantage of AirPods for social stigma is they aren't solely hearing aids, so you have a type of (casual) plausible deniability about why you're wearing them. They won't draw people's attention in the way that hearing aids (because they're different/unique) do.