Not sure what is the answer for the first question, since my experience were limited to manage small-medium traffic relay (20+ GB/day). Maybe top relay operators will share their experiences later. I think top relays have big traffic more than 1TB/day.
> Hands on is sysadmin
Basic skills to manage linux or unix server such as configuring webserver (nginx, caddy, etc), setup proper firewall, ssh and account security, manage running service/apps (systemd, sysinit, etc), and basic linux/unix command knowledge were needed.
> Costs
Costs for running small-medium relay around $10/month . Varies depend on server provider.
> Preferred relay software
Currently using strfry. Other popular choices are nostr-rs-relay, nostream.
Update:
wss://nfrelay.app can be accessed normally (up) again. Thank you for the patience. Let me know if you are still having problem connecting/using the relay.
Took down the server all together ๐
PSA:
Due to unexpected problem coming from our hosting provider #NostrFilterRelay , wss://nfrelay.app currently cannot be accessed properly (down). We are really sorry for the inconveniences.
I see, thank you. I need to check again whether have similar issue or not. I haven't seen multiple reconnection issue yet from Damus users so far.
Thank you. It works properly now. ๐ซก
By the way, did you cross check the trending notes into nfrelay.app to filter in the last step?
Does the issue also happened with bostr (JS) or only happened with bostr2? I think we use same Websocket (ws) library in NodeJS so i wonder about it
Ah maybe it was entries in the local dB from before. Cleaned it now. Any plans to enable negentropy?
nostr:npub1nxa4tywfz9nqp7z9zp7nr7d4nchhclsf58lcqt5y782rmf2hefjquaa6q8 Did you deactivate Mostr DVM? It seems there is no response in the last few days
I think you can support HTTP/2 request easily in by enabling it in Nginx (Assuming using Nginx)
https://www.tecmint.com/enable-http-2-in-nginx/
It will solve connection issue without "hacky way".
I have no problem serving Damus users request in was://nfrelay.app because using Caddy that support HTTP/2 by default. Caddy intercept and reverse proxy the request properly in my case.
Yes, it has variation of "dry/summer" starting date prediction ๐
BMKG (Indonesia Climate Study Office) said the start of dry/summer season should be started from early March but it was varied in actual.
In my city, it is mostly cloudy in the last days with some days in light rain. Seems to feels like not a "dry/summer" season
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