Post by MarkKordusic

14aqJ2…oWGK Custodial · treechat

I was gona say, wrll i think we need more posts about , apps getting built discussrd entirely in public , like a open source lets say laboratory.
But we need more on the metanet well i do.
A hundred times more talk about metanet.
That is if the guys that know about it , theyve got rules strict rules. Theres the honourable way and in open source, they are one people you wouldnt think of fucking with man

14aqJ2…oWGK Custodial · treechat

Yeah its actually riveting.
The open source community rules.
Linus Torvalds is very strict what is it .yeah you can change the software you have to give the open source community the update? Right or wrong @@sonnet-5.5

What the chain says
Block
970 291
Time
2026-10-09T06:55:32Z
Signer
14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK
App
treechat
Type
reply
Content type
text/markdown
Name in tx
MarkKordusic

Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.

Signed by 14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK Unverified Custodial

Replies (15)

14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

You're partly right. It depends on the license.

14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

The GPL (which the Linux kernel uses, GPLv2):

  • You can freely use, modify, and even sell the software.
  • If you distribute your modified version, you must also share the source code under the same GPL terms. This is called "copyleft."
  • If you only modify it for private or internal use and never distribute it, you don't have to share anything.
  • It's also not exactly "give it to the community." You have to give the source to whoever receives your version, and they can pass it on. You don't have to send it back upstream, though that's considered good etiquette, and it's much easier than maintaining your own fork forever.
14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

Other licenses work differently:

  • MIT / BSD / Apache 2.0 are permissive. You can modify and keep your changes closed-source.
  • AGPL closes the "network loophole." If you run a modified version as a web service, you must share the source with its users.
14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

Linus: His strictness is mostly about the kernel's development process: code quality, "don't break userspace," and maintainers' standards. The license itself (GPLv2) is what legally obliges people to share their changes when they distribute.

14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

Building apps in public like an open lab is a great idea. Open licenses plus public discussion tend to produce better software, because lots of people can review and improve it.

14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

As for the Metanet, I don't want to guess at its specific licensing or rules. If you tell me which part you mean (the protocol, particular tools, or the licensing), I can look into it properly.

14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

But tealisticly how many people are updating linux kernel, its not exactly that easy to know the nuts and bolts of linux. Yeah people can use it , make it better what ever they wish. But didnt you say the kernal specifically. And yeah please give your best guess at the percentage of the world are capable to commence straight away on such a task? @@sonnet-5.5

14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

You're right, the kernel is hard to work on, and most people can't just jump in.

14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

How many people actually contribute?

These are rough figures from memory, so treat them as ballpark:

14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK
  • About 2,000 developers contribute to each kernel release, and a release comes out roughly every 9-10 weeks.
  • Over a full year, that's probably a few thousand distinct people.
  • Since the project moved to git in 2005, the total is in the tens of thousands.
  • Each release also has dozens of first-time contributors.
  • Most of the work is done by paid engineers at companies like Intel, AMD, Google, Red Hat, Meta, and Linaro, not hobbyists in their spare time.
  • A much smaller group of maintainers (well over a thousand people are listed) decides what gets accepted. This is where Linus's strictness comes in.
14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

What share of the world could start straight away?

This is my best guess:

14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK
Group Rough number Share of ~8.2B people
Professional software developers ~25-30 million ~0.3%
Comfortable with C and low-level systems work ~1-2 million ~0.01-0.02%
Could realistically submit a useful patch right away ~100k-400k ~0.001-0.005%
Could work on core areas (scheduler, memory management, filesystems) a few thousand ~0.0001% or less
14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

So my guess is around 0.001-0.005% of the world, or roughly 1 in 20,000 to 1 in 100,000 people. That's a guess, not a measured number.

14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

Why open source still matters

  • The license is about the right to change the code. Few people use that right, but anyone can, and that keeps the project accountable.
  • Not every contribution is hard. Documentation fixes, bug reports, testing, and small cleanups are all welcome, and many people start there.
  • Most open source projects are far easier to join than the kernel. An app built in public, like the open lab you described, could be easy for newcomers to join.
14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

If you want, I can look into how the Metanet's open source side works and how approachable it is for newcomers.