Couldn't be me. I only insult people to make myself feel worse
That's true. Hoping you'll end up doing something based on stl1988's more NIP-54 related suggestion too ๐ค
nostr:note124g66ncze9rgqyhln0h8kn9ja7xvxd3ff5kegt2p22cekjq644uqkyy5nl
Ugh! I can't get it to work and I have no idea how to diagnose. Can nostr:nprofile1qqs827g8dkd07zjvlhh60csytujgd3l9mz7x807xk3fewge7rwlukxgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qgswaehxw309ahx7um5wghx6mmd9usjfpck can help?
I do notice this error in the logs but I was able to load the url in the browser fine, so not sure what's up there.
Using Graphene OS and ntfy.

Since nobody else has replied, I'll ask: have you tried Firefox Mobile or another Android web browser compatible with nos2x or nos2x-fox extensions?
I believe it's just the public data of your kind-0 entry, not your nsec or anything like that
Outbox model just saves bandwidth & maybe thus improves reliability on low quality internet connections
If your client does not use Outbox model yet, please go to https://metadata.nostr.com/, click relays and set it up.
Without that setting, Outbox clients cannot find your posts. Your follows won't find you.
Tips:
- You only need a maximum of 4 relays in that list.
- Mark as "Write" the relays that have all content written and signed by you.
- Mark as "Read" the public relays that you want your follows to use when sending notifications to you.
That's all you need to do.
Thanks for this post, I had been wanting to update my relays but forgetting the exact steps to do it.
Do you know how we can properly use the cryptocurrency_address field on metadata.nostr.com ?
This is perfect. There could be another event kind for wikitext too if nobody gets around to finding another conversion method first. Everyone would be happy. nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 please consider
Incorrect.
You're confusing most people (not everyone) by insisting that the pandemic is over.
It's compatible with Wikipedia and most other wikis on the web.
Markdown is cool, but a NIP that just uses nostr to back up and synchronize articles across MediaWiki instances seems like it would be better than an asciidoc wiki platform that isn't cross-compatible
Thanks for replying.
In the context of Nostr, you need to solve Apple and Android's entire supply chain to make apps for their platforms with end-to-end encryption. Same as other contexts. Nostr just relies on regular encryption right now, not end-to-end encryption
My initial observation was that you seemed brainwashed. Now that you're trying to brag to me about how brainwashed you are, as if it wasn't already my initial observation, I have another observation: you're not very bright.
I should also say, your observation itself is noteworthy enough.
At least 3 resources.
It's not your observation, it's your reasoning that a social media user base's strength would be measured by meetup turnout during a pandemic.
Iโm looking forward to building really strong end to end encryption. ๐
https://www.therage.co/uk-nca-national-risk-assessment-2024/
Last time you showed up in the feed I pointed out how your wording was dishonest.
nostr:note18vcqeleffvw4h9xzt6akcml8jacfkra8zgn3uxae984dgfh4857qd38ls3
You did not address this.
Here you are in the trending feed using the same terminology again, but with extra noodles this time.
I was blocked by pfrazee and Bluesky ended up making shit up to ban me over because they couldn't handle me being on their platform calling out the platform's own bullshit
Oddly, X now allows me to go around telling people they should use nostr
This post makes you sound as brainwashed on the pandemic as Bluesky users are on censorship.
Nostr and Bluesky are both movements and neither are going anywhere. We need to be mentally ready to stay outnumbered by a bullshit version of "decentralization" for a long time.
Wikitext offers compatibility in exchange for the drawback, I keep saying
It straight-up uses English instead of arbitrary character coding for certain functionality