This #meshcore split is the latest in a line of projects needing to split as someone half inches the name that communities used for years.

See what recently happened to @vinyl_cache https://fosstodon.org/@vinyl_cache/116369631889505872

Before that a few years ago @Freenet had to split out to become #HyphaNet .

The Vinyl Cache Project (@[email protected])

Statement: On Vinyl Cache and Varnish Cache We received helpful feedback that, as of April 2026, the situation around Vinyl Cache and Varnish Cache might not be easy to understand for users and distribution package maintainers alike. This is an attempt to help clarify what Vinyl Cache and the new Varnish Cache project are. https://vinyl-cache.org/organization/on_vinyl_cache_and_varnish_cache.html

Fosstodon

I'm pretty pissed off that Fedora chose to stick with Varnish cache rather than provide @vinyl_cache @gentoo switched:

https://packages.gentoo.org/packages/www-servers/vinyl-cache

www-servers/vinyl-cache – Gentoo Packages

Gentoo Packages Database

@onepict if you added „and we use the name for new software that has different goals and does not share any code with the existing project“, then the @vinyl_cache situation would approach the @Freenet one.

@ArneBab True, I'm finding the similarities in the trademark and names, things that were held in common being held by entities other than the community .

@Freenet situation was an extra level of bad

@onepict Yes -- when potentially project-breaking power is in the hands of people who don’t represent the user-community or developer-community, that’s dangerous.
@ArneBab I think you handled the situation really well.