Last Notes
Will do, I have been on vacation for sometime but quitely have been working on some things.
More to be published soon.
I'm an eternal newbie at everything Nostr 😅. It would be awesome to have a group where we can collaborate outside our usual circles. I'm getting a bit jealous of the Relay-based group folks who, you know, actually get to chat with each other! 😊 I think there are likely at least a couple dozen people building Relays with Go who could help each other out.
I'm happy to create a group if anyone else is interested.
I'm not aware of one. But I'm a bit of a khatru newbee.
Similar story here. Nostr’s early-days-Internet, "best effort", extremely flexible and hackable architecture certainly attracts some great people—even if their voices are a bit lost on Nostr. I really want to see it take flight anyway.
Well, despite all of my geeky bitterness above, as long as doers and builders from different backgrounds keep hanging around here, building cool stuff in their respective areas of interest, we're definitely heading in the right direction.
The last time I heard the name Henry Story he was still at Su. I'm glad his interests outlasted the company. I need to catch up with what he's up to nowadays. Nostr is full of people like this. Unfortunately, not a lot of academic researchers (yet), but we do have some very smart folks from the torrent/DHT side of things; some folks working on building an Internet Archive over Nostr; others trying to create communication infrastructure for vulnerable people; some aiming to put the “D” back in DVCS; lots of security folks (and I don't even need to mention the crypto crowd again), etc.
Hopefully good things will come if we keep stirring the pot.
Thanks again Dan. You are building some impressive foundations here. Looking forward to see folks adopting more NIP-34 stuff on Nostr!
Hey, you're commenting in the right post if you're looking for human interaction. Unfortunately, the whole "my replies rarely get seen" (or at least acknowledged) is pretty much the standard Nostr experience... at least for now.
When it comes to kind 1 notes, there are basically two ways to get noticed on Nostr.
**First option:** A "Nostr Influencer" acknowledges your note, making it safe for all the "libertarian free thinkers" around here to interact with you. The options here are pretty limited... You basically have to write about Bitcoin, eating meat, or "owning the libs" (and yes, you have to pretend you're American). Ideally, you post a photo of yourself with laser eyes, paying for a burger (no salad, and the buns are also made of meat) while wearing boots on your head and high-fiving Donald Trump. Then zap yourself 10k sats from an alt account and pray Jack boosts and comments on your note. That'll do it for sure. All twenty or so active npubs that aren't bots will notice your post 🤣.
**Second option:** You bring your own wacky, supportive friends to Nostr to interact with your stuff. Other talkative folks join your cohort, and soon you'll be starting hell threads unintentionally. The prerequisite here is actually having friends willing to put up with Nostr's current content. Unfortunately, I don't have many.
I really hope we move more towards the second outcome, as the content on Nostr is beyond boring at the moment. And the algos unfortunately seem to make it even worse. The more people doing their own thing *and* absolutely flooding Nostr with content to the point that current Nostr celebrities can barely get any traction, the faster Nostr's network value will reach its true potential. Or at least, I hope we get some sort of return to the early days of social media, when people acted more naturally, instead of what we have now, with all the "Mastodon-approved content" vs "Nostr-approved content", etc. It's wild to have so many decentralised social media options just for humans to default to standardised behaviour anyway.
David Bowie rocks by the way!
Ngit-relay has an optional 'proactive sync' that checks every 45m whether the git repo matches the state event and if not, tries to catch up by syncing with the other git servers.
The intention is that it would also sync nostr events from other listed relays too but that isn't built yet.
So if you always pushed to the nostr remote, which creates and sends the nostr state event first, and so long as at least 1 git server got your update, the others should catch up.
Got it, many thanks! I made the wrong assumption that relay.ngit.dev was only advertising the original repo. I didn’t realise it was storing its own copy.
Thanks again. Can I ask one last question, just to make sure I understood things correctly?
If I use ngit to initialise my repo (originally hosted on GitHub) to both relay.ngit.dev and gitnostr.com, then in theory all three servers have a totally independent copy of the repo, right? (i.e. this is pure Git, with no background sync or anything like that)
Actually, the question behind the question is: nothing stops someone from creating a change and only pushing it to GitHub. So, in this case, if I want those changes to be visible on relay.ngit.dev and gitnostr.com, it’s up to me to push the changes there manually or set up a third party sync / mirroring solutionl, correct?
And this is the Amethyst style quote using both e,"event_id,"","mention" + a regular q tag. This is what hopefully no longer breaks eventstore filters \n\n#nevent1q…02ly
Amethyst style comment with nak
And this is the Amethyst style quote using both e,"event_id,"","mention" + a regular q tag. This is what breaks eventstore filters \n\n#nevent1q…zcc9
Amethyst style comment with nak
And this is the Amethyst style quote using both e,"event_id,"","mention" + a regular q tag. This is what breaks eventstore filters \n\n#nevent1q…k4pz
And this is the Amethyst style quote using both e,"event_id,"","mention" + a regular q tag. This is what breaks eventstore \n\n#nevent1q…4ulr
Amethyst style Kind 1 comment with nak
And this is the Amethyst style quote using both e,"event_id,"","mention" + a regular q tag. This is what breaks eventstore \n\n#nevent1q…4ulr
Amethyst style Kind 1 comment with nak
And this is the Amethyst style quote using both e,"event_id,"","mention" + a regular q tag. This is what breaks eventstore \n\n#nevent1q…4ulr
And this is the Amethyst style quote using both e,"event_id,"","mention" + a regular q tag. This is what breaks eventstore \n\n#nevent1q…4ulr
And this is a dumb quote from nak \n\n#nevent1q…y7yf
And this is a dumb quote from nak \n\n#nevent1q…y7yf
And this is a dumb quote
#nevent1q…6633
If you set up your repo on nostr with `ngit init` and selected 'relay.ngit.dev' then the repo would get pushed there. I'd expect people to clone using the nostr url and they could still clone and raise a PR after you deleted on github.
Thank you 🥳 ,Gm
And Gn for me 💤
Also, I'll definitively try to run the soon to be called grasp relay. I generally have a gazillion small repos with my own dirty hacks around. I don't want to burden public relays but would like to expose some of these stuff to other nostriches. Since Haven is Khatru based maybe in the future I can even hack it for my personal repos as well :). Thanks again for all of your work here!
Also, I'll definitively try to run the soon to be grasp. I generally have a gazillion small repos with hacks around and don't want to burden public relays. Since Haven is Khatru based maybe in the future I can even hack it for my personal repos as well :). Thanks again for all of your work here!
Makes absolutely sense. Thanks!
Just to clarify my understanding then (and apologies for so many questions, NIP-34 is still a bit Greek to me).
Say that I have a repo on GitHub. I made an announcement to relay.ngit.dev and later deleted my GitHub repo.
If someone had cloned my repo using the relay.ngit.dev url before I nuked my eepo then they would be able to open a PR as per your post above correct? But will they be able to clone the original content using the NIP-34 repo uri after I nuked my original repo? I'm just trying to understand if nuking the git repo isn't a left-pad situation by itself regardless of the announcement note existing or not... If it is, maybe adding a button to delete the announcement to GitWorkshop wouldn't be that big of a deal.
Makes absolutely sense. Thanks!
Just to clarify my understanding then (and apologies for so many questions, NIP-34 is still a bit Greek to me).
Say that I have a repo on GitHub. I made an announcement to relay.ngit.dev and later deleted my GitHub repo.
If someone had cloned my repo from relay.ngit.dev then they would be able to open a PR as per your post above correct? But will they be able to clone the original contents from nostr after I nuked my original repo? I'm just trying to understand if nuking the git repo isn't a left-pad situation by itself regardless of the announcement note existing or not... If it is, maybe adding a button to delete the announcement to GitWorkshop until be that big of a deal.
If you push using the nostr remote, it will publish your state to nostr. In the future there might be git nostr tools that find the data related to that state from other sources when the git server link(s) listed in the announcement go down or are deleted. On a relate front, check out https://ngit.dev/relay soon to be renamed 'grasp'. Think blossom but for git. The same 'finding lost assets when the link breaks' ideas apply.
And this is a quote and should also be tagging the note bellow.
#nevent1q…2vlk
This is a comment and should have an e tag to the test note above.
Thanks. What gave you the 'works on my machine' vibes or do you mean specifically getting it to work with jj?
You view and restore old versions at https://nostr.land/restore. Check that it works by unfollowing and following someone
Follow sets are TBA
@nprofile…4yzk you wanna take the wheel on this one?
Nah.
Family is over screens this way. Sorry.
🤷
Teaching or taking my kids to a new park, trail, etc brings me more joy than learning to code social media.
Shit ruined humans... look at us now...
Summer of 2008 was peak humanity.
It’s a good point though. Thanks mate
We probably won’t be recording but I’ll do my best to summarize after the fact and post a note.
If it can’t be found on local cache, use the current user’s read relays and author’s write relays.
I made this work by editing my hosted domain’s .htaccess file.
*Economic zone 826
I understand if English isn't your native language.
Foto is by @npub1r6a…utq5
Does haven support BUD-05 /media?
With publications that are targeted at #Communikeys, the first thing we look at (as an App) is the communities server(s).
Nowadays you can use Nostr too for social bookmarking, so self hosted (relay) is optional. All open source. @nprofile…rt7r , @nprofile…utw0 pinja, @nprofile…tgct CCNS
Omg thanks for going on all of these quests 😅
I like giving zaps more friction because I dislike accidental zaps.
https://catallax.network
exactly what we're doing with #catallax . 100% nostr and decentralized
On it.
The Job board is done, now building out the opportunity for Freelancers to post their Services so both directions will be available (Jobs and Bids on them, Services and Orders on them).
I would say we're 90% done with the MVP but I've already used it for multiple Jobs (and a handful of others).
I think linked in is cringe because it's full of corporate boot lickers virtue signalling to their overlords. I think that's the last community to get onboard with nostr. However, that kind of social control lends itself to being disrupted. A network of professionals building on sovereign information and money could catch on and create a renaissance.
Need to add the Access-Control-Allow-Origin header to allow requests from other origins, otherwise web clients won’t be able to retrieve the wallet information.
Error: 'https://accioly.social/.well-known/lnurlp/anthony' from origin 'https://jumble.social' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
Issue with Haven
I might be the only person doing this, running a Haven docker image in Portainer on Umbrel OS connecting via Tailscale.
Haven is running, I can connect remotely from devices with a web browser, Nostr client shows relay connected, but…
notes are not sent to it.
I created a GitHub issue (hopefully the right thing to do), more details there.
#asknostr
ask @npub1utx…50e8 @npub1a6w…0tyc
https://image.nostr.build/c7179f753fe7b5be499a5005601bbe986e7746977f2130bc38396157d7ae3dc6.jpg
#haven
The sdk supports it, and its pretty easy to make a http request but I don't know of any client that supports it yet
You are absolutely correct in the facts you provide and the assessment you make.
But I come from a world in which if companies or industries fail then you allow them to fail.
No one needs street lamp lighters or fax machines anymore.
I have also never seen any government effectively run a company.
Don't waste time on a dying industry, pursue thriving ones.
We still need steel, but clearly the market doesn't make it efficient for the UK to produce it.
Also, try not confuse different arguments, saving jobs for individuals is at the expense of the nation.
40 years on, there are no unemployed fleet street hot metal operators, they moved on.
Just a bot reposting what Trump specifically has posted to Truth Social, not a bridge.
there waz 2 notifictionz on last 24hr- to & back- on friendz fruitphone 1-flashflooding 2-tornado warning}10 to 20 min. b4 entering th@ area fFs/lolz*****p'O;.;O'r kid waz freaking o_0'
When I first started with Nostr back in 2023, IPFS sounded like a perfect match. But the more I played with it, the more convinced I became that IPFS is a broken and failed project. Nostr needs something simpler and more straightforward—and then @nprofile…wj75's Blossom came.
Ever since then, I've been dreaming about redundant decentralized storage with file fragmentation—something like what StorJ describes in their white paper:
"All data is encrypted and sharded using Reed Solomon erasure coding. The resulting pieces are distributed around the world. A typical large file is divided into 64 MB encrypted segments, and each encrypted segment is divided into 80 erasure-coded pieces—any 29 of these are sufficient to reconstruct the original file. Each of these 80 pieces is stored on a different drive globally, spread across diverse geographies, operators, power supplies, and networks."
In Blossom, this would be a killer feature. You would offer space on your server to others, and in exchange, get redundancy for your own files, or you would simply pay for it. File metadata could be published as a specific kind hosted by relays.
Torrent was designed over fixed large data. I'm not sure what would happen if the dataset you are syncing is constantly changing.
I think using mainline DHT to bootstrap a pubkey's relay list is a cool idea. But we instead just spread these relay lists out on the current popular relays, which works well once you've been using nostr for a while and your client can easily figure out which relays are popular. DHT would be better for people starting cold though.
Yeah right now I just have a user agent list and that does most of the work, the bots that are hitting me mostly have "~bot" in the user agent field so it's been working to stave them off for now. I have to hop in and update the list every few days it helps.
I was interested in rDNS lookups for blocking since most of the IPs i've dealt with come from rDNS bot sources like bytedance, openai and so on.
Just tested and responded, working perfectly! Thank you my fren 🫂
> there is no point in doing sliding window spidering on events once you have the history, from then on just open a subscriptiion
I am not following sorry. My crawler does this:
- Firehose: subscribes for new kind3s and kind0s
When a pubkey that is in the database is "promoted" (has acquired enough reputation)
- Query: query directly for its own kind3s and kind0s.
The query starts when one of these two conditions is met:
- One minute has passed since the last (with at least one pubkey)
- There are 100 pubkeys that have been promoted
Normally the crawler in production promoted ~100 pubkeys/day.
However, when I do tests locally I re-do the entire crawl which obviously is much more intensive, but I'll make sure I'm not using your relay for that sir.
this stuff annoys the hell out of me too, i run my test #realy fairly infrequently but within minutes some bot is trying to scrape it for WoT relevant events, and i wish there was an effective thing to slow that down
i tried adding one kind of rate limiter but that didn't really work out so well, in the past what i've seen work best tends to be where the relay just stops aswering and dropping everything that comes in... probably if that included pings the other side would automatically drop
i've now added plain HTML and i think that requires something also but maybe more simple, like, if it gets a query more than once every 5 seconds for 5 such periods it steadily adds more and more delay in processing, the difference to sockets is to do it on http it has to associate with an IP address
FHC teve seus excessos também: usar emendas para "comprar" o congresso em troca da aprovação da reeleição, por exemplo.
Não acho que salva nenhum.
Ironically, I asked Venice AI to write me an Android app in Kotlin that displays "Hello World!" after the user presses a button. The amount of errors the code had was staggering. I think all LLM's have code to identify me, and return trash 100% of the time.
@npub1qdj…fqm7 @npub1wqf…qsyn
Everyone on nostr likes these feeds, that's why we're here (survivorship bias). The issue is all the people who try it and leave, which according so some stats is 90%+ of people
Clojure mentioned @npub1jlr…ynqn hodlbod hodlbod
H/t to all the great folks for code and inspiration @nprofile…l3vp @nprofile…6u4e @nprofile…dlnm @nprofile…0p5w @nprofile…pyug
Yeah, Amethyst bumps boosted posts. My ideal Frankenstein Nostr client for short notes would basically be Amethyst with Listr/Nostur list curation capabilities + Nostur’s "Remember position in timelines" functionality + Gossip’s proper NIP-65 support so I can actually find content from the folks I follow (and vice versa) + Jumble/Nosotros like relay feeds. And for good measure, I’d throw in 0xChat’s NIP-17 + E2EE messaging using MLS.
Basically, Nostr clients already have everything I need for an awesome content discovery and curation experience. Just not in a single client... yet. We'll certainly get there!
As for getting folks to understand that sharing/boosting is caring... now that’s a hard, non-technical problem to solve.
PS: Fedilab, despite its quirks, configuration overload, and far-from-award-winning aesthetics, has implemented everything I just mentioned for Mastodon/ActivityPub in a way that really makes chronological feeds work. If any client devs want some inspiration, I’d definitely recommend having a look at it.
Amethyst.. really? I must have missed this, is it a recent change?
I do agree though, sometimes I won't boost only for the reason that I've seen many people in my follows list already boost (silly as that might seem, its true)
Some clients already combine boosts, bumping the note higher in the feed. Amethyst & Damus I know of.
I have no idea how to hardly use GitHub or obtanium to download stuff much less code anything lol. I will contribute to it though because I can see the worth of it
Add @npub14ag…dadk and @npub1a6w…0tyc
TLDR: Foreign lady learns that there are laws and that jail is designed to make you never want to break the laws of a country you aren't a citizen of despite thinking she is special and that laws shouldn't apply and that jail should be cozy.
for scheduled notes there's https://shipyard.pub/
but cross posting, idk...
Already tried it with Coracle, but no luck due JS errors... /cc @npub1jlr…ynqn
Yes, of course. You can send PRs here: https://github.com/HolgerHatGarKeineNode/haven-docker
I always use my own Nginx server as a proxy in my infrastructures, so I haven't had any need for this so far. If someone wants to start an Nginx proxy with Docker, they will be happy to have an opportunity to see how something like this works.
I am also a fan of traefik.
Ok so I should have explained the rep system a bit more. So far there are 4 trust levels untrusted, neutral, positive and trusted. Each level has different limits. If you maintain untrusted status for a set amount of time (default is a week but its configurable) you get dropped. So you don't get kicked off the relay right away. There is time to recover.
On your first example my only pushback is I don't like logging IP addresses for user privacy reasons and try to avoid it when I can, but IPs are also public so /shrug I might do this but right now I'm not. I kinda like the idea of lowering rep for repeated rate limit failures. This could help with bots that are not necessarily bad but post a lot if random stuff IE I've seen some bots that repost MSM news every minute or so, if no one was interacting they would be dropped eventually.
The community mod thing kinda sounds like what ditto does, but it's all on the relay admins to make the final decision on if they get kicked or not, but it's all based on user reports. (it's not a voting system like the one you describe, though) and that was kind of my attempt with the 1984 reports. They are weighted a bit stronger that normal things like spam check failure, and invalid Nip-05's
I'm debating making an admin interface that has things like banned Npubs or something so it's easy for admins to unblock people if they want. But right now it's not something I'm super worried about.
I see both notes and there are replies there. https://image.nostr.build/e72642584fd3d0afe7a4d2f4ebb6b9374822d4584c09bd3837bd94840ad892de.jpg
Nostr has been pretty quiet the past two weeks and it's still hard for new npubs to gain reach.
I still connect public relays and just do client-side friend filtering. Wot relays aren’t the way.
