@jaz You look way too old to be this ideological. What did mommy do to you? Do you still have unresolved feelings?
Alex Gleason (alex@gleasonator.com)'s status on Tuesday, 30-Jan-2024 11:08:36 JST
Alex GleasonAs I'm learning about Bitcoin Lightning, I'm seeing some major red flags. To use it, you need an account with a service provider. It's a username/password type of custodial account. Then, the node has full control over your funds. They could shut down without warning, or transfer your funds. The only way to actually have control is to run your own node, but doesn't that defeat the purpose of Lightning? The whole point is to allow many users to transfer tiny amounts of money a lot, eg zaps. To me, it seems that Lightning nodes have all the problems of Mastodon. Imagine the problems of Mastodon, except it's your bank account. That's bad. What am I missing?
These should probably all be part of Webfinger, since Webfinger was designed to do all of it.
Also it would be neat to build a little React app where you can enter an internet identifier, and it pulls all these URLs to give information about what it all supports.
@97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322 Mastodon API is not ActivityPub. It's a REST API inspired by Twitter's legacy API. Old versions of GNU Social were even API-compatible with Twitter, and you could use GNU Social client apps to interact with Twitter. Mastodon developed this idea out separately from ActivityPub. In fact Mastodon was not even originally an ActivityPub server - it added that later.
Ditto exposes zaps in a way Mastodon API clients can implement, but it doesn't solve the ActivtyPub problem. Mostr does emit a "Zap" activity for zap receipts, but it doesn't actually contain all the necessary information you would need to verify the zap: https://gitlab.com/soapbox-pub/mostr/-/blob/main/src/activitypub/transmute.ts?ref_type=heads#L412-429 To complete it, I would need to add a stringified 9734 event in there and other essential fields like the preimage. I didn't add these things because I didn't understand how zaps actually work, and I'm only now starting to learn.
The main issue with ActivityPub zaps is that the zap spec itself (NIP-57) requires a Nostr event to be sent to the LNURL callback in order to get a receipt. To build that Nostr event you need a keypair for the user. The receipt is then delivered to a Nostr relay. This essentially means that to implement Zaps, you have to implement Nostr. The only way around it is to ignore NIP-57 entirely and just go straight to sending Lightning payments. But then there's no way to get the receipt on the ActivityPub side, and thus no dopamine rush notification or any statistics or context about zaps on the protocol at all.
Either a new spec would be required, for zappers like Alby to support an "activitypub" optional field in the lnurl callback (as they do for "nostr") and then emit an Activity of the receipt back to the AP server, or AP servers like Mastodon and Pleroma will have to implement basic Nostr features (maybe as a facade) to work within the existing system.
Alex Gleason (alex@gleasonator.com)'s status on Thursday, 25-Jan-2024 12:51:08 JST
Alex GleasonLightning Zaps on Nostr are of event kind 9735. This is a reference to the Lightning protocol, whose default port on nodes is TCP port 9735. This is itself a reference to the UNICODE LIGHTNING SYMBOL, which has an ID of 9735! Not the High Voltage emoji, the meteorological lightning symbol: ☇
Alex Gleason (alex@gleasonator.com)'s status on Wednesday, 24-Jan-2024 09:51:47 JST
Alex GleasonOpen Source is the secret of my success. Every great opportunity I've ever had was the result of Open Source. I skipped all the job interviews. I contributed patches and they hired me on the spot. I built open source and they found me. Without it, I would be just a regular man with precious ideas. Ideas aren't precious, no matter how good they are. Even the best creations aren't precious on their own. You could die an unknown Shakespeare. OPPORTUNITIES are precious. Open Source maximizes opportunities. People are resistant to it because they're afraid. Their heads are full of doubts, of tropes like "how will artists make money?" For that reason, brave people are able to benefit from Open Source while fearful people don't. If you want to be a successful software person and you're not already a millionaire, I would highly recommend building Open Source software.
@1bc70a0148b3f316da33fe3c89f23e3e71ac4ff998027ec712b905cd24f6a411@3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d Mastodon has a pure anarchist philosophy when it comes to decentralization. They think your server should have zero reliance on anything else. Bluesky takes the opposite approach, more like an authoritarian socialist one, where there is an high level of reliance on the official Communist party servers, but the whole stack is made up of user-interchangeable microservices. So for example, as a user you could run a custom timeline algorithm service and other users could point to it. It's basically the Twitter microservices topology but users can set the URLs to each piece. Importantly, identity is centralized on Bluesky's BGS.
Nostr does not take a pure anarchist approach to servers, but it does take a pure anarchist approach to clients. That's how it's different. Although in reality, with many clients relying on services such as nostr.build, and there being many singleton services like Primal or nsecBunker or whatever without the clear message to "host your own" as the main way of doing it, Nostr is a big mixture of everything.
I create Fediverse software that empowers people online.I'm vegan btwNote: If you have a question for me, please tag me publicly. This gives the opportunity for others to chime in, and bystanders to learn.