Skip to content

RSS Feeds for updated & new userscripts and forum #2026

Open

Description

@sjehuda

What is missing?

RSS

Why?

So we receive updates automatically by RSS Reader.

Alternatives you have tried.

No response

Activity

  1. added
    enhancementSomething we do have implemented already but needs improvement upon to the best of knowledge.
    on Dec 3, 2023
  2. sjehuda commented on Dec 3, 2023

    @sjehuda
    Author

    I want to implement RSS feeds for OUJS.

    I was thinking of using jpmonette/feed

    This is not rerlated to #914

    Where can I get an API key to practice on OUJS?

    Is there a server that OUJS (dev) can be tested on?
    I'm not in the mood to create a setup /OpenUserJS/OpenUserJS.org/blob/master/.github/CONTRIBUTING.md

    Reference https://openuserjs.org/discuss/Web_feeds_(AtomRSS)#comment-187d6346b27

  3. Martii commented on Dec 3, 2023

    @Martii
    Member

    I want to implement RSS feeds for OUJS.

    Maybe. It depends on if the VPS can handle the traffic and how it may be abused in our current bad actor environment.

    I'm not in the mood to create a setup /OpenUserJS/OpenUserJS.org/blob/master/.github/CONTRIBUTING.md

    That's how it works. Find the mood please.


    jpmonette/feed

    Needs npm . Our build/exec/deploy is currently my domain since I maintain the backend... so no extra build steps at this time... or you will have to seriously sell me on it which won't be easy.

  4. added
    featureSomething we don't already have implemented to the best of knowledge but would like to see.
    and removed
    enhancementSomething we do have implemented already but needs improvement upon to the best of knowledge.
    on Dec 3, 2023
  5. sjehuda commented on Dec 4, 2023

    @sjehuda
    Author
  6. Martii commented on Dec 4, 2023

    @Martii
    Member

    I do get error of "HTTP 429 Too Many Requests" when I navigate pages
    with Back and Forward buttons, yet much less in recent months.

    That's #1548 and continual everywhere else as well. We've reduced some of it but alterations happen with the bad actors. Until I can get more resources in the back-end this has to be the way... more costs more money.

    I assume that this is what would happen when someone would scan given
    feeds too often.

    Yes and the caching (http, rss/atom, and limiter(s)) will be enforced... which is why there is a maybe on this issue. The bad actors literally have nothing better to do in their nets and constantly hit unprotected sites.

    Do you think it would be good to make this error message (429) of feed
    paths in the form of XML so that it would appear as a message inside
    RSS Readers that don't specify the exacy reason for network errors?

    This is partially related to the last half of #1971 ... still pondering this. Translations would eventually be nice to have but I haven't run by any tool kits in JavaScript/Node that actually handle this gracefully yet alone MVC which can be done with a "code" that goes into the View... but before I got here that wasn't implemented so there's a bit to change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureSomething we don't already have implemented to the best of knowledge but would like to see.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions