Awesome! Thanks for sharing 🤙
Also working right now in a PoC to forward events to other relays as promised! I will let you know when the forward of events it's working ok 🤙
hey #[0] just finished fixing this bug... All URLs for nitter should be with `https` by now (including the profile metadata). Nevertheless, notes that the referenced in your example that are on other relay may appear with http as they are already registered.
I see... It's actually the feed generated by Nitter if you see (for this case) the actual feed (https://nitter.moomoo.me/SpaceX/rss) all links are with "http".
I will implement a solution to replace all links schemas to https if the server supports it. As you said it doesn't require to change the pubkey, I was wrong
It also appears to be a problem of the instance in moomoo.me. Other instances such as https://nitter.it/ handle the links ok (i.e. https://nitter.it/SpaceX/rss)
I see... It's actually the feed generated by Nitter if you see (for this case) the actual feed (https://nitter.moomoo.me/SpaceX/rss) all links are with "http".
I will implement a solution to replace all links schemas to https if the server supports it. As you said it doesn't require to change the pubkey, I was wrong
Hmm it could be happening on my side… 🧐 I will check this first. Because all nitter feeds need to be with https, isn’t it?
In that case when fixing the possible bug I can change that in batches… but the pubkey will change… how do you see it?
Definitely seeing much faster performance when generating the profiles on https://nostr-twit.glitch.me/
Awesome work dude! Very much looking forward to the rss profiles broadcasting to other relays. Will make them even more reliable to access and less of a drain on your relay!
Thank you! 🤙 Will come soon!!
🤣🤣 Well that’s good to try to figure how to scale this! We will make it 🤙
Thanks! I'll let you know! at the moment I'm migrating the app to another server with more capacity (CPU, RAM...) The migration should be with near zero downtime and I plan to perform it tomorrow 🚀
Yeah, thats a good idea! Definetely going to implement and initially test with my public relays 🤙
Now I'm prioriticing to make it stable regarding any load (including this proposal), so I can work in improving it and adding features
Hmmm I will take that into account for other feeds as well when creating a feed 👍
Awesome work!! Thank you! I’m scaling the relay to keep everything ok 🤙
Let me know if you have performance issues
🙂
Any thoughts on an API endpoint so that if I send a GET request to https://rsslay.nostr.moe/api/create?url=https://nitter.moomoo.me/paulg/rss for example, it could return json like:
{
"Public Key (Hex)": "09ecfafa65d246a218dea31b941a0a7ff06d4d82e10ca7487176f61a035084fe",
"Public Key": "npub1p8k047n96fr2yxx75vdegxs20lcx6nvzuyx2wjr3wmmp5q6ssnlq76g4xn",
"URL": "https://nitter.moomoo.me/paulg/rss"
}
This would make things easier for the Twitter follows import project I mentioned earlier.
Hey #[3] the API is finally implemented. You can make a GET request to /api/feed as you commented (i.e. https://rsslay.nostr.moe/api/feed?url=https://nitter.moomoo.me/paulg/rss) and get/create the feed profile! Hope you like it 🤙
Any thoughts on an API endpoint so that if I send a GET request to https://rsslay.nostr.moe/api/create?url=https://nitter.moomoo.me/paulg/rss for example, it could return json like:
{
"Public Key (Hex)": "09ecfafa65d246a218dea31b941a0a7ff06d4d82e10ca7487176f61a035084fe",
"Public Key": "npub1p8k047n96fr2yxx75vdegxs20lcx6nvzuyx2wjr3wmmp5q6ssnlq76g4xn",
"URL": "https://nitter.moomoo.me/paulg/rss"
}
This would make things easier for the Twitter follows import project I mentioned earlier.
Good idea! Will implement it... I will let you know when its live 🚀
Thanks!
#[0] THANK YOU for this fix, the duplicate/triplicate text from Nitter's rss feeds was driving me nuts
https://github.com/piraces/rsslay/commit/fb3c91dbd761338ccdf4ce2faae6bd49f412e9a4
You are welcome! 🥰
When they go live to the App Store it will be a revolution ⚡
Ouch!! Will review it… do you have more details on the crash?