my future house will look something like this

fuck windows

ok maybe i will have them on the southern face, and angle the building to have two sides with a big window panel

but something like this, and the big 3' deep soil at the top with gravel under it and drains to grow a heap of low growing, shallow root plants

content curation, as in labeling it "one of ours"? so the post has to be authorised to be labeled such?

communities then - this is exactly how they work

people submit posts, and actually anyone can read them, but they are not counted as part of the community until they get a moderator's approval

it looks like this was a request sent by snort.social:

["REQ","65eab48c-63d5-49f3-8018-93ccc0f16934",{"authors":["8ccfa77bf43e3afd4076aa91d5c0e7c2dae9d279aeee72666aec02aac317447a"],"kinds":[10003,3,10015,10000,10002,10005,10001]},{"authors":["8ccfa77bf43e3afd4076aa91d5c0e7c2dae9d279aeee72666aec02aac317447a"],"kinds":[30078],"#d":["snort"]}]

event 30078 is application specific data

#snort developers, you should be authing NIP-42 to access this kind of event... i have categorised events that should not be given out to everyone, there is 4:

kind.EncryptedDirectMessage,

kind.GiftWrap,

kind.GiftWrapWithKind4,

kind.ApplicationSpecificData,

4, 1059, 1060 (h/t hodlbod) and 30078 are somewhat sensitive kinds of data and really should not be returned from a relay without the querant proving they are 8ccfa77bf43e3afd4076aa91d5c0e7c2dae9d279aeee72666aec02aac317447a in this case

good that there is starting to be a convention to label the client in the request tags now, or at least, i suppose that the Application Specific Data is for Snort that is not the right way to go about it...

ah, i'm too poopered to be bug hunting at this point in the evening

i have a pretty good idea how i'm gonna squash this bug... it's an issue that doesn't exist with nostr.wine and eden.nostr.land relays but comes up with primal.net relay and from what i've been reading from some chatter from nostr:nprofile1qyd8wumn8ghj7urewfsk66ty9enxjct5dfskvtnrdakj7qgmwaehxw309aex2mrp0yh8wetnw3jhymnzw33jucm0d5hszxthwden5te0wfjkccte9ekkcettw5hx7mnvd9hx2tcqyqalp33lewf5vdq847t6te0wvnags0gs0mu72kz8938tn24wlfze66qnzkp - that it comes up with go-nostr's relay client code on primal.net for "replaceable" events, which is the range from kind 10000-19999 as well as follow list and profile metadata (0 and 3)

the way i found it has been due to implementing NIP-42 in my client, and when it tries to send this type of event something different happens and my client bombs out and disconnects because the authentication reply doesn't happen

this isn't a problem with whatever relays it is that nostr.land and nostr.wine are using but it affects my relay, which is based on go-nostr and khatru codebases, and it affects primal.net which i assume may well be a khatru fork too...

i just realised there is a common sound to some forms of the word for Jesus as the name Zeus

in slavic languages they say ee-soos and someone's username reminded me of the JEEEEZUS exclamation from some old teen adventure movie from the 80s (the one with tom cruise in it). and in portuguese they say it with a harder J and the U is more like an OO than UH

there's some peculiar things about portuguese, i never got interested in learning it until i literally live in the country, and now i hear these sounds and i'm like, "this sounds so much like serbian" so often, but i'm learning the actual words involved and they are different words but the sound is still very similar to my serbian-trained ears

i think communities would allow this, to constrain the user count, if i understand what Gzuuus is hinting at

i've just bumped up against a bug involving a client not receiving an ok message from the relay (my khatru based relay) and it stalls the NIP-42 protocol and causes the client to time out and die

the common factor every time is that i get a log printing "replaceable event" which i put in there, and clearly the replaceable event code is not sending the ok

guess who wrote the original version i forked from... no, i'll wait

nostr:nprofile1qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgcwaehxw309aex2mrp0yhxxatjwfjkuapwveukjtcqyrafsj7hmweg9ur7zmn6apajdg48hxuskujx53rhrux0ttjcqx84yx35fg2 this is actually a bug in go-nostr

which #nostr clients support #NIP-42 properly?

it's quite comical watching primal connecting to my relay but failing to auth to it for a given subscription, which is kinda annoying because it means it's probably not posting to my relay either

#asknostr

i may have found my substitute for zerohedge

nostr:note1qc3x73dgehps4ytm8644m4r5j5d5ztlp3qjlk3x8j5tf9jrujwuqju974u

i am just about to do this, is there an event kind for this? ACLs basically, right?

you should consider making it multithreaded tho

it could just use a tag on the npub of the bot so you at it and follow with a citation reference and it posts it

enoch is enoch!

you forgot that was his other name!

your argument seems to be that you can't run the internet without professional, educated asshats in data centers

or what

you are just a troll, good bye

about 5 weeks into the project at this point but nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 's starting points have helped a lot, as has nostr:npub1937vv2nf06360qn9y8el6d8sevnndy7tuh5nzre4gj05xc32tnwqauhaj6's work, his algia CLI client helped me a bit with learning how to write client side handling

not gonna say that i did it by myself because i haven't got the luxury of being paid to do it by myself, i have a 5 month roadmap to fill and i want to hit the target easily by 4 so we can get more related things done later

yeah, when i say "heavily refactored" i mean a lot of it i HEAVILY rewrote, the whole JSON parsing has been reworked to a more optimal engine than any generated garbage like what is used in go-nostr

i built it from fiatjaf's khatru, nostr-sdk and go-nostr repositories... the back end stuff i heavily refactored

i think that since you are comparing apples to oranges what about instant messaging clients on phones

sure, most of them use servers

but keet.io you only need to be running the client on your desktop and it picks up your messages and your phone can grab them too

for group chats anyway, i don't think they have (nor simplex) made it easy to share identities but with nostr i could do that tomorrow if i could throw together a quick GUI for a nostr chat client, it's beyond easy on the protocol level

i just osted a screenie of my relay's current memory usage, it's less than an average web app

so yeah... actually, things have progressed a long way since it was necessary to have hosting to run peer to peer services

my relay uses literally equal to one web page

yes, the internet has to have async

i am working towards phasing out my phone altogether and replacing it with VoIP based phone and SMS messaging, if that's possible, otherwise i get a dumbphone just for SMS and calls but it's gonna be some rugged thing and i'll want to throw it at the wall a few times

i'm not sitting up waiting for people to respond to me, when i'm at the computer, and not working, i'll check my messages, like i am now

the whole purpose and principle of nostr is exactly like email, you have relays (POP) and clients (SMTP)

currently lightning only has a sender, and the receiver must be alive for the message to send, there is no "try again later" option

people can run their own post offices and it's just like having a mailbox in front of your house, or you can have a post office box

these ideas that things must all be live and immediate is a product of conditioning designed to make obedient internet drones and cult mildcontrol slaves

you aren't one of those so yes you want async