nostr:npub1xv8mzscll8vvy5rsdw7dcqtd2j268a6yupr6gzqh86f2ulhy9kkqmclk3x I don't quite remember what the outcome of your experiments with adding v4v to RSS feeds was. Is there a spec (informal or not) by any chance, that I can use to add Lightning addresses to Substr feeds?
Why aren’t we doing more stuff with Nostr and Tidal? It’s really cool, they launched it back in June, I’ve seen it pop up a few times but we should do more with it.
Like make ‘share a song’ more a feature in the app and auto login with your nsec when you see events with Tidal content.
https://developer.tidal.com/blog/tidal-embeds-the-other-stuff-transmitted-by-nostr
Because that's not just a centralized platform, but also one that exists to extract rent from so-called intellectual property (which isn't actual property)?
"MAINTAINERS: Remove some entries due to various compliance requirements."
Substr is almost ready for a public alpha release. If you want to host your own blog on Nostr soon, follow my posts, and/or the releases feed on Gitea.
Sneak preview: https://nostr.kosmos.org/~raucao
Source code (not yet documented): https://gitea.kosmos.org/kosmos/substr
Please tell me that nobody is using the name "substr" for any of their Nostr software yet. (I did do a quick search and couldn't find any results.)
He must be really annoyed by the Saylor pig banner that still decorated the facade of Paralelni Polis (RIP) until recently.
OK, I have profile pages with linked article lists now, as well as pretty URLs for both the profile and article pages. The only things still missing are RSS feeds and out links to actual Nostr clients.
GN
Initially, I didn't want to spend the whole Sunday on this, but it's basically almost done now. I started building a nice server-side renderer for long-form content on our Nostr relay:
The next step is to create human-readable URLs, i.e. `/@username/article-id`. But my favorite feature will be `/@username/articles.rss`, because if it doesn't have an RSS feed, it's not a blog.
It works, but you should add higher pre-set amounts than 1K in my opinion.
I was thinking about alternative URLs just yesterday (for a different, but similar use case). I think it should still support the full URL and reference it as the canonical one via `link rel="canonical"` in the HTML. You also need the full URL to link out to other clients from there anyway.
That's completely irrelevant if there's one instance with 99% of users on it, which doesn't acknowledge any DIDs other than a literal placeholder one.
Shout-out to all the fedimint devs at last weekend's bitcoin++ in Berlin!
In fact, my biggest takeaways of the conference were:
1. That it's not just the Fedi company/investors employing devs to work on the protocol and reference implementations
2. That every fedimint federation is its own little consensus network, that you can build additional, interesting functionality upon by implementing your own fedimint modules
3. That the lack of fedimint wallets was mostly due to how difficult it is for client software to talk to a federation of nodes instead of a single Web server, but that this has just been addressed with the brand-new Web SDK, which I test-drove and was able to build an MVP wallet upon within less than an hour
⚡️Alby Hub in Warsaw --> Alby Go in my hands in Guatemala --> bar’s wallet ⚡️
In just a few seconds https://video.nostr.build/aab250f5b5e5636dcf7a3df960705c611238f4439b6f672967cac450108984d0.mp4
WTF, they actually gave up entirely on sovereign identity?!
"In principle, the cryptographic keys for signing repository updates and DID document updates can be held directly on the user’s devices, e.g. using a cryptocurrency wallet, in order to minimize trust in servers. However, we believe that such manual key management is not appropriate for most users, since there is a significant risk of the keys being compromised or lost.
The Bluesky PDSes therefore hold these signing keys custodially on behalf of users, and users log in to their home PDS via username and password. This provides a familiar user experience to users, and enables standard features such as password reset by email."
Today, I went back to working on Nostr onboarding features for Kosmos users (whom we haven't even told about all the Nostr functionality yet).
Slowly arriving at something usable. This is all loaded asynchronously from the Ruby app server now (once authenticated). No custom JS needed until signing the prepared events later:
If you develop and/or maintain a Nostr client, which allows onboarding new users, and your onboarding doesn't involve creating and publishing a NIP-65 relay list... please fix that!
Happy Friday deployments, everyone! 🚀
I think prediction markets are pretty neat. They were the primary way of predicting the outcome of elections prior to the invention of modern opinion polling.
In recent weeks the polymarket for the US presidential election has noticeably diverged from the polling. The polls have stayed flat, it’s essentially a coin flip as to who will win. The prediction markets have broke to Trump with a 60% chance of winning. Is this a real shift that bettors are seeing vs the polls or is someone manipulating the market. You could make the argument that placing bets on your preferred candidate is a capital efficient way of shifting the outcome. Journalists use the markets to shape their coverage and will start writing articles about momentum when they see the prediction markets shift. Elections are very messy so it’s easy enough to find evidence of momentum in any direction if you’re looking for examples to fit the narrative. And the narrative about a candidate pulling ahead will lead to more press and focus and is likely to help the candidate get more votes on Election Day.
All of this to say it appears one person is attempting to do this in favor of Trump.
https://www.cryptopolitan.com/bettor-trump-harris-betting-pair-polymarket/
It was also considerably skewed towards Harris before. And the centralized UK bookies e.g. give Trump even better chances than current Polymarket odds. Paddy Power has them at 8/13 and 11/8, which translates to 61.90% and 42.11% respectively.