😸 daily accepted events ~2.8M rejected non flood events ~2.4M rejected flood events 1M - 3M rejects based on IP ~2.2M rejects based on pubkey ~250K db size 348G 🤱 is like 7x less than the above in terms of events db size 108G if you or your app can't write to the relays ping me. 'flood events' are like thousands of events in minutes from same IP.

working on decentralized llm sharing. my current solution is an html page that fetches the listings and torrents from nostr network:

waifu-magnet

the python script running on a vps seedbox or dedicated box are making the torrents:

Gist

Torrent generator from HF link

Torrent generator from HF link. GitHub Gist: instantly share code, notes, and snippets.

the html is the ultimate decentralization but i may ditch that and do regular website to be more functional and have more control over curation (effective blocking of spam). i will need to calculate web of trust and it is too heavy for an html. the html upgrades itself! checks nostr network for a newer version, downloads from blossom and verifies the hash. presents the new version to the user. has anyone done such html apps with nostr?

My clanker made a script that - downloads files from a HF repo - calculates hashes - generates a torrent file Cool part is it is using HF as webseed for initial seeding. After more people start using the torrents it will switch to torrent network as default. Uploaded a few generated torrents: Gemma 4 E2B: https://nostr.download/909109e7fd7b69f947677df723b88613d09a52e151ca992cfdd3a52546dee411.torrent Minimax M3 UD-IQ2: https://nostr.download/3a438d921f8a760285033a1b5fdd0d4ce372560bb865f2184e39e9f488891e70.torrent Code:

Gist

Torrent generator from HF link

Torrent generator from HF link. GitHub Gist: instantly share code, notes, and snippets.

Hardest part was finding correct URL formation for webseeds. First I was using Minimax m3 and it struggled a lot but then GLM 5.2 found the solution. . The rest is trivial.. In my tests qBittorrent on ubuntu was less eager to try webseeds. Transmission app does a better job of initial fetching from webseeds. HF webseeds mean files are also linked to HF (but it does not validate the model files!). If anyone bans a model, we'll have decentralized ways to share.

update to the AHA Leaderboard's methods https://huggingface.co/blog/etemiz/aha-2026-leaderboard

Evaluated 16 models today. Dramatic change in top 3: Claude Opus went down fast: Grok did even worse with new version: Not much change in Gemini: Qwen is mediocre and stable: Inclusion AI seems to be doing well aligned models. Gemma 4 was a surprise, they came a long way since Gemma 2 which scored one of the worst in AHA 2025. Kimi was always bad in 2025 and 2026 but last model (2.7) seems to be doing better. Minimax M3 one of my fav vibe models, is 8th. Not bad! Full board: https://aha-leaderboard.shakespeare.wtf/ Gonna update the article soon.

who is following this guy? and what is his accuracy rate? https://www.instagram.com/cultivateelevate/

😸 has now 512 gb ram and protection from floods enjoy

removed a quarter of old notes from nos.lol because of ram. i didnt delete them yet. how many people want me to serve them in another address? a.nos.lol or e.nos.lol ? is there a relay multiplexer project that could sit between nginx and strfry and another archival relay software that will redirect requests to two relays and join the responses and serve the user? that way i could serve recent and archival events from the same address.

we don't dumb down we wise up

🤱nostr.mom is using AI to throttle spammy content for low WoT users based on their IP. it doesn't ban, it just throttles that IP and accept from spammer less and less. if anyone has problems with my relays, i can now blame AI 😄 checks are done on my GPUs so your IP does not leak to "big AI". if any tool or relay is blasting to nostr.mom its low WoT users was mostly blocked anyway because that rate is only for 1 user. however high WoT users will be a different set of algorithms and not affected by this change. so for blasters: not much changed.

i think nostr needs an AI layer. clients and relays are not enough. people are lazy and wont wait until they curate their follows. they want immediate hit with high quality content. the question is who will run the AI layer. what algo will the AI choose. how will clients use the resulting 'labeling' event (possibly 1985) h/t @Vitor Pamplona i am already doing processing of content for moderation. maybe i can extend it to also classify notes in terms of quality, attach keywords so it can be presented as a subreddit. then clients can say "i am interested in these keywords, but give me high quality notes". then a user dont have to see all the bitcoin trending content all the time, they can discover content in other topics.. for example i post about AI, relays, gardening and y'all have to see my every post in every topic. some gardeners probably hate my AI posts. 😃 but an AI can potentially find more relevant stuff and client can re-sort the feed for more relevance. what i propose is some people run bots (LLMs with open source code) and label events to make them more useful for efficient distribution, if clients like the code they can use labels from the bots they like. since label events will have tags for the original content it is easy to find the raw content.

been detecting nude pics using AI. seems to be working. not seeing much on nostr.mom. either i did a good job reducing nude pics on nostr.mom or those people left nostr too 😂 @Ostrich-70 is sending 1984 events to nostr.mom. anybody can use those events to filter out nude pics. now i am making an LLM analyze note content when WoT is small. when WoT of pubkey is small my relays count the spam from IP not pubkey. this analysis will help them further fine tune and decide what to do with the events coming from one IP. since i am vibe coding this, there is a small chance your IP gets leaked to AI inference engines like openrouter or minimax or kimi. if your IP is super sensitive consider a VPN.