https://git.mills.io/yarnsocial/yarn/pulls/759
Gopher/Gemini users would now be able to see who follows them.
https://git.mills.io/yarnsocial/yarn/pulls/759
Gopher/Gemini users would now be able to see who follows them.
https://git.mills.io/yarnsocial/yarn/pulls/759
Gopher/Gemini users would now be able to see who follows them.
https://git.mills.io/yarnsocial/yarn/pulls/759
Gopher/Gemini users would now be able to see who follows them.
yarnd specifically built (_recently_) exponential moving average backoff for fetching feeds (_not yet a default feature_) and we spec'd out a # refresh = <seconds> that authors can put into their feed's Metadata.But otherwise, yes you are right. I _believe_ this is the biggest weakest in serving feeds over Gopher/Gemini IHMO -- having no caching controls or mechanisms whatsoever 😢
yarnd specifically built (_recently_) exponential moving average backoff for fetching feeds (_not yet a default feature_) and we spec'd out a # refresh = <seconds> that authors can put into their feed's Metadata.But otherwise, yes you are right. I _believe_ this is the biggest weakest in serving feeds over Gopher/Gemini IHMO -- having no caching controls or mechanisms whatsoever 😢
If-Modified-Since etc.) is another problem. The “archived feeds” extension somewhat helps with that. Other than that, I don’t there’s anything else we can/should do. 😕(I sometimes forget about this issue because I have a 50 MBit/s line and I only fetch feeds every 15 minutes. I don’t really notice. But it doesn’t scale, that’s correct.)
If-Modified-Since etc.) is another problem. The “archived feeds” extension somewhat helps with that. Other than that, I don’t there’s anything else we can/should do. 😕(I sometimes forget about this issue because I have a 50 MBit/s line and I only fetch feeds every 15 minutes. I don’t really notice. But it doesn’t scale, that’s correct.)
If-Modified-Since etc.) is another problem. The “archived feeds” extension somewhat helps with that. Other than that, I don’t there’s anything else we can/should do. 😕(I sometimes forget about this issue because I have a 50 MBit/s line and I only fetch feeds every 15 minutes. I don’t really notice. But it doesn’t scale, that’s correct.)
After all, there *are* other ways of notifying users about followers. Like, just send an e-mail. Or ping someone on IRC. Or whatever. I think that it would *help* if there was a solid built-in mechanism in twtxt – but it’s not *strictly* required.
@benk has already mentioned that this might not be the most pressing issue.
To be completely honest: I’m lazy when it comes to implementing new features and I use HTTP anyway, so this is not my *personal* agenda. 😅 I’d be perfectly happy with dropping this idea, if it doesn’t gain enough momentum.
After all, there *are* other ways of notifying users about followers. Like, just send an e-mail. Or ping someone on IRC. Or whatever. I think that it would *help* if there was a solid built-in mechanism in twtxt – but it’s not *strictly* required.
@benk has already mentioned that this might not be the most pressing issue.
To be completely honest: I’m lazy when it comes to implementing new features and I use HTTP anyway, so this is not my *personal* agenda. 😅 I’d be perfectly happy with dropping this idea, if it doesn’t gain enough momentum.
After all, there *are* other ways of notifying users about followers. Like, just send an e-mail. Or ping someone on IRC. Or whatever. I think that it would *help* if there was a solid built-in mechanism in twtxt – but it’s not *strictly* required.
@benk has already mentioned that this might not be the most pressing issue.
To be completely honest: I’m lazy when it comes to implementing new features and I use HTTP anyway, so this is not my *personal* agenda. 😅 I’d be perfectly happy with dropping this idea, if it doesn’t gain enough momentum.