Bonum Certa Men Certa

Gemini Protocol's Originator: “I Continue to Care About This Project and I Care About the Community That Has Formed Around It.”

Solderpunk



Summary: 'Solderpunk' is back from a long hiatus; this bodes well for Geminispace, which grew fast in spite of the conspicuous absence

AS we noted 4 days ago, Gemini space had become very important to us. It's growing very rapidly (it's hard to correctly estimate the overall size, but crawlers/spiders see almost 4 times as many capsules this year compared to last year). Recently, some people expressed concerns about alleged stagnation or rather a lack of changes to the original specification (not that everything must change or expand over time). Then, some people asked for patience [1, 2], knowing that 'Solderpunk' was likely to return some time soon and finalise the specification. As of minutes ago, there is already a proposal to freeze the Gemini specification.



Well, 'Solderpunk' probably wants to keep it simple. And he's back now, having just posted an update with plan for the specification:

Geminauts!



Lo, I have returned.

And I have come not to bring peace, but the sword.

Well, not really. Sorry, couldn't resist a little drama.

But I *have* come with a strong resolve to move things forward quickly, decisively, and if necessary unilaterally. I will be putting the "dictator" in BDFL (but not ignoring the "benevolent").

My thoughts are something like this:

The never ending discussion (and at times heated argument) that has characterised the efforts to collectively and openly finalise the spec using this mailing list, and the associated risk of leader burnout, now feel to me like they are a larger risk/liability to the project than the prospect of making slightly suboptimal and/or unpopular decisions when wrapping things up relatively quickly and without agonising over every little detail. The sooner the spec is finalised the sooner we can spend more of our time and energy reading and writing Geminispace content. People who aren't interested in spending time and energy doing those things have no place playing a strong role in deciding how to finalise things, anyway.

It's clear that any hope of unanimity in the community on exactly what Gemini should look like is long gone. There are too many people coming from too many technical backgrounds for us all to agree on what is necessary and what is extraneous. Anything resembling "design by committee" will likely result in bad compromises leaving everybody unhappy. Better to have decisive leadership with a clear vision. This will leave some unhappy. It's unfortunate, but it's inevitable. Gemini can't be everything to everybody.

Despite my total lack of involvement for several months and the lack of any progress on the spec, Geminispace *itself*, which is our real goal, has neither stagnated nor shrunk. It has only gotten better. Awesome things like smol.pub have turned up. All the time there are more and more people setting up little digital homes in Geminispace, who accept and embrace Gemini as it is right now, and many of them are very happy with the status quo. They are writing truly wonderful content, and I have not come across a single thing written there yet which made me think "right now this is merely good, but it could be excellent if only Gemini supported X, Y or Z". And all of this is hosted on diverse servers and compatible with diverse clients, including clients which have not been updated in months. All of this says we have gotten the most important things right or close enough to right already, and there is no risk of catastrophically messing anything up if we simply resolve outstanding technical issues with the minimum possible change. Additional capacities in the gemtext format are not necessary. That's not just, like, my opinion, man, that's an empirical fact. Geminispace is there. It's *exactly* the kind of space I originally envisaged.

I will start wrapping stuff up, via changes to what have always been the canonical versions of all relevant documents, hosted at gemini.circumlunar.space, as quickly as I can. I am not going to take the time to justify every single decision against all real or imagined objects in long posts to the mailing list or my gemlog. Maybe I will do this retrospectively some day, but for now I just want to get it done. I will act largely alone in this regard, but I'm not going to completely disregard all external input. A lot of people have put a lot of of time and care into thinking and writing about these issues both on this list and in the git trackers that sprung up once I delegated spec finalisation to Sean. I'm going to read that stuff and I'm going to be be guided by it, and I will reach out to individual people for clarification when I feel it necessary. I am genuinely thankful to all of those people for their efforts and I do not intend to be dismissive of them.

If I sound angry and frustrated, I apologise. I mean, to some extent I am, but not at particular people or at the community, I'm angry and frustrated at vague abstract things like human group dynamics and viral internet hype cycles. I continue to care about this project and I care about the community that has formed around it. I acknowledge that I am far from blameless in how this year in Gemini has turned out. I hope the community still has some faith in me, and I hope everyone understands that I'm doing this because I honestly think it's for the best, and not because I want all teh [sic] power. I don't want *any* power! But nobody I know and trust enough to give the power to wants it either, and big formal multi-person decision making is not going to yield good or fast results, so, here we are.

I'm not going to have time to do this *and* follow the list closely and reply to any and all questions. But I will make a genuine effort to keep the list informed as I work.

Cheers, Solderpunk


As a reminder, Gemini is a new project (it only 'feels' old or nybrutalist) and the specification is still work in progress. Regardless, we're an early adopter and we're pleased to see how fast Gemini grew this past year. Having the founder back in the game (to do technical work on the specification) is icing on the cake.

Recent Techrights' Posts

Who really owns Debian: Ubuntu or Google?
Reprinted with permission from disguised.work
Keeping Computers at the Hands of Their Owners
There's a reason why this site's name (or introduction) does not obsess over trademarks and such
In May 2024 (So Far) statCounter's Measure of Linux 'Market Share' is Back at 7% (ChromeOS Included)
for several months in a row ChromeOS (that would be Chromebooks) is growing
Links 03/05/2024: Microsoft Shutting Down Xbox 360 Store and the 360 Marketplace
Links for the day
Evidence: Ireland, European Parliament 2024 election interference, fake news, Wikipedia, Google, WIPO, FSFE & Debian
Reprinted with permission from Daniel Pocock
Enforcing the Debian Social Contract with Uncensored.Deb.Ian.Community
Reprinted with permission from Daniel Pocock
Gemini Links 03/05/2024: Antenna Needs Your Gemlog, a Look at Gemini Get
Links for the day
IRC Proceedings: Thursday, May 02, 2024
IRC logs for Thursday, May 02, 2024
Over at Tux Machines...
GNU/Linux news for the past day
Jonathan Carter & Debian: fascism hiding in broad daylight
Reprinted with permission from disguised.work
Gunnar Wolf & Debian: fascism, anti-semitism and crucifixion
Reprinted with permission from disguised.work
Links 01/05/2024: Take-Two Interactive Layoffs and Post Office (Horizon System, Proprietary) Scandal Not Over
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Wednesday, May 01, 2024
IRC logs for Wednesday, May 01, 2024
Embrace, Extend, Replace the Original (Or Just Hijack the Word 'Sudo')
First comment? A Microsoft employee
Gemini Links 02/05/2024: Firewall Rules Etiquette and Self Host All The Things
Links for the day
Red Hat/IBM Crybullies, GNOME Foundation Bankruptcy, and Microsoft Moles (Operatives) Inside Debian
reminder of the dangers of Microsoft moles inside Debian
PsyOps 007: Paul Tagliamonte wanted Debian Press Team to have license to kill
Reprinted with permission from disguised.work
IBM Culling Workers or Pushing Them Out (So That It's Not Framed as Layoffs), Red Hat Mentioned Repeatedly Only Hours Ago
We all know what "reorg" means in the C-suite
IBM Raleigh Layoffs (Home of Red Hat)
The former CEO left the company exactly a month ago
Paul R. Tagliamonte, the Pentagon and backstabbing Jacob Appelbaum, part B
Reprinted with permission from disguised.work
Links 01/05/2024: Surveillance and Hadopi, Russia Clones Wikipedia
Links for the day
Links 01/05/2024: FCC Takes on Illegal Data Sharing, Google Layoffs Expand
Links for the day
Links 01/05/2024: Calendaring, Spring Idleness, and Ads
Links for the day
Paul Tagliamonte & Debian: White House, Pentagon, USDS and anti-RMS mob ringleader
Reprinted with permission from disguised.work
Jacob Appelbaum character assassination was pushed from the White House
Reprinted with permission from disguised.work
Why We Revisit the Jacob Appelbaum Story (Demonised and Punished Behind the Scenes by Pentagon Contractor Inside Debian)
If people who got raped are reporting to Twitter instead of reporting to cops, then there's something deeply flawed
Free Software Foundation Subpoenaed by Serial GPL Infringers
These attacks on software freedom are subsidised by serial GPL infringers
Red Hat's Official Web Site is Promoting Microsoft
we're seeing similar things at Canonical's Ubuntu.com
Enrico Zini & Debian: falsified harassment claims
Reprinted with permission from disguised.work
European Parliament Elections 2024: Daniel Pocock Running as an Independent Candidate
I became aware that Daniel Pocock had decided to enter politics
Publicly Posting in Social Control Media About Oneself Makes It Public Information
sheer hypocrisy on privacy is evident in the Debian mailing lists
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Tuesday, April 30, 2024
IRC logs for Tuesday, April 30, 2024