Count me in 😎

Thank you very much!! 🤙

Have you checked if you are blocking all the trackers and ads out there? Interesting tool to check here: https://d3ward.github.io/toolz/adblock.html

Just wanted to try it out... 👀

Also... it's bluesky based or have an integration with nostr? What is the plan of #[2]?

Wen bluesky? Anyone will to share an invite code? 🥺

Will investigate too! 🤙

Well... will continue investigating 🧪

🤯 Can’t wait for my invitation to come!!

Yes, for rss feeds of twitter I recommend using https://nitter.moomoo.me/ instead of nitter.net. This last instance fails frequently 🤨

Thank you my friend! 🤙

Hi! this issue has just been solved... Sorry for the inconvenience caused. Please try to refresh the page to avoid the browser to get old assets from the cache. Let me know if it continues happening 🤙

New rsslay version v0.4.4 released!

In this version:

- Changed info in main page to no longer reference nitter.net and instead reference nitter.moomoo.me (more stable one) 🛠️

- Random feeds to discover on each load of the main page 🌐

- Content length of emitted events is now configurable (set to 5000 chars on rsslay.nostr.moe) 📄

- Fix an annoying bug which will reset relay list when following a profile in the page 🪲

- Bumped libraries, cleaning, and improved stability 🚀

Check it out at https://rsslay.nostr.moe/

Any feedback is always welcome!!

P.S. Much more to come!!

Yep. Same for me 🥲

Will try to reproduce both cases and I will keep you updated 🤙

Does #[0] extension injects `window.nostr` in the current page? I assume that but I'm now browsing in Edge (👀) and it's not being injected. Therefore I can no use pages such as coracle.social and so on...

Wow!! I like it a lot... Great work 🤙

Zapped for zapping a zapper of a zapper and continuing the chain ⚡

#[0] looks like last cycle of zapper failed to pay everyone... just letting you know 🤙

Support for SSL. I will love to connect vía "wss://" instead of "ws://" this will allow me to use webapps with my PC running Tailscale.

I know its already secure but webapps will not accept it😢

It's awesome so far!! Great work and congrats! #[2] 🤙

Testing from the app from getcurrent.io 🧪

Just checking!

Yeah! Its about a simple `` entry in the RSS feed pointing to the comments section of that RSS entry. You can see them in #[4] (stacker.news) or #[5] (WordPress blog)... As you can see a simple "Comments: [URL]" is added before the final link 🤙

New #rsslay version v0.4.3 launched! 🚀

In this version:

- Improved lists of relays to reply events to (ones with "sync" support with another relays, to improve reacheability) 🔗

- Support for RSS comments (common in Wordpress sites or stacker.news for example) 🌐

- Bump dependencies 📚

- Testing 🧪

Check it out: https://rsslay.nostr.moe/

BTW: actually handling almost 15.500 profiles

Changed https://relay.nostr.moe (wss://relay.nostr.moe) to paid to avoid spam... My attempt to make a reliable, spam free relay. You can now check it out for 1000 sats 🤙

Received! I posted on the issue at GitHub too. I just released v0.3.4 which should fix the crash and the version number problems 🤙 Let me know if you found issues

Ah! My fail sorry 😞 forgot to update some variables. Will fix that!

rsslay improvements deployed 🚀:

- Now it can authenticate with other relays vía NIP-42 to sync messages

- Now syncing with more relays (thanks #[0] )

- Modified UI with links to profiles in different clients (also a link with NIP-21 scheme)

- Others 👾

Enjoy! 🤙

Will investigate this way. Thanks! 🤙

Hmm I have been thinking and I have some concerns regarding smashing other relays with lots of events... Analyzing some of the most used relays use #nostream which have a rate limit by default... Any ideas?

Crossing fingers!! 🤞🙏This will be huge! 🤙

#[1]

Should be fixed by now! Nevertheless, some older notes could be shown with `http` due to being already in other relays...