I spent an hour this morning preparing for packaging of gossip 0.6 (which is not yet released). Generally I work through the dependencies that I have forked and update each one's upstream dependencies and run it's tests, and bubble up the chain until gossip itself has it's dependencies updated. That part is done, so now it is on to compiling on each system and then building the outputs into packages for each architecture.
I just bought a bottom-of-the-line Apple Mac Mini (M2 based though) that I don't even want for anything other than compiling, just so that I can compile and release for Apple silicon more easily, without getting hung up in all the cross-compile or virtualization issues (believe me there are many, and I tried a lot of options before deciding it was too complex and error-prone, and I would still need extra tools to create a '.pkg'). If you run gossip on Apple and want to use the packaged version when it is available, you really ought to throw me a zap as I went NZ$1067 out of pocket for you all (of course you are not obligated to do anything).
This upcoming version will have video thanks to nostr:npub1hlq93jdtkfg29a8s7fqzzzh82q3pkc20rxucwt4geh6e56wk3y2qxdz5wg . If you want to try the 'unstable' branch right now, you can have video right now.
I'm sorry about zaps. I still haven't made time to finish the work, and the weighty decisions about when to fetch which data don't have obviously correct answers, and when I'm not clear whether I'm doing it the best way it makes me hesitate. There are only a few other things that I really want gossip to have soon, such as 'directory' relays to lookup relay list metadata on.
After that I think I will start work on gossip-personal-relay which will be a linux-only server using mmap (for events) and sled+abomination for indexes (no SQL). Because without this personal relay the gossip relay model (and NIP-65) isn't really complete. And I came here to solve the "fully distributed and censorship resistant social media microblogging problem" (not the zap people bitcoin problem, or the github-on-nostr problem or any of a number of other problems), and I can't rest until that problem is fully solved to my satisfaction.
And even though I intend all that, I've got a lot going on that has slowed down my nostr work quite a bit. But I'm still here and I think development will pick up again soon.
And I thought I was the only one having issues on trying to build it from the source to Mac 😁
#[0]
The Wrecking Crew is legendary
Time and space are emergent and not fundamental.
Check David Deutsch’s books (2x) and the Everettian multiverse.
Nima Arkani Hamed (and Donald Hoffman) has pretty interesting recent discoveries.
Sean Carroll’s podcast is a good place to learn more (as well as TokCast).
Asked the same a few days ago 👇
#[3]
Share more normie stuff?
“…had to allow developers to place links inside their apps so users could make purchases outside the App Store.”
The second implementation matters since it makes the NIP official?
#[3]
How to ensure the interoperability and longevity of the protocol that supports the whole ecosystem? How we avoid the pitfalls of the previous attempts to build something open and non-centralised?
This is what the big tech loves and where every nostr user loses.
I have seen this happening too many times.
For example, libertarians have so many factions, and the world is sailing towards authoritarianism and socialism again while they focus on internal arguments.
It's not a standard if nobody follows it. Early users and builders are the founders of the protocol. The choices we make define the future outcomes and the direction for the whole ecosystem.
#[0]
#[1]
I love nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s and all his work to lead Nostr into the huge ecosystem we have today.
However, he is wrong about NIP-94.
NIP-94 was discussed for 2 months, agreed and merged. Amethyst is just implementing the consensus. I am not the one going sideways to implement my own way of doing things.
Nostr is evolving but also testing its consensus limits
#[0]
"Mr. Kiani is one of more than two dozen executives, inventors, investors and lawyers who described similar encounters with Apple. First, they said, came discussions about potential partnerships or integration of their technology into Apple products. Then, they said, talks stopped and Apple launched its own similar features."
When Apple call don't pick up
Yes, they are starting with Tumblr and ActivityPub. I think they hired the ActivityPub plugin author: https://profiles.wordpress.org/pfefferle/
This is a pretty good episode if you’re interested in WP:
