liminal 🦠

@nprofile…nvy4 's "Bitcoin And ... Podcast" is such high signal at such a high frequency. Give this man sats! Honored to have #ProjectAlexandria featured as a topic in the most recent episode 🫂
#nevent1q…3qj0

2024-06-28 15:43:37

- reply

Have yet to do home espresso or aeropress yet, but you bet I will at some point 🤓

2024-06-27 18:13:03

- reply

We are going to grow and fragment so wildly that you're global feed will actually be a pleasant experience.

2024-06-27 07:16:37

- reply

Yeah, even in that community there is alot of ingroup/outgroup perspectives, and then mixed is somehow in both but not accepted by both 😮‍💨

2024-06-27 04:02:29

- reply

Build clients out of code stored on events. Delete them for ephimeral clients/services. Users post replacable events of devs/clients they trust.
https://github.com/vitorpamplona/nostr-web-server/tree/main

2024-06-26 22:45:42

- reply

Got some stuff on stemstr and nostr.build 🫂 if you wanna check it out
https://nostr.build/creators/creator/?user=172&display=video

2024-06-26 22:41:59

- reply

Gurl I'm addicted to nostr and you have such a beautiful voice 🤣💜

2024-06-26 22:03:05

- reply

Missing this bit of gold
https://blob.satellite.earth/2bd7e308c1797d64fca09b1d61e9bde24c68dd45e501c7383eff1e85392df11f

2024-06-26 21:46:11

- reply

this is a good primer on what we're trying to do.
#naddr1qq…k892
#nevent1q…766h

2024-06-26 19:28:02

- reply

Honestly a great complement for an art piece 😁

2024-06-26 17:06:18

- reply

A lot of things kinda changed the immediate priority, but I hope to get the it done in the week at most.

2024-06-26 14:32:44

- reply

Love it 🔥

2024-06-26 00:27:09

- reply

We're at the cusp of a cambrian explosion.
#naddr1qq…k892

2024-06-26 00:20:39

- reply

Fun night?
https://media1.tenor.com/m/WstfoWery-YAAAAC/wink-drunk.gif
(I've come to the realization that you embody the best parts of Lucille Bluth 🤣)

2024-06-26 00:04:10

- reply

of course 🫡
Putting visual cues and reminders do help though 😁 i am getting better

2024-06-25 23:29:55

- reply

I have the cleaning efficacy of a tornado. My advanced appologies 😆

2024-06-25 22:30:34

- reply

Can't wait to see what you're cooking 🔥🍖

2024-06-25 22:25:14

- reply

Prepping for that Android release.
https://media1.tenor.com/m/z2njouIMtFEAAAAC/cocktails-drinks.gif

2024-06-25 21:14:02

- reply

Ereader/book/blog functionality*

2024-06-25 21:11:08

- reply

I think peak nostr-educational resource will happen when we combine modular articles with external/specialized functionality. ereader functionality is a must, but this goes soooo much further.
https://www.youtube.com/watch?v=5-4wd3dVtEk
https://distill.pub/2020/growing-ca/

2024-06-25 20:07:59

- reply

Honestly. Great photos!

2024-06-25 19:50:12

- reply

if you can't control it, deth immediately 👻

2024-06-25 19:46:18

- reply

Transparency in the decision process is what you're hinting at?

2024-06-25 19:41:24

- reply

I better see a #thighstr post after this 🦵👀

2024-06-25 19:37:34

- reply

@nprofile…uazd nostr.build is nostr's bedrock for hosting content. They have a lot of ideas, are incredible builders and are clearly executing with their improvements and and features.

2024-06-25 19:35:05

- reply

You've always been a creator ma'am. Was actually going to tag you and Puzzles because meme attribution has potential and you guys are killing it with original memes and art

2024-06-25 19:33:37

- reply

R, Julia

2024-06-25 19:32:37

- reply

that is absolutely crazy. You guys are absolutely killing it here with your support. In a sense, nostr's bedrock for hosting content.

2024-06-25 18:28:34

- reply

@nprofile…q5j3 @nprofile…uc5r @nprofile…cf2c

2024-06-25 17:31:41

#biblestr and #ProjectAlexandria is really going to "stir" up the nostr pot.

2024-06-25 17:11:50

- reply

🫂🫂🫂

2024-06-25 17:10:22

- reply

PineNote progress is pretty slow so I generally wouldn't recommend for users, but the software is open and the specs are public. Maybe you'd find some information on that there.
https://pine64.org/devices/pinenote/#documentation

2024-06-25 16:58:44

- reply

this seems most likely

2024-06-25 16:47:57

- reply

You cooking something? 👀🎶🔥

2024-06-25 16:47:06

- reply

Bookmarked 🤜🤛

2024-06-25 16:46:05

- reply

The format is definitely most ammenable to "sections" though, given the title tag requirement.

2024-06-25 16:41:50

- reply

It could be section, but i like the general idea. Novels may have sections, but one may want to fine grain it even more. The purpose for denoting sections ( through whatever method) is that the author explicitely is stating "this text belongs here, not over there". Makes a nice training set on "semantically closed" concepts.

2024-06-25 16:38:34

- reply

@nprofile…ykdn you wanna explain?

2024-06-25 16:31:19

- reply

Yes please, do it for you and let the world experience both your inner and outer beauty 😊

2024-06-25 16:28:14

- reply

I'm pretty sure Onyx Boox runs straight Android. The Supernote /may/ also be on Android, i know their future releases intend to dual boot linux.

2024-06-25 16:22:00

- reply

his face 🤣🤣🤣😂🤣
https://i.nostr.build/nWMDE.jpg

2024-06-25 16:04:40

- reply

Good morning Annie 😊 love your mug ☕

2024-06-25 15:58:26

Let the, fire, consume me.
https://song.link/t/62262265
#tunestr 🔥🤘🔥
"For fear my eyes are closed
I'll shut this out no more
Embrace this and become the catalyst
And now it swells in me
Smash all my defenses down
I'll take this I'll let the fire consume me
I will not fall I will not fail
I pound the walls I shake the cage
I will not fall I will not fail
Let this fire consume me
This burning passion it fills me with desire
And it drives me and drives my cause
I'm filled with reasons, but reason drive me further
Disdain for disbelief will stay this course
Oh, let the fire consume me
Let the fire burn
Let the courage run through me
Let the fire burn"

2024-06-25 15:45:29

Philip Labonte's vocal chords are nuts 💪
#tunestr 🔥🤘🔥
https://song.link/t/62262264

2024-06-25 15:24:31

- reply

An example
https://wikifreedia.xyz/nip-event-register/dd664d5e4016433a8c

2024-06-25 15:22:31

- reply

Ux needs work, but i think we can fix this with "nostr register" or just wiki entries with endorsments of clients or npubs
#nevent1q…fuqj

2024-06-25 15:14:25

- reply

Metaphorically 😂. Printing is nice but the actual pdf specs are enough to give someone an anurysm 💀

2024-06-25 15:11:18

- reply

Yeah, my gripe is specificially with pdfs. Epub can stay 😊

2024-06-25 15:00:10

Book burning? Im pro pdf burning 💩
#nevent1q…sxjf

2024-06-25 14:55:19

- reply

Burn all the pdfs and convert them into modular articles! They're so bad to work with 😖

2024-06-25 14:53:50

- reply

Yeah was curious about this. Like is it a design constraint or something we explicitely build. Guess ereader performance would decide on that.

2024-06-25 14:46:28

- reply

That should be fine, because they are distinct articles on their own. I think a single user would be less likely to publish their incrementally growing book one in a way that clutters the feed, or the design can incentivize that behavior. Def would like to avoid the "nostr plays" type of cluttering.
Viral publications could unravel something like this:
1)user posts 🔥 article
2) many users share - nothing different
3) many users edit, fork and integrate the existing article.
But because these kinds are slower moving than kind1, i don't expect it to be a huge problem considering what is already being delt with.
Even better is when specialized clients connected to themed relays/communities use this. Members of that community can decide on best practices for posting and writing.

2024-06-25 14:28:53

- reply

When you publish, the parser will have to create some top level 30040. If that's only what we want to see, we could have a tag in there to at least denote the highest level.

2024-06-25 14:14:59

- reply

i think search starts out identifying all the 30040s and searchable through their titles/authors. A high level contextual view, or how we generally look through books.
The interesting concept comes at the analysis/search level between individual zettles. Been thinking about a word embedding kind. Tags could "model" and the id of the referenced event with the coordinates in the note.
General dvms would have a field day with existing embeddings AND you can plot/organize through their embeddings forbthe users to find connections. Select individual zettles that are exactly what you are interested in.
We're given books and papers with an implicit task of finding the gold in the text. Here we have the coordinates of all raw materials. You find the zettle that you care about and read the surrounding context or insert it into the context of your ideas.

2024-06-25 14:00:29

- reply

Chat GPT generated articles 😅. Made multiple articles to see if I could compare individual notes or mess around with hyperlinking:
```
articleTitles =[ topic , topic 2...]
toc = [what is it? , who would use it? ..., conclusion]
for article in articleTitles:
for section in toc:
AI. prompt("you are a blogger with skills in {topic}. You are currently writing {section}. Please write it in markdown.")
```
SVM = Support Vector Machine - "find me a 'curve' that separates these datapoints into two classes given their labels"

2024-06-25 05:07:06

- reply

Yes! Which is why i pay for my nostr.build subscription and am patient for your vision. You know the way better than me. Sure i can incentivize things, but your vision is priority. 😁🫂🫡

2024-06-25 04:47:36

- reply

Make it nostr native and have meme attribution+zap splits. Could create an interesting incentive structure there. Wavlake has it for their artists, but memes appeal widely

2024-06-25 04:45:14

- reply

So you are a fan of air replies then 👀

2024-06-25 04:19:58

- reply

The brightest stars burn fastest. Its not always about moving fast and breaking things, especially if you want to stick around for a while.

2024-06-24 22:10:23

- reply

And me with my pen
https://media1.tenor.com/m/YuaZwKZxXgoAAAAC/write-that-down-taking-notes.gif

2024-06-24 20:43:53

- reply

If you think the spec could be accomplished in a better way, please let me know. I know the stringified json is blegh but i think it accomplishes the best given the compromise of mixing nips 23 and 51, and has a nice equivalence with nip01.

2024-06-24 20:34:31

- reply

The network grows
https://v.nostr.build/xEoak.mp4

2024-06-24 07:27:07

- reply

Less so with AI auto complete. Now my code is shittier, bloated AND i have less understanding of it 😎🙌

2024-06-24 06:25:02

- reply

Congrats man! 🫂

2024-06-24 05:52:18

- reply

i imagine they would have loved the mess 🤣

2024-06-24 05:11:06

- reply

How was the water? Did you jump? 👀

2024-06-24 04:56:34

- reply

Chaos man is happy 😁

2024-06-24 04:55:23

- reply

https://media1.tenor.com/m/pgAApB3nJnwAAAAd/smile-grinning.gif

2024-06-24 04:49:39

- reply

Wanna get your face kicked in? That's how you get your face kicked in 🦵💥 🤣

2024-06-24 04:08:36

- reply

g'nite Sarah 🥰

2024-06-24 03:00:15

- reply

I am familiar 🤣 she better be careful of any 💩 flying her way.

2024-06-24 02:58:16

- reply

I like this 😂

2024-06-23 21:00:14

- reply

Have you reconciled that there is no perfect tuning system? Standard temperament is a hack to try and make even approximately even intervals.
You can tune with ratios, but you'd be out of tune with everyone else that uses standard temperamant - though, its not like you're unfamiliar with that 🤪. Perhaps it is the best for you then 😁

2024-06-23 20:15:13

New #Amethyst emoji selector looking sleek 😎

2024-06-23 20:11:44

- reply

They're not? 😳

2024-06-23 19:55:56

- reply

🙋 halp plz #smolstr dev here

2024-06-23 19:54:27

- reply

Same here, maybe give a few minutes warning to prepare 💪

2024-06-23 19:53:38

- reply

https://media1.tenor.com/m/-0kZOBdeNksAAAAC/homie-shower.gif

2024-06-23 19:24:34

- reply

https://v.nostr.build/6G7LR.mp4
https://www.youtube.com/watch?v=EKNQOupZ4Vw

2024-06-23 19:07:12

- reply

The client should be effective enough to read. Could benifit from better design and to have nested notes, but if the events are formatted well, it should work.
Uploading, let alone doing so from a web interface is a different story 😅

2024-06-23 18:42:13

- reply

🫣

2024-06-23 18:36:19

- reply

Anyone with your nsec has access to the whole account dm and otherwise. You can always say "this account has been compromised" and switch to a new one. Key rotation, switching accounts seamlessly hasn't been solved yet.
Additionally, relays can see all your activity and ip address (geolocation) and have the potential to record it - so pay some mind about that. It's not a `known` issue, but still something to be aware of, and there are ways to mitigate it if you are concerned about that.
Non of this is too far from regular social media, it just gets brought to the light because we're all potential builders and potential adversaries.

2024-06-23 18:24:46

- reply

All in due time 🤫
https://media1.tenor.com/m/EdthteqX798AAAAC/black-metal-pagefire.gif

2024-06-23 18:07:40

- reply

Happy Birthday! 🎉🫂

2024-06-23 17:15:29

- reply

Typically no, but in trying to keep close to the specs I was working from (lists and long form content) this was a good compromise.
The tags section of a list makes up the whole list. There there is nothing in there that states what belongs or doesn't belong to the list.
I thought about some sort of "list spec" as an element of the tags section:
```
{
tags:[
...,
["eventlist", ["e", id0, relayhint0],["e", id1. relayhint1],...],
...
]
//eventlist as a list within the list of tags
}
```
Just doesn't seem fun to deal with. Stringified json is how nostr profile metadata works. Its not the most efficient but its a tradeoff because you're not iterating through every tag and checking a number of conditions to display - for every user.
Then seeing nip-01 and finding an equivalency between ideas:
kind1: text note, simple, just renders text. All the functionality needed for just a paragraph section, but being an article it could benefit from markdown as another rule. Thats how kind 30041 relates to kind 1, the base case for a section of text.
Kind 0 : Profile metadata - you click on the "title card" of a user's profile and then you're taken to a page where all their kind1s are dropped down like an accordian of index cards underneath the profile metadata. That's why 30040 is the article equivalent to kind 0 - gives bounds for rendering one layer and also provides surrounding context.

2024-06-23 14:55:53

- reply

Lets see how this works, sorry if I repeat or get too verbose:
https://zettelkasten.de/introduction/anatomy.png
https://res.cloudinary.com/lesswrong-2-0/image/upload/v1568584395/Zettelkasten_Svg_1_iuqopd.svg
Just to reference the architecture of Zettlekasten for the architecture I'm trying to emulate.
Conceptually - think linked list
Implementation - think of kind 30040s as containers that can connect together. Why containers? Because we need a way to reference the article as a whole, whereas a linked list only deals with immediate neighbors for traversal.
If we have 3 article headers, where id# represents the id of a short text note and ah# is the id for a kind 30040
ah0 : [id0, id1, id2],
ah1 : [id3, id4, ah0],
ah2 : [ah0, id6, ah1]
Each of them contain 3 notes each, but ah1 contains ah0 while ah2 contains both ah0 and ah1.
Even though ah2 contains two headers with one being nested - traversing over the ids in the header allows everything outside that level to be loaded when needed.
Going back to the rendering function
```
def render(e, kind):
if kind == 0 or kind == 30040:
metadata = JSON.decode(event.content)
if kind == 0:
print(metadata.name)
print(metadata.website)
else:
print(metadata.title)
print(metadata.author)
if card.clicked:
eventList = e.tags
return renderEvents(eventList)
elif kind == 1 or kind == 30041:
print(e.content)
else: # output raw json
def renderEvents(eventlist):
for e in eventList:
render(e, kind)
```
It is just a giant wrapped if-else statement that has rules to render the specific kind that appears in the list. The rule to render kind 30040 would be to just display the metadata from content. At minimum you can render the title, which can also be a section or chapter title. All events in the list should have a rule that says how to display it.
Referencing the spec:
```
{
"id": ...,
"pubkey":...,
"created_at": <unix timestamp in seconds>,
"kind": 30040,
"tags": [ // influenced from nip-51 lists
['e', <event0-id>, <relay-url>],
['e', <event1-id>, <relay-url>],
['e', <event2-id>, <relay-url>],
...
],
...
],
"content": `{'title':<article-title>, 'author':<string>, ...}`, // influenced from nip-01: kind 0 metadata, stringified JSON object
}
```
Some extra reading:
https://zettelkasten.de/introduction/
https://www.lesswrong.com/posts/NfdHG6oHBJ8Qxc26s/the-zettelkasten-method-1

2024-06-23 12:55:50

- reply

The article header in theory should help you not worry about how nested it is. You are only traversing one list at a time and using the rules to render each individual element.
```
def renderHeader(nevent)
for e in nevent.tags:
render(e, kind=e.kind)
```
An article header would just render the .content feld, which is just stringified json metadata not unlike kind0. So it will just be a title card among the other notes that are rendered - keeping the rest of the article unrendered beyond that level.

2024-06-23 12:13:12

- reply

Architecturally its tree based, but you start from the leaf nodes and build small branches. Hierichical articles build larger branches from smaller ones and you connect them by adding the id of the individual note or the article headers. Article headers themself can stand in as a more `strong` section like a chapter.

2024-06-23 12:07:36

- reply

The idea is that article headers collect notes which can be turned into their own focused thing.
If you have the individual notes you just assemble their id's as a list for 30040. Doing it all in one go is a bit more involved which i have a rudementary script for. You have to parse out the individual sections, create notes from the sections and then create the list from those ids. Basically the reverse of how we read.
Yes, you are correct. 30041 is in form the same as 30023 but the difference is in what they represent and how they are organized. 30023 is itself a full piece of content while 30041 is meant to be a fragment or section - that is to say, there is broader context that the note lives inside.
In a feed sense, it makes sense to show a whole blog post but if someone wants to publish a textbook all at once with multiple levels of subsection everyone else's feed is going to have a very bad time.
Just as 30023 renders a title card, 30040 functions as that, along with holding any other metadata with respect to the whole article. Only the title card is supposed to be in the default feed which loads/renders the notes once selected.

2024-06-23 09:01:52

- reply

This would be incredible.

2024-06-23 06:32:03

- reply

G'night 🫂

2024-06-23 05:13:50

- reply

oh, i understand. Crunchwrap w/ chipotle mayo & 🌶️😍
https://media1.tenor.com/m/PbkYp_j3raUAAAAC/taco-crying.gif

2024-06-23 04:57:06

- reply

Congrats and my future condolences 💩

2024-06-22 22:50:16

Rise Against vibes today 🔥#tunestr
https://song.link/nl/i/1440858616
#nevent1q…vu5f

2024-06-22 22:48:12

- reply

That looks incredible thanks for the rec!

2024-06-22 21:13:31

- reply

Now that's quite a mug you jave there 👀

2024-06-22 21:09:21

- reply

Found a badass 😮😎

2024-06-22 21:08:12

- reply

✊

2024-06-22 21:05:44

- reply

How lovely

2024-06-22 21:01:01

- reply

21 is a cool number. I am partial to another one however 😛
https://www.horrormovietalk.com/wp-content/uploads/2021/11/The-Number-23-movie-poster.jpg.webp