5
No post scheduling scripts yet? (monyet.cc)
submitted 3 years ago by to c/plugins@sh.itjust.works
5 comments fedilink hide all child comments
 

I mean, I wanted to start work on it, but if someone's already released/working on one then I'd just happily use those instead.

Also, the absence of a thing usually means it's not possible to have. In my mind I think it's easy to have userscript code make API posts on behalf of the user, but maybe somehow in the intricate layers of tech it's made impossible or tedious. If so, I'd like to know before I learn it the hard way.

all 5 comments

sorted by: hot top controversial new old
[–] 2 points 3 years ago (1 child)

!lemmydev@lemm.ee may be able to help

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] [S] -1 points 3 years ago (1 child)
    • it's not federating any content to my instance.
    • going to that instance and performing a search also outputs no results.

    but thanks for the heads up! I'll ask there about this as well.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 3 years ago

    going to that instance and performing a search also outputs no results.

    If you mean searching for "schedule" in that community, I can confirm I didn't see anything.

    But, if you mean that you don't see any post at all at this URL https://lemm.ee/c/lemmydev , that would be weird

    Anyway, good luck!

  • permalink
  • fedilink
  • source
  • parent
    • [–] 1 point 3 years ago (1 child)

    FYI: Posted right now:

    Note that you need to send your credentials, so you must trust the developer.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] [S] 0 points 3 years ago*

    that's a major security risk. even the reddit predecessor uses app tokens (though with the death of 3pa idk if such things still work). that's why I want something that only runs on the client side.

    tbf there's nothing stopping userscripts from stealing your jwt token in the cookie, which is just as big a security risk, but at least with userscripts you can read the source code.

    my plan would be similar to that one in which I store the jwt with the scheduled posts, with the notable difference of the data remaining on the browser storage. i wont even need to see any passwords since the jwt is already in the cookie which the script could read off of.

  • permalink
  • fedilink
  • source
  • parent