my bet's on the latter 😂
You are being hunted, might need some witness protection for you 😭
you three* cant forget about the bear 🤗
Its cuz you both have stolen it! Give it back so London can appreciate it 😋
Sounds terrifying 😬
Really cool stuff! 🎶🎶
https://album.link/ch/i/1001639767
#tunestr #groovestr #postmetal 🤘😤🤘
Dog:
- yay has bone 🐶🦴
- yay hooman sits next to me 🧍🐕
- yay hooman gives pets 🧍🫳🐕
Repeat 🔁 for ♾️
- 😡 stay away from me dont touch my bone 🦴
- nooo 🥺 come closer want pets 🫳🐕
🤷🤷🤷
Likely going to rerecord to have a cleaner version up. I've been practicing 💪🎸🚀
Maybe make a calendly like Tatum 😂
Please don’t screw it up.
Please don’t screw it up.
Please don’t… ah, who am I kidding?
https://variety.com/2024/tv/news/apple-neurmancer-series-william-gibson-1235925640/
Have you read Ramez Naam's Nexus book? Some overlapping themes
nostr:npub1jv3tmy30yrr0ek0fzdz5wfanh0pdp947fqgewyz44qndmg75ev9sz7lakg you were my 420th follow 😎
If what you are trying to do is keep a catalogue of related/themed notes: kind 1 is not the way. i argue for having "modular articles", but the concept could apply to themed groups of notes.
Nested notes kill the experience (and occassionally, the app), same thing with publishing a lot of notes in a short time to the user's feed, that are all related.
Solving it? We need two event kinds:
Kind 30040 - article header: this is what renders to the main feed of users on the typical clients. It displays the name of the article (or group name) and whatever other metadata about the text you care about. As a tag it contains a list of existing notes that make up the article of group, and these events could be any type of event that can be rendered.
For articles,
kind 30041 - article note: The content of the article as multiple notes representing sections of the article. These notes typically would only be rendered when the article header ia selected (kind of how notes that kind30023 (habla.news) renders a note when its clicked on.
make sense?
