But America won't exist soon (the sovereign individual)

In my mind, if I was a teenager, it was the 90s 😂

But Canada won't exist soon (the sovereign individual)

Another fun tax fact

Small business/solo contractors only pay 9% combined tax on profits under $500k

First 50k in personal dividend income from your business is tax free

They've been treating business class quite well here, much much lower taxes than USA

Jerks' daily job is to find targets, not sure if deindexing from aggregators would help much, you should then deindex from major public relays too, and only post your stuff on paid relays (paid to read, not only to write). Meaning, you shouldn't be on public Nostr if you're afraid to be found by someone determined to find you.

I think the only anti-harassment solution that could work on Nostr is client-side filtering, based on contact/mute lists, friends' reports, etc. Don't show replies from people you don't follow, or that were reported/muted many times by people you follow, or replies from public relays. I bet some of these policies are implemented an nos.social, but the issue is - everyone's using Damus/Amethyst/Primal, and those have nothing like that.

The way I see it, we should have a separate pluggable layer/API/NIP for content post-filtering, that can be plugged into any app: an app forms a feed (main/replies/notifs/anything) and then passes all the events from the feed to the filter, and filter returns various labels (spam/harassment/nsfw/impersonation/...), and app covers the content of the labeled event and shows labels above it. This way apps don't have to rebuild their feed building logic - just apply another layer above it, users would specify the filtering API endpoint in the settings and get the filtering they want. Safe mode could be 'cover notes from users I don't follow until filter returns it's labels - uncover if no bad labels returned', more reckless mode could be 'show notes first, only hide them if filter returns some bad labels'.

If nos or anyone is interested in experimenting with me in this area, let me know.

That's so fucking funny that's literally what I'm listening to that prompted my gm note

Lol yah me neither anymore 🤣😉

Not currently listening to g unit

Gm,

If you grew up listening to hiphop in the 90s

I know you sang along the word nigga at least 1000 times, don't lie

When you call the 'notifications' method, you subscribe to the notification channel from that precise moment. Anything sent before that moment is not included in the channel.

In the code you were subscribing to the relays very early and then you were sending the metadata event (if one of the relays is offline it may take some seconds to continue). Therefore, when the `notifications` method was finally called, it's likely that the events had already been received (but not included in the notification channel).

---

I'll update the documentation of the "notifications" method.

man. shit really popped off this evening on #nostr

I'll give that a shot here in a bit. what are you thinking the issue might be?

hmmm okay. I may have to dive into it more because that is not the behavior I was seeing. it appeared to remember what I had seen on subsequent restarts when using Event, but perhaps I am, how you say, a dipshit. will test again and inform.

Try to move the `client.subscribe` code and filter in the `process_reminder_notifications` func, between the `let mut notifications = client.notifications();` and `info!("listening for notifications");`