Mungkin satu atau dua bulan sekali kak. Ini juga karena sekalian pas jalan-jalan ๐
Sesekali memanjakan lidah

#foodstr
Is this preparation for Nostrasia2024 , Takumi-san? ๐
I think this can be achieved by implementing custom proxy relay in front of regular relay.
Custom proxy relay <-> Regular relay (Strfry, Nostream, etc)
Custom proxy relay can provide GraphQL, Rest API, RPC or any implementation to fetch nostr events with custom way from regular relay.
GWS om. Istirahat cukup, kurangin begadang. Moga cepat fit lagi.
Congratulations.. wish you have a wonderful family โค๏ธ
Yes, It can be used independently either by custom relay or custom nostr client
topic-classification-api v0.1.0 module has been released.
Integration of new feature "Topic Classification" will come soon in the next #NostrFilterRelay update. This feature will mark 95% of #NostrFilterRelay target features.
Happy to say "The last milestone is migration of events into NIP-32 compatible" ๐.
https://github.com/atrifat/topic-classification-api/releases/tag/v0.1.0
Can you link (source code repositories) which relay who have no storage? I think the minimum implementation use RAM as storage.
"Nostr is the simplest open protocol that is able to create a censorship-resistant global 'social' network once and for all."
โ nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6
Congratulations nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 , Our CEO of Nostr. ๐ /s
Additional option ๐ค
3. Short term relay (Serving 7 last days event only) with long time archival only for metadata (kind 0,3,10003)
The third option only need around 12GB in my experiment
Nice, 0xChat nostr:npub1tm99pgz2lth724jeld6gzz6zv48zy6xp4n9xu5uqrwvx9km54qaqkkxn72
supports sign in with Amber
All can be downloaded at zap.store
nostr:npub1g24xhk0qx6za23gyd4wg87d399kf7vnn2yh2umaqf0q8kd6tn8mq7wpfjl
Klien nostr alternatif seperti Nostrmo juga mulai mendukung Amber mas bisa dicoba ๐
Thank you Cody. Oh related to hub feature, yesterday I think i found that there is small UI bug. In UI panel it shows that relay tray was still connected (green status) with hub but actually it was disconnected (shown in hub webpage status: 0 connected)
Yes, rarely to open nostr DM. ๐
I have already sent the reply (Giftwrap DM). Have you received it? Otherwise I will send regular DM (NIP-04)
I use nak REQ to my local relay tray yesterday after sending event through hub relay. But, no worry, it seems yesterday I only have connection issue. It is ok, it works properly now ๐
There is another bug. Using v1.5.0 AppImage, with the following setting: Default block and only allow kind 1. But local relay tray reject all events including kind 1 that was supposed to be accepted.

Yes, probably. There are also other issues. I will post the detail in repo issues later,
Cody, I have tested v1.5.0. It works properly when requesting event (REQ) through hub relay. The hub fetch my local relay tray event. But, it is not forwarding event to local relay when i send event (EVENT message) through hub relay. Is it not implemented for now?