Busy weekend. Trich servers aren't live. Bad news my one helper is unreliable. 😔 Good news is I've met a nice lady yesterday, a owner of a dispensary. Very nice store, excellent staff and the best overall shop in Jersey. She expressed the need for something like #Nostr in the community. It's a Instagram dominated market and censorship cracks down pretty hard. I learned that discord is nuking servers related to legal cannabis communities.
Another positive note would be the direction of the menu bot. The data needs freedom. I've built out the bot to power my client but the data still lives with me. When discussing deployments it seems like the costs are unnecessarily high to have it run daily. So we will just run it locally and publish the database to relays. There are apps that run their entire business keeping this data to themselves. I guess I'll submit a new nip and try to standardize the data.
Trich will continue down the "centralized" root to start. #weedstr posts are pulled and comments and discussion goes to their nip65 relays. I have no real intention of trying to get nostr users on my app and the people looking for Trich don't know nostr nor do they even really care about decentralization. This allows a early beta to make sure all my infrastructure is working properly. I haven't made a decision about reading nip 65 relays for the feeds. On one hand its a cannabis community app and should be more focused on the community built around my relays, on the other hand I shouldn't limit the power of Nostr. Could be a simple tick box in settings but there's still sometime.
Long note short. Everytime I try to meet people in the industry for feedback, Nostr shines more and more.
Nutty
npub1ue…ahmu8
2026-08-25 14:10:06 UTC
Author Public Key
npub1uemw74rj4qf743z7vnrtxkr6tqpeut94hv2f6uckjr767uskj2sq8ahmu8Published at
2026-08-25 14:10:06 UTCEvent JSON
{
"id": "1fe6e54b843473377abf91cfb275743610f651c303e3816c33b4fc34e5321f92",
"pubkey": "e676ef5472a813eac45e64c6b3587a58039e2cb5bb149d731690fdaf721692a0",
"created_at": 1787667006,
"kind": 1,
"tags": [
[
"t",
"Nostr"
],
[
"t",
"weedstr"
],
[
"client",
"Primal Android"
]
],
"content": "Busy weekend. Trich servers aren't live. Bad news my one helper is unreliable. 😔 Good news is I've met a nice lady yesterday, a owner of a dispensary. Very nice store, excellent staff and the best overall shop in Jersey. She expressed the need for something like #Nostr in the community. It's a Instagram dominated market and censorship cracks down pretty hard. I learned that discord is nuking servers related to legal cannabis communities. \n\nAnother positive note would be the direction of the menu bot. The data needs freedom. I've built out the bot to power my client but the data still lives with me. When discussing deployments it seems like the costs are unnecessarily high to have it run daily. So we will just run it locally and publish the database to relays. There are apps that run their entire business keeping this data to themselves. I guess I'll submit a new nip and try to standardize the data. \n\nTrich will continue down the \"centralized\" root to start. #weedstr posts are pulled and comments and discussion goes to their nip65 relays. I have no real intention of trying to get nostr users on my app and the people looking for Trich don't know nostr nor do they even really care about decentralization. This allows a early beta to make sure all my infrastructure is working properly. I haven't made a decision about reading nip 65 relays for the feeds. On one hand its a cannabis community app and should be more focused on the community built around my relays, on the other hand I shouldn't limit the power of Nostr. Could be a simple tick box in settings but there's still sometime. \n\nLong note short. Everytime I try to meet people in the industry for feedback, Nostr shines more and more. \n\n \n\n",
"sig": "d90fa59399070e550d8a4cdacdce2417162090b1d9dd1c80fef2069ff720023a9db1a4d652ffa60dc33cedb07801cbadde3529f1b9b334f64c5836d9c62664bf"
}