If you can't read notes from nostr:nprofile1qqswgeqapmkhr5kscrmge56s34g0ekce2jkpendzd8wmk7ncjlpzv9qprfmhxue69uhhyetvv9ujuam9wd6x2unwvf6xxtnrdaksknl65g that means Nostr has failed.


Coming back to twitter 😅


🙃 https://image.nostr.build/bdfd07aa04ec6144fd4b9a0ed014495d733847f71a1e0396772d7b2000c73cae.jpg


This made me laugh a lot 🤣🤣🤣.


nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn Coracle is broken, by the way.
nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c same for Gossip.
The only thing that works is nostr:npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxg's Nostrrr.

If you want to browse the notes, go to https://nostrrr.com/p/nprofile1qqswgeqapmkhr5kscrmge56s34g0ekce2jkpendzd8wmk7ncjlpzv9qprfmhxue69uhhyetvv9ujuam9wd6x2unwvf6xxtnrdaksknl65g


https://highlighter.com/npub1u3jp6rhdw8fdps8k3nf4pr2slnd3j49vrnx6y6wahda8397zyc2qw7q7na also works, but doesn't support nprofile nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft


It has failed, I confirm


After reading bio I suspect that it's full of GFY


Algo não está certo! Não há o que ler, exceto pela sua menção ao perfil. Tem alguma ironia que não estou sendo capaz de perceber, amigo?!


Works for me, the timestamps are from a while ago so it takes a second to load


lol, this bot counts "gay" as a swear


also, it's all now on my relay so it will spread to whichever lunatics are periodically spidering it (i know at least one or two are on and off)


Failed.


NoStrudel appears to not show the notes??

https://i.nostr.build/POR05.png


Empty on Amethyst


but nobody uses "gay" any more in a casual way, it's either an in group word or an insult, thus it qualifies for many as a swear


Hello


Cannot read it with Amethyst. And I have their relay in my relay list.


What about these notes makes them more tricky for clients to find?


Actually, if I add relay.westernbtc.com as a relay, I *can* see this account's posts.


Add relay.westernbtc.com as a relay.


They're not published to the "default" relays.


Depends. This one was orphaned to nostr.mom  nostr:nevent1qqswu4rmrxu0ysc7rdl8rhxuk0yzh56rqnp2fptng56kl9gsa4jejmgppamhxue69uhk2tnwdaejumr0dspzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqvzqqqqqqyeu4h7d


nostr has failed.

Ah well. We tried.


? i can see them but there isnt much


Gossip fails for at least 2 reasons, probably more.
* The loading spinner hides the 'load more' button so you can't look back further
* I never finished and merged the code that loads N events (instead of a time period)

Can't find relay list for gitlost. Have no idea where the notes are published. Not sure why gossip isn't finding it I haven't investigated.


Now it works fine. Not sure if that's due to noStrudel having improved for old notes or my client is catching up with these long running queries or the notes are now on more relays ...


I see screenfuls of one-liners from 10 months ago.  But only after I reverted a commit and then pressed the Load More button 11 times.

I worked on code to fix this (load a count of messages, not a time period) but never quite finished it and then it has languished.  I need to get out my necromancer manual and reanimate that code.


Why not just ask the relay for whatever without specifying a time frame -- then working from that?


It's in purplepag.es, user.kindpag.es and relay.nos.social


Someone has probably broadcasted the notes to some other big relay.


How do you know?


Pack up, we are going home


they are on my personal cache relay as soon as they appear in my client... <3 nostrudel


empty on primal


If you can't read notes from nostr:nprofile1qqswgeqapmkhr5kscrmge56s34g0ekce2jkpendzd8wmk7ncjlpzv9qprfmhxue69uhhyetvv9ujuam9wd6x2unwvf6xxtnrdaksknl65g that means Nostr has failed.


If I could see them, I would read them. But maybe that’s your point.


Did I break the apps by general requests?


I see them


Ok. Cancel my “no can read” note…


350 days ago to be exact.


#Amethyst

nostr:nevent1qqsv740ulxcmmwzewytn7mlxu4ztj8w9ju0tnrm8jl7lnfnyg00lavgpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqzyrjxg8gwa4ca95xq76xdx5yd2r7dkx254swvmgnfmkah57yhcgnpgqcyqqqqqqgqz0wu8


Bring back gay!


Is this a thing outbox model fixes?


i know, what do we have to say now? happy? merry?


https://m.primal.net/IaRV.jpg
https://m.primal.net/IaRT.jpg


See it on #Freerse.


All notes can be seen on #Freerse. Nostr is successful. 🚀

https://image.nostr.build/bf2093cc08ca7278ed118e5562096e9a199716f1338750d1350494f095e9aaed.jpg
https://image.nostr.build/0c3d89ad79b4b4461c585e9c7bd5cef2c0dd3989f1429f4e29e181a35941f271.jpg


0xchat works, what’s the point? 🤔
https://m.primal.net/IaYW.jpg


You only see these few events that someone sent to relay.damus.io and nos.lol, you miss the other hundreds of events that are in relay.westernbtc.com.


You only see these few events that someone sent to relay.damus.io and nos.lol, you miss the other hundreds of events that are in relay.westernbtc.com.

Shadowbanning achieved.


Primal's got nothing.


If the #nostr elite say #nostr has failed, that means it is working!


We need more clients with outbox support 🥹
nostr:nevent1qqs2kln497095rxvc5ecwl5rmf23kv2z6p067x5dk2ywtheu4amdacspz9mhxue69uhkummnw3ezuamfdejj7q3q80cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsxpqqqqqqzxlrk9j


Works on amethyst, not on primal


we should send all of them to relay.damus.io and Nostr is fixed!


Probably some events are getting deleted either because of the images or videos in them or because of the profile picture. This is because they might not respect the requirements in a request that I made before and published on my Nostr and Twitter account.


Works fine.


works on next.nostrudel.ninja, but only after I fixed an issue where it wasn't getting the 10002 from purplepag.es

This seems like a little bit of an unfair test since nostr:npub1u3jp6rhdw8fdps8k3nf4pr2slnd3j49vrnx6y6wahda8397zyc2qw7q7na relay list event seems to only be on purplepag.es 🤔


Yes same for me  nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955,  nostr:npub1nz64zngcqm8vj8nhrdkcjpfwn2rcaqysnxec88tqfclp5afrpglsqm0w5y works and  nostr:npub13myx4j0pp9uenpjjq68wdvqzywuwxfj64welu28mdvaku222mjtqzqv3qk too, even the old Plebstr. Just a  nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg"problem" it seems.


This is a great tests for clients, If your client can only see about 10 events then its not loading the events from nostr:npub1u3jp6rhdw8fdps8k3nf4pr2slnd3j49vrnx6y6wahda8397zyc2qw7q7na relay wss://relay.westernbtc.com/
nostr:nevent1qvzqqqqqqypzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqqs2kln497095rxvc5ecwl5rmf23kv2z6p067x5dk2ywtheu4amdacslrdkys


It's also on user.kindpag.es and relay.nos.social which are known (to me at least) to store relay lists of everybody, but I shared the nprofile1 code here with the relay.westernbtc.com hint, which should have been enough, no?


nope, the fiatjaf failed


Primal

https://m.primal.net/IalA.png


This is why i keep nostr:npub1wyuh3scfgzqmxn709a2fzuemps389rxnk7nfgege6s847zze3tuqfl87ez on my home screen


oh I didn't see it was an nprofile. that would explain why noStrudel was able to get the profile at least.

Right now I don't have any way to tie mentioned relays in nprofiles to a user. if there is a relay in an nevent or nprofile it will use it for get the event or profile metadata but it does not remember it as being associated with the npub 😞


When is the last time it posted? Newest I can see is 10 months old


That is why I love my #noStrudel on #StartOS

https://m.primal.net/IaoN.jpg


now compare that with the notes in the nostrrr.com link in nostr:nevent1qqsf7nmxkfwjnj4gy5ykjqfaadqh237sfpqtzuu2cl3lllk6ndnelgspz9mhxue69uhnzdps9enrw73wd9hj7qgswaehxw309asjumn0wvhxcmmv9uq3wamnwvaz7tmzd96xxmmfdejhytnnda3kjctv9umgtgpj


⚡ The Infinitely Divisible Satoshi CLN v24.05


For a lot of different reasons, gossip's code is not structured in a way that my (or your) mental model would suggest. Partly these are for performance or ease of coding (earlier), and partly because it developed along a certain path which created a lot of technical debt. Refactors are in order.

I've tried to fix this issue several times under the title of "load more" and each time I've gotten so tangled up and confused that I backed out and attempted to attack the problem from another angle (usually being able to apply some small set of safe steps first).  90% of what I need to do is understood by me, but it's hard to find a way to do it which doesn't become a mess as I start tripping over the 10% that I haven't completely realized from the outset was going to trip me up.

I'm well down a path of fixing this now which has a good chance of actually succeeding.  The general plan is like this:
1) Keep an 'anchor' time for the feed (just one, it resets when you switch feeds).
2) The first subscription to the feed you switched to starts a long-term subscription that loads events from the anchor forward, and continues to listen after the EOSE.
3) Start a short term subscription that loads until the anchor, limit some number of notes (call it N).
4) When you scroll to the bottom and press 'load more', then anchor shifts to the created_at of the oldest feed event, and then this subscription is rewritten to load the next N events (the long-term subscription doesn't care about the anchor shift as it doesn't change).
5) Whenever you shift to a different feed (inbox, a different list, My notes, etc) everything is reset and it starts over.  This means is goes back to the relays again and often loads things from them it already has.
6) I will then create some kind of caching (not of events which we already cache, but of knowledge about which time ranges have been loaded with which filters) so that it doesn't reload the same events from the relay over and over.

Once this is done, it should be easier to modify from that point than from the current point, so if I discover this is hard to do I can work backwards somewhat.


I get most of it. What you describe is closer to my mental model.


Ok I fixed gossip on the 'load_more' branch.  It still needs testing and some more changes before it gets merged in, but you can try it now if you'd like (no schema changes, safe to switch back and forth).


If you can't read notes from nostr:nprofile1qqswgeqapmkhr5kscrmge56s34g0ekce2jkpendzd8wmk7ncjlpzv9qprfmhxue69uhhyetvv9ujuam9wd6x2unwvf6xxtnrdaksknl65g that means Nostr has failed.