monlovesmango

building on nostr

Public Key

npub13sx6fp3pxq5rl70x0kyfmunyzaa9pzt5utltjm0p8xqyafndv95q3saapa

NIP-05 Address

monlovesmango@astral.ninja

NIP-57 Address

monlovesmango@getalby.com

Profile Code

nprofile1qqsgcrdyscsnq2pll8n8mzya7fjpw7js396w9l4edhsnnqzw5ekkz6qprdmhxue69uhkummnw3ez6ur4vgh8xetdd9ek7mpwv3jhv8jwdy8

Publishing to

nostr-pub.semisol.dev

Author Public Key

npub13sx6fp3pxq5rl70x0kyfmunyzaa9pzt5utltjm0p8xqyafndv95q3saapa

Show more details

Last Notes

2023-02-19 08:02:24

- reply

def agree send delay feature is needed

2023-02-15 17:11:07

- reply

thank you rob! glad you find it useful.
I am currently in the process of completely revamping the relay strategy to be more targeted (kinda frozen with indecision atm), and hopefully make UI less busy as well. in theory the targeted relay strategy should be faster and less data intensive, the hard part will be supporting the legacy relay strategy as well to continue to provide a smooth experience.

2023-02-15 16:44:36

- reply

lists are meant to be flexible enough to hold anything, though rn only have lists for users, hashtags, and events defined, I also think lists of relays or lists of other's lists should be added.
lists are essentially tag lists and can be public and/or private. user tag lists can also hold the relay hint field so you can specify which relay to use for which user in a list.
my idea was users can create their own feeds by pulling in the lists they have saved. so you could create a feed by pulling in a list of hashtags queried against a list of relays. or a list of hashtags from a list of users (using the relay listed for each user).
what do you think #[1] ?

2023-02-07 02:20:53

- reply

correct, this is what kind 2 does. but this pr may make kind 2 irrelevant
#[5]

2023-02-07 02:19:22

- reply

check out @mikedilger.com 's pr for the direction that relay management is heading:
https://github.com/nostr-protocol/nips/pull/218#issuecomment-1420052432
tldr is you won't need to add relays to stay connected to people

2023-02-04 22:38:34

discussion of new long form posts pr by #[0]
https://github.com/nostr-protocol/nips/pull/220
#[1]

2023-01-30 16:50:26

- reply

hmm non-follows should only pull in as the reply or root event of a follow's reply. very weird this is pulling into your follows feed...

2023-01-28 18:24:26

- reply

hahah yes

2023-01-28 17:57:04

- reply

thanks for sharing! agree completely

2023-01-28 17:49:13

- reply

this would explain it. glad #[1] was able to point you towards a reasonable explanation! how fucking stressful.
agree, I also think your key is safe.

2023-01-28 17:45:14

- reply

the whole paper read like a troll post tbh. and while I never had a positive view of stacks i really don't trust them now.

2023-01-27 23:40:25

- reply

was nip69 a real thing? why can't i find it.

2023-01-27 23:07:39

- reply

settings > dev tools, choose sql query and use this search:
SELECT n.event FROM nostr_events e
left join nostr n on e.id = n.id
where kind = 0
and pubkey = '3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24';

2023-01-27 22:08:21

- reply

gahh persistent db would be so useful for this...
someone must have a copy somewhere.?
if this happens to you again you should use astral sql query to grab the kind 0 event

2023-01-27 21:58:19

- reply

have you found the event with the wrong lud06?

2023-01-27 21:55:12

- reply

do you ever use the sign for 5 min option on nos2x?

2023-01-27 19:52:47

- reply

yes, hard to know what the future relay landscape will look like. I do agree that languages specific relays will be a thing. I also agree that people would likely want translation relays and such.
all i'm saying is language query filter is first step and good short term solution to jump start language specific feeds.

2023-01-27 19:48:54

- reply

i agree with you here. I just don't think the majority of fired twitter employees are in this camp. if they were the majority twitter wouldn't be where it is today.
I also think anyone that has shown this propensity should be recruited. not just fired twitter employees.

2023-01-27 19:41:10

- reply

i'm talking about the same query filters that search for hashtag or event thread. relays would still hold all languages (unless they want to be a specialized relay). standard query filters from clients would query the posts the user wants.

2023-01-27 19:35:21

- reply

yes but its less checks bc client receives less notes

2023-01-27 19:27:42

- reply

welcome lyn!! been awaiting your arrival!

2023-01-27 19:18:20

- reply

well in my mind, relays with the same/similar policies will be managed together in the same (named) grouping.
no way users can manage each relay policy individually, seems way too granular.

2023-01-27 19:08:42

- reply

long term this is kinda how I envision the language param tag being used. based on the new relay list nip you could add criteria that automatically only posts to certain relays by the language that is used.
https://github.com/nostr-protocol/nips/pull/32

2023-01-27 19:06:14

- reply

I guess i think its higher signal if you can filter which language you see from your follows (especially if you normally skip those weird languages)

2023-01-27 19:04:03

- reply

having a languages query parameter would mean clients can query for only one language of notes and don't need any processing power for sorting notes by language....
yes at least it seems like we all agree on that point which is promising!

2023-01-27 19:00:10

- reply

you've never used the google search feature that allows filtering by language?

2023-01-27 18:58:00

- reply

as someone who has had to choose between paycheck and mission I might be super cynical at this point. my views are what they are.
just to be clear, i don't think ex twitter employees are bad people or 'compromised'. but they def put stability over values. as did I at one point.

2023-01-27 18:48:04

- reply

I guess I assumed twitter has a lot of fancy algorithms for their curated content

2023-01-27 18:42:00

- reply

sure this is definitely a thing, I agree. but not what i'm talking about.
rn on nostr most conversation is in english. who do you think would prioritize language query filters more, those speaking english or those speaking something else?

2023-01-27 18:35:59

- reply

i mean we all agree twitter is broken right? not functionally, but incentives are broken. and I can't say i trust the people that built those broken incentives.
obviously I am generalizing and there are exceptions. but would trust someone who quit more than someone elon fired.

2023-01-27 18:27:51

- reply

oof i don't know how I feel about a new kind to group notes.
I was saying if you write a spanish note, you only broadcast to your spanish relays. english note, only broadcast to english relays. dont need to translate across notes, but def could be a nice feature

2023-01-27 18:21:41

- reply

hmm not sure if I like having users compose multiple notes for translation, but definitely could work
i was imagining translation to be done by client when displaying note. seems simplest.

2023-01-27 18:19:01

- reply

and the translation would be in a separate field on the event then?
i'm not against a translation model like this. I just think a language query param should be first step (and seems to be needed in your suggested method as well).

2023-01-27 17:42:50

- reply

what exactly do you mean by translation relays? how would that infrastructure work? how would clients query that relay without a language query parameter?

2023-01-27 17:37:33

- reply

of course they will continue code. I just don't think their values align with nostr.

2023-01-27 17:35:53

- reply

first, relays wouldn't do translation clients would
second, yes and the language query parameter would help with that
third, I agree americans complain about spanish which is why they would prefer to just have it translated for them. but don't totally understand your point here

2023-01-27 17:28:09

- reply

de acuerdo. mi espanol esta terrible 😂😭

2023-01-27 17:08:48

- reply

sure if you pay them cushy twitter salary

2023-01-27 17:06:17

- reply

nah. just bc elon fired them doesn't make them valuable.

2023-01-26 08:46:15

- reply

yes for sure removing markdown but also don't want to break links. please bear with me...
cannot wait to remove all those markdown deps

2023-01-24 01:09:51

- reply

imo security (in this case minimal bad actors) still is more important than speed.
agree pay for relay will work. but still want a free/non lightning option.

2023-01-22 18:46:44

- reply

you using safari or chrome? I don't have iphone so astral is completely untested there

2023-01-22 18:45:55

- reply

bit*

2023-01-21 23:31:51

- reply

ok this should be fixed now. you will need to refresh astral.

2023-01-21 23:29:29

- reply

sorry that the search wasn't working... its very confusing/frustrating for end user. it may have been UI being laggy... trying to make astral less UI intensive as I update

2023-01-21 22:23:45

- reply

existing nip05 should resolve. at least I'm seeing all of them. I did fix nip05 query for general nip05 lookup, just missed it in setttings. do you have example of one that isn't resolving?

2023-01-21 22:22:20

- reply

and upgrade happened exactly 2 days ago

2023-01-21 22:21:13

- reply

you know what this is prob from upgrading to latest nostr-tools version (it has slightly different api for querying nip05). will fix. thank you for letting me know 🙏

2023-01-21 21:48:03

- reply

damn. its actually been working pretty smooth for me lately. only thing I can suggest is clearing cache for astral.

2023-01-21 21:18:31

- reply

weird. are you on desktop or mobile?

2023-01-20 16:34:02

- reply

nice! any relay that supports nip33 would support the lists nip. from the nip33 discussion it sounds like #[1] 's nostream relay implementation supports it, but don't know more than that.
https://github.com/nostr-protocol/nips/pull/54
also I need to update the lists nip to use nip04 encryption instead (and just use ourselves as the peer). this was suggested here by #[2]
#[4]

2023-01-20 16:30:21

- reply

fixed

2023-01-20 01:01:19

- reply

yeah! nice job

2023-01-20 00:31:37

- reply

nah you good. astral cuts it off at 10 pubkeys or something. yeah little user card that pops up on hover would be sweet. someone opened a pr for this and will get to it at some point.

2023-01-19 20:51:52

- reply

damn fixing

2023-01-19 19:02:39

- reply

damn just tried to tip you and doesn't work. I don't know if lnurl-pay can fetch invoices from onion addresses

2023-01-19 18:49:39

- reply

hmm if it has a port in it I don't think its an ln addr. if you are using a url astral will not convert that to lnurl, so you would have to paste in the lnurl string.

2023-01-19 17:01:48

- reply

huh..? anyone's ln addr is publicly available if they enter it on their nostr profile...

2023-01-19 16:50:06

- reply

lemme know if it still isn't working for you. send me your ln addr and I can try to figure out whats going wrong.

2023-01-17 18:12:17

- reply

ooohh mango shaved ice... all time greatest desert??... 🤤🤤🤤

2023-01-17 18:10:32

- reply

mmmm mango sticky rice...🤤🤤🤤

2023-01-17 17:37:20

- reply

even if everyone in the network is following the same 10 relays, how is taking down one an easy attack vector?
i don't think everyone should have same/similar relays. i just think community conversations should be grouped on common relays, not randomized over a slew of relays

2023-01-17 17:17:27

- reply

I don't think we want randomness or uniqueness in relay choice. this makes it inconvenient to find the posts you want. we just want redundancy for messages that shouldn't be censored.

2023-01-17 17:14:49

- reply

this is where humans come in :)
if you see a post that you think is important, and its only on a select list of your relays, you repost it or publish it out to your other relays. spread the reach and redundancy of the message.

2023-01-17 17:07:12

- reply

yes but will be much harder to piece together a coherent convo. we are already seeing this.
not every post will need redundancy. most posts are not important. the key feature of nostr is that when redundancy is needed, it is easy to amplify a message for greater redundancy.

2023-01-17 16:52:22

- reply

I actually don't think relays should be chosen randomly. i think relays need to be community based. each community stands up a few relays and you use the relays for the communities you want to follow.
if you do it randomly the data replication needed will be immense.

2023-01-16 19:38:46

- reply

avi running his mouth ab mangos 😂 indian mangos are good and all but why limit yourself

2023-01-16 17:08:29

- reply

yeah! entonces debo hablar mas espanol

2023-01-16 16:34:41

- reply

hablo un poco espanol. a veces necesito google translate 😅. pero me gusta practicar otros idiomas.

2023-01-16 04:21:02

- reply

yes correct. and even still most of the lag is from the db (even though its not persistent). I don't think caching prof pics will help much. but I think I can improve the handling of the db so that it is more responsive.

2023-01-16 04:10:41

- reply

😂 lightning tips es mejor de likes gratis

2023-01-15 20:48:14

- reply

well likes is mroe of a design decision... but we'll see how long I can hold out. personally would prefer to just go to paid likes but don't know timeline on that.
but yes, I like some of the design decisions and am interested to see how they handle relay data. oss ftw!

2023-01-15 20:44:43

- reply

ah yeah the relay query stuff has def been isolated to its own webworker... but still wouldn't call it clean haha. improving incrementally. appreciate your thoughts!

2023-01-15 20:37:07

- reply

i think hamstr.to must have replaced the relay query and browser db code too bc it feels a lot more lightweight and faster than astral. they also have likes/reactions so def more than just a new skin. been meaning to check out the code.

2023-01-15 20:02:26

- reply

I mean tbh i agree with you. still working on improving the speed (I think next update should make a big difference). any general feedback about improving the codebase being a mess? i'm sorta new to this so always trying to learn how to do better.

2023-01-14 21:12:49

- reply

also I don't think its appropriate for nip04 encryption scheme here..? isn't this only for when shared secret is needed?

2023-01-14 21:10:13

- reply

would you consider using the nip I linked above? have you had a chance to review it? its written to be extensible for events, hashtags, users. and to allow users to create lists other than just mute that they can name themselves.

2023-01-14 20:54:00

- reply

not yet. for mute I was hoping to use the encrypted lists nip (kind 30000) that I had proposed: https://github.com/nostr-protocol/nips/pull/114
also wanted to get an unencrypted version out there.
#[0] do you guys have any documentation on these new kinds?

2023-01-13 16:32:20

- reply

wow great work guys!! such a nice feature

2023-01-09 19:00:45

- reply

exactly. not touching any legacy walled garden system. whether that be fiat or app stores.

2023-01-09 16:13:54

- reply

had my fingers crossed you would make a pr for this!! thank you lee! posting some feedback now

2023-01-08 03:38:49

- reply

that model makes a great incentive for relays to game likes though. events you post to a relay can be independently verified. aggregated lists cannot be.

2023-01-08 03:18:54

- reply

and who is going to be source of truth of that single event? how do you validate the last person handling it updated it accurately?

2023-01-07 22:57:50

- reply

yes last night. why? are you having issues? was supposed to fix getalby

2023-01-07 22:51:28

- reply

I haven't changed anything... hahah
its prob bc the next time you loaded it it was already in astral browser db..? db is much faster to query than relays.

2023-01-07 18:58:39

- reply

👍 sounds good

2023-01-07 18:23:48

- reply

what was their rationale?

2023-01-07 18:03:15

- reply

I would love to but honestly just figuring out this front end dev stuff and haven't had time to learn anything else.
also can't afford a start9 rn but think its a really cool project and hope to get astral on the marketplace at some point.

2023-01-06 23:55:10

- reply

yeah can't tell. matte finish is nice.

2023-01-06 03:29:45

- reply

yeah i'll probably put in notification personalization, but by follows, pow, etc. but might be complicated to track down how far removed your post is from the reply, but identifying direct reply might be straightforward.

2023-01-06 03:17:55

- reply

it probably to make sure others in the thread can get notifications if they want them..? bc otherwise its hard to get notified of a new reply

2023-01-06 03:12:52

- reply

wasn't aware it says all p tags. even original branle only included first 4 or so.
i guess astral isn't to spec cus now it allows you to edit the p tags yourself.

2023-01-06 00:18:43

- reply

i don't think its a you problem. somehow his ln address is in lud06 field.

2023-01-05 19:49:10

- reply

yes or to spread it to other relays that may not have seen it

2023-01-05 19:05:45

- reply

interesting. do you mean on user profile or on the ln address that shows up on the tip card? or both? the points jb makes are valid, I want fewer workflows where user runs into payment flows their wallet doesn't support.

2023-01-05 18:42:42

- reply

you shouldn't need to clear cache. you may need to close the window and then reopen (so browser fetches new version). and maybe reload a couple times..

2023-01-05 04:34:09

- reply

decentralized github. weve already seen github be eager to censor.

2023-01-05 04:17:41

- reply

i really want to see git implemented over nostr

2023-01-04 16:12:01

- reply

in my view the two main modes of human communication to establish value are:
- words
- money
free likes have no words and cost nothing yet take up more bandwidth, processing, and storage due to volume unless you go centralized route.
paid likes will come to astral, but after media

2023-01-03 18:15:54

- reply

ok you convinced me. I will allow multiple invoices. thanks giszmo!