Perhaps. From what I see MQTT seems more for resource limited systems whereas this is more a formalization of Nostr-like mechanisms. Always interested in protocols so will have to dig into that a bit.
Released the specs I was talking about and they include an error reporting facility. Would love to get your thoughts. https://github.com/corgips/specs
Whatever you call Corgi, don't call it a protocol. There are and will be too many pieces (specs) for it to ever be more than a collection and a process for curating that collection. https://github.com/corgips/specs
That feeling when you release something and are then like what now, what now. Probably a good time to proof read. https://github.com/corgips/specs
Corgi needs a logo to replace that little blocky default thing. Anyone want to give it a shot? #artstr https://github.com/corgips/specs
Not sure if a PR is the way. Here's the repo which includes some initial /schemas. Really interested in your input, especially since nobody's used any of this stuff yet. https://github.com/corgips/specs
From here the plan #1 is to operate the process as it's spelled out, which includes methods to update that process. Need to find more facilitators to fix the bus factor, get the word out, collect feedback on details of the initial specs, and encourage folks to jump outside the box and try a branch! https://github.com/corgips/specs
I've just released the Corgi specs out of compassion for everyone who's struggled to make decentralized social media a reality, because frankly I've worked up the courage to describe my vision in specs, and lastly to try and apply wisdom, not just what I can bring but, the amazing wisdom of the crowd which is of course really about those you out there who are experts in your respective fields.
Nothing excites me more than possibility, but then of course it takes courage to explore sometimes. This new spec garden is an example of that. It's about thinking outside the box to see what better ways are possible. That's why I'm going ahead with it in a sort of ultradraft state to share and see what may come. https://github.com/corgips/specs
Alright let's do this. https://github.com/corgips/specs
GM, gonna be a fun day!
Doesn't seem so AND what a great opportunity! Generate one as first 8 digits of hash of title, platform, initial year of release.
There have never been so many ways available to us. Why not try it?
Airborne ingredients ✔️
Nobody's talking nearly enough about Let's Encrypt's free certs for IP addresses. Aligns really well for systems that have their own naming schemes, webs of trust, hint hint
Planning schemas at the core of these new specs. I'm by no means an expert, just understand the value of spelling things out so I hope you'll share your thoughts once the drafts are out.
Guess that means I'll be out with some drafts sometime on the 4th of July. Independence Day but independence from what?!
Have selected an organization name for the new spec garden and now deciding where to launch. Not to skew the results but currently Github has a wild if statistcally insignificant lead over Codeberg. 9h left to vote! https://pollerama.fun/respond/8a2161da1220e4b84e7403a42e93c3821bf470e093cb48bf9f7087104fde136b
Excellent. I'm interested to look into this more later. Was it created for a specific project or what was the motivation?
Where can one find this Voyage app?
Probably submit a court order to Google or the phone provider if they have their sw on it and voila.
One of the ideas I'm excited about is type schemas. In the spec garden there'll be a place to publish json schemas for every event type which will be versioned right along with the specs. I imagine this will make generating code so much easier.
Gm 🤙
Inspired me to try more brushes in Procreate and then frustrated with that, actual oil painting.
I see no problems here. Since you get shit done, this is how it should be.
I figure if nothing else I'll help improve the docs, but I'd like to get to a state of being able to browse by http://{pubky}
If you are willing to implement Mainline DHT from scratch, go for it. But if you are OK with using an off the shelf implementation here is how to implement Pubky from scratch:
1. Encode a DNS reply packet containing the endpoints you want, for example www. A 3600 IN vitorpamplona. com
2. publish that packet using Mainline PUT mutable rpc method using an ed25519 keypair.
3.on a different machine, make a GET query with Mainline for the Public key from step 2
4. once you resolve the encoded packet parse it and find www.
congratulations, now you made https://www.
there is of course more to it like work on a home server that stores your data for you and republishs your packets on Mainline periodically and offer a simple but open api, etc.
but the main thing here is what I described above, if you don't think that is valuable, then that is fair.
If you don't want to start from scratch, then you can do what I just described using this GUI https://app.pkarr.org , or if you can tolerate rust, you can go to https://pkarr.org where you can read more about the system, but also use the examples in the pkarr directory to publish and resolve packets and get a feeling for the speed and reliability.
so, does a censorship resistant DNS that can fade in the background and be taken for granted by web developers and make all the rest of web technologies usable in a more sovereign way and offer a credible exit from cloud hosts, does any of that sound interesting?
happy to answer more questions.
I'd like to setup my own pkarr-type service. Do I need pkdns or just pkarr or is more required. If you can give me a high-level checklist I'll try and set it up and submit PRs as I go.
Not sure I want the same key used for even more things, but pubky looks interesting. Going to give it a try today.
Sat down yesterday to write a page about wisdom for Nostr and this is what came out
April 24th, 2024 - Wisdom, Competition and Success
Nostr is a strangely wise place. It's good because it helps us appreciate what we have while sharing collective insights about the future. For example we know Nostr is small but that each platform that grows and dies gives us a chance to make it the next big one.
Talk to a CEO in their early days and they tend to be idealistic wishing to democratize the net or disrupt finance but time and time again as the numbers grow they get more focused on the bottom line. The money and power displace the ideals. This is one reason we believe decentralization is so important. It places a ceiling on how much power any one entity can amass.
The downside of this however is it can extend as a philosophy into everything. No relay should get too big. No client should get too much market share or strong-arm the protocol. In this way romance for freedom and decentralization can majorly slow us down.
We know our principles around open source software, resiliency of decentralization and the freedom to tinker. We'll always have those. It's important however to be mindful that competition to create the next dominant platform is fierce. The wise path is to rally around what's working best today.
What I don't understand is if the Agents can take away Neo's mouth how come they can't like take away all of the hackers legs when they try to run?
Been watching the Matrix trilogy this week and finding a lot more there than when it first came out. At first I was put off by the humans as batteries thing but once you get past that, the embedded philosophy feels prescient with respect to how digital our lives have become. Always fun to see the red/blue pilling scene as well.
Also enjoyed this article tying the story in with other works.
https://fivebooks.com/best-books/quantum-physics-reality-jim-baggott/#book-57085
#matrix #redpill #bluepill
Been watching the Matrix trilogy this week and finding a lot more there than when it first came out. At first I was put off by the humans as batteries thing but once you get past that, the embedded philosophy feels prescient with respect to how digital our lives have become. Always fun to see the red/blue pilling scene as well.
OMG I love the Kandinsky so much. Might have to make a print! Excellent work.
