Avatar
blu
3f503eef50d5b9f73af8d44ed380e4a3090e2c63631bffa9cd919bea38356a64

Oh that's awesome. Can I ask, what's the utility of adding Nostr here? Is it easier, better auth? I.e. a challenge to the email way of doing things?

Thanks for the pointer, I'll check nostr:nprofile1qqsggm4l0xs23qfjwnkfwf6fqcs66s3lz637gaxhl4nwd2vtle8rnfqpypmhxue69uhkummnw3ezuetfde6kuer6wasku7nfvuh8xurpvdjj7qgswaehxw309ahx7um5wghxcctwvs666g7h out more.

The reason Nostr growth is stagnant is mostly cultural, not technical, IMO.

Sure there is still some deep weirdness with the UX compared to the centralized services (like being unable to delete or undo posts/likes/reposts, or that the phone clients still have weird little bugs and are still under featured in some basic ways).

Remember, there was a LOT of excitement here not long ago, and many people left after joining despite the fact that it kept getting better. Which should tell us something, no?Why was this? My guess is because there's only like three topics of discussion here:

1. Bitcoiners talking about how great Bitcoin is

2. Bitcoiners talking about how great Nostr is

3. Bitcoiners talking about politics

There's outliers who break the mold for sure (and we need more of them), but even Bitcoiners are interested in other things and going where people outside of Bitcoin are, and so even most Bitcoiners left.

In many ways Nostr is more fully featured compared to Twitter/X, and in other ways it's even less buggy, but despite the bugs people still use it because that's where so many interesting people are and talking about all sorts of things. Most people are fine dealing with the bots and whatnot and for very few is censorship a real selling point (for now).

If you want a flexible template, checkout my site's Github: https://github.com/thebrandonlucas/blu

I've managed to get it to where you can just upload things to the `md` folder as markdown, and it auto-deploys to my site's VPS via a Github action and it just works. But because it's written in svelte, you have full flexibility to code up whatever else you want if needed. I spent a lot of time building it that way so I could have the low barrier to publishing while also having the full power of a webapp if I later wanted it. Sounds at least on track for what you're looking for.

This is cool but FOSS alternatives already exist for GitHub, such as Gitea. Pretty easy to setup and already mirrors a lot of GitHub functionality and fairly widely used. Why reinvent the wheel just to integrate Nostr? And if we do want to integrate Nostr with a Got service, why not just fork Gitea and add the Nostr stuff to it?

That phrasing, without doubt, had an immense positive impact on the world's changing views on slavery. Even the fact that you feel the need to call it out as hypocrisy is downstream of the effects of that "all men are created equal" statement. Be careful about ridiculing the foundations of your own belief system just because its creators were not as "evolved" into it as you are.

If you just want to do blog/article posts, quick and dirty way is Substack or Ghost. If you want more flexibility/code it yourself, HTML + Caddy on a VPS is straightforward.

Let me know if I can help, I went down the rabbit hole on all these tradeoffs recently for my own site.

Replying to Avatar Final

When it comes to choosing software I want, there are three "No"s that make the reviewed software an immediate fail:

- No patches

- No assurance

- No trust

If your software is not regularly updated or responds inappropriately to #security disclosures, then you can assume it is not safe and can become even more unsafe in the future. This should also be heavily scrutinised by fork projects or projects with upstream dependencies or third-party libraries. If you are not able to take upstream patches or updated libraries in a timely manner, then your software should not be promoted with a commitment to security.

Assurance is continuous assessment and review by security professionals to measure confidence that security controls are working as designed. Threat modelling, penetration testing / reverse engineering, security scanning and audits are methods to do this. Assurance helps discover vulnerabilities and potential room for improvement, which is a good thing since it leads to change and commitment to developing more secure software.

Assurance matters because implementation is not always equal to the intended design. You can code something, read the code line by line and test / debug the feature and it may still have a security vulnerability, it just isnt known yet. Therefore, you should only use software you know is committed or receives regular audits. The frequency is completely up to your tolerance.

Security assurance is heavy work and often can't be done alone by developers. Proprietary or corporate-sponsored products often have the benefit of assurance because they provide financial incentive (bounties) to make people choose to commit into discovering vulnerabilities to help secure the product. In open source, especially for smaller projects, this can often only be done by good will of users, or worse, isn't done at all. The most popular example, xz, only had their backdoor discovered thanks to goodwill of an eyed Microsoft employee.

This is where the controversial (for Nostr) take comes in, but this would also mean Windows and MacOS, Chrome and others are far more assured than esoteric software. Security professionals are far more likely to be targeting popular software for security assurance, NOT your small Linux distro you spent weeks 'ricing' through baskets of additional, far more esoteric software.

This isn't all bad news though. Open software benefits from being derived from already highly assured software, such as GrapheneOS and the upstream Android Open Source Project. Sometimes, especially with cryptography, it can be better not to DIY.

No trust is a given. You shouldn't use software if you don't trust it, their upstream / third party components or it's developers. I wouldn't decide to concede because that would be hypocritcal.

There are a lot of ways I decide what makes software trustworthy beyond these three No's, but they'd probably be better in something more long form.

#privacy

nostr:nevent1qqs9mauz7vznmzrjgxsgxxy6t6x3pdsh5w9vd7wstpcwmyszkfgp3dspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsyg9e3hk5e6h2ypusm09ncv2qq6fqp8f5clueylpgdq66nxm5sxjuygpsgqqqqqqsvctalz

I would love to read that longer form if you made it, as I and the community would greatly benefit from it.

You can get a phone number or transfer your current one with jmp.chat without needing a sim. Then get the cheogram app to use it. It forwards calls and texts you receive. The UX is terrible but it works pretty very well once you get used to it, and you can pay with bitcoin

Made a package for the Bitcoin UI devs out there:

: A Zero-Dependency Web Component for Stylish Bitcoin on-chain, Lightning, and unified BIP-21 payments.

Try it out here: https://bitcoin-qr.blu.cx/

Source code: https://github.com/thebrandonlucas/bitcoin-qr

In the new mutinywallet design, how can I swap my onchain to lightning? Trying to do this in the mutinynet version of the app

"It is wrong to think that belief in freedom always leads to victory; we must always be prepared for it to lead to defeat. If we choose freedom, then we must be prepared to perish along with it. […] No, we do not choose political freedom because it promises us this or that. We choose it because it makes possible the only dignified form of human coexistence, the only form in which we can be fully responsible for ourselves. Whether we realize its possibilities depends on all kinds of things — and above all on ourselves."

-- Karl Popper, On Freedom

Wrote an article on the benefits of payjoin for Bitcoin:

https://brandonlucas.net/articles/bitcoin/payjoin

Ah, so using nostr wallet connect! But based on this PR implementing is definitely non-trivial 😅

Awesome job though, this ux improvement is a game changer

Where is the startup working on lightning micropayments for AI-based requests?

Also note that you can do this with your own self-hosted node if you’d like to as well (doesn’t necessarily have to be a Voltage node)