nostr:npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w
nostr:npub1nxy4qpqnld6kmpphjykvx2lqwvxmuxluddwjamm4nc29ds3elyzsm5avr7
hey guys I appreciate what you're doing at nostr.build . I would appreciate it even more if you could explain your method for handling CSAM filtering.
Sadeq is working on next thw Dezh Nostr-based project which is a blossom server called nos3. (Nostr Simple Storage Service).
Same as other nostr:nprofile1qqst4k7a55r4w2ee0pfqfr48fuh08tvjkx4vqlpafcw7c96w3nwfv2spz4mhxue69uhk5etvd3ukv6tndqhxcctwvshst6rvu4 projects we care about spam protection, safety, control and management.
Also here is the repo:
{"admin":"💬 📉 Entropy Spike: A hidden file is transmitting data to an external location, Process tree visualization no longer renders properly."}
Is this something I can tie into grain? After I tie up what I'm doing with the client, testing and docs I think my next biggest things are blossom support. I want to try to have it in before next spring and release it when my cherry blossoms bloom next spring.
