Man, that's not what I associate the abbreviation GCC with. 🤣

Bitcoin Twitter really seems to be dying.

It seems mostly drowning into Main Character Syndrome capture, engagement farming, useful idiots cheerleading grifters, with very short bursts moments of energized grasps for air of really good posts and discussions.

The trend is noise over signal.

It's kinda sad as it had a very good moment, but i guess nothing is for ever.

What is still unclear is a lot of important public discussions need to be had. But they seem to be Balkanizing and going dark. My DMs are full of things that would serve the commons. But people no longer have the patience for Eternal September arguments and socks.

Nostr could become one of the new bitcoin public squares, but we are definitely still far from it. Gotta find the purple pill formula for the bitcoiner nostr derangement syndrome. ✌️

i is simple...

source code available, with no restrictions on who can receive, use, modify, redistribute, sell.

auxiliary stuff around business process on how its developed have no bearing on its categorization as open source.

What does it mean to be open source? When I first got involved with open source bitcoin in 2017, I thought this was a simple question. However, it is far more nuanced that I rarely see discussed. There are at least 9 different gradations ... am I missing any?

8. External maintainers. Does the core team attempt to grow external contributors into maintainers and ultimately relinquish some power over the direction of the project?

7. Self-sufficient funding. Does the core team proactively seek external funding sources for development of the project so that the project can survive even if the founding entity abandons it?

6. Recruiting external contributors. Does the core team embrace and champion new contributors who aren't affiliated with the core team's organization?

5. Supporting external contribution. Does the core team prioritize and review external contributors PRs?

4. General vs. specific design. Did the team that created the software design it with only their specific application in mind? Or did they design it general enough to accommodate many types of future users?

3. Working in the open. That is, does a team work for months or years in private only to publish code for major releases? Or are issues and PRs in a public tracker with public discussion on a daily basis?

2. Permissive license. Does the license restrict commercial use or is it free open source like MIT License?

1. Source available. This one is straight forward.

What does it mean to be open source? When I first got involved with open source bitcoin in 2017, I thought this was a simple question. However, it is far more nuanced that I rarely see discussed. There are at least 9 different gradations ... am I missing any?

Excited for vexl - just installed the test flight and added an offer

WE WILL LAUNCH A NEW MINING POOL THAT DOES IT RIGHT.