Avatar
Alex Gleason
79c2cae114ea28a981e7559b4fe7854a473521a8d22a66bbab9fa248eb820ff6
I create Fediverse software that empowers people online. I'm vegan btw. Note: If you have a question for me, please tag me publicly. This gives the opportunity for others to chime in, and bystanders to learn.

Check this out. It's so close to being able to import a Nostr URI directly.

Using a colon doesn't work in the alias, only a slash.

Anyway this is making me think instead of trying to build Nostr on top of git, git could be replaced with a Nostr thing.

It occurred to me that you can host JS/TS code on Nostr, and import it directly in Deno from an http gateway. It fucking works.

Do you have a note ID I can try it with?

nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z Hey do you have a link to that Nostr-hosted static HTML site? It was importing .js and .css files from Nostr relays through an http proxy.

The bridge has to work with everything, so it chooses the lowest common denominator, which is Mastodon. Our software could be patched to improve the situation, and I have already done so by truncating the names in Soapbox. Patching it on the API side would require a lot of work I'm not sure is worth it opposed to just building Ditto.

nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6

Nostr isn't going to take off if only for the naming...I mean who the hell is "97cxyzab445..."?!? It tells you nothing...

nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn

This is a deficiency of Mastodon, not Nostr. It is necessary for supporting the legacy Mastodon network. When viewed through Nostr most people have usernames.

CSP is a header in the HTTP response called "content-security-policy"

You can see it by running: curl -I https://blimey.social

Run: curl -I https://gleasonator.com

Compare the content-security-policy header.

You will see the "style" section is different. Mine allows unsafe-inline, yours allows only a single nonce

You need to make it return the correct thing. You can also check the console logs in the browser to see the errors resulting from this.

Paste your Nginx file into ChatGPT and ask how to do it.

I don't want to write up specific instructions on this because I don't want to encourage other people to do it. It's not a good thing. Akkoma has broken support for other frontends. This is an Akkoma problem.

Ah the great master race.

Hey guys, I was featured on the latest Thank God for Nostr podcast where we discussed veganism, my beginnings at Truth Social, ActivityPub, and the move to Nostr.

Give it a listen here: https://fountain.fm/episode/7IvgMxBTfPXPw6CI60Oc

Thank you nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn for the great interview!

Bluesky is down. Something which should not be possible for a decentralized social network.

Mastodon has been trying to do privacy features like this forever. It's the reason they don't have quote posting yet. They want to limit who can reply to a post. Something that goes against the grain of decentralized social networks.

The second best way is the kind 10002. But I wish the relay URL was on the kind 0. The kind 10002 seems like it requires activism to make people adopt. I needs to be a more ingrained part of the protocol.

IMHO the fact that nostr identities use self-created and self-managed keypairs is not a flaw, nostr does not need a way to bind keys to names, nor does it need identity provider services.

If you want to bind a key to a name, use a petname. That idea was there from the start (afaik). What is a name anyways other than a way for you to remember who that key represents?

The whole business of binding keys to other sorts of identifiers was always murky to me. Why are these other sorts of identifiers important? Who are they important to? Are the centralized? Do they promote centralization? Why should I trust some 3rd party with this binding?

Back at Sun Microsystems IT, I made a proposal I was (and still am) very proud of, but it wasn't accepted and probably wasn't really well understood either. The proposal was to send new recruits a javacard with a Sun PKI keypair pre-generated on the card, along with a serial port smartcard reader (this was pre USB). They would fill out their job applications under a session authenticated by (or else digitally signed by) the keys on that card. Everything the company knew about the person happened through those keys. In this way, the problem of authenticating people before giving them a keypair disappeared. The problem of binding some knowledge about them to a keypair was solved, because all that knowledge was acquired in the first place through that keypair.

I have no idea who fiatjaf really is. I don't know his real name. No third party bound some identifying information about him to his keypair and shared it with me in certificate form. And yet I have a good idea who he is and how much I trust him and in which regards. "By their fruits shall you know them" - Matthew 7:16

Nostr has other issues. How to roll over a keypair. How to export/import private keys without risking their exposure. IMHO these are much better issues to have than ... oh shit Thawte/StartCom/Comodo/DigiNotar/TurkTrust/NICCA/CNNIC/WoSign/LetsEncrypt/Symantec/StartCom/GoDaddy/Certinomis fucked up and aren't trustworthy.

You can reverse lookup a pubkey by finding a kind 0, getting the NIP-05 and then doing a NIP-05 lookup to get the relay. Don't shoot me.

nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn