This repository has been archived by the owner on May 26, 2023. It is now read-only.
[Idea] Allow providing own twitter and/or Mastodon app to use for cross-posting #906
Comments
Andre601
changed the title
|
I don't think this is a good way to circumvent the limits because it would mean twitter could detect several app accesses from the same IP and then ban the IP altogether (making the situation worse) if they consider that this is some kind of bad faith attempt at going above the limits. |
|
Okay. Then what other options are there outside of the self hosting? I once was thinking a github-action based setup, but that would probs use the same IPs... It's a lot to think about... |
renatolond
added a commit
that referenced
this issue
May 26, 2023
Closes #930, #913, #911, #906, #904, #897, #896, #895, #890, #886, #880 Closes #877, #872, #871, #868, #866, #863, #862, #859, #820, #810, #809 Closes #724, #721, #711, #688, #679, #606, #603, #593, #581, #577, #551 Closes #533, #517, #506, #505, #493, #430, #422, #311, #297, #241, #238 Closes #233, #197, #165, #164, #161, #160, #159, #151, #150, #148, #146 Closes #140, #139, #138, #135, #134, #127, #124, #123, #120, #119, #118 Closes #116, #112, #109, #106, #105, #103, #96, #90, #88, #86, #85, #74 Closes #65, #55, #47, #36, #33, #28, #19, #18 Closes #957, #955, #953, #950, #949, #936, #927, #925, #894, #873, #867 Closes #864, #650
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Given that the request for elevated API request limits has been denied, I had the time to quickly think about a possible idea her.
Idea
Allow people to provide their own App cridentials to use for the crossposting from/to twitter and Mastodon. If I understood it correctly are requests per application (on Twitter), so having a separate application could reduce the calls on the main one and allow the user a faster posting.
So basically, when user provides the accounts to link would there be an option to also provide apps. When set will the crossposter use those for the user instead of the default one, therefore having a separate rate limit bucket.
Possible Issues
One issue could be logging in I suppose? I assume the application requires you to "log in" using some token or cridentials to then interact with twitter, so in the end could there be a risk of sensitive data being leaked (Tho, you already store oauth approvals/tokens/... to post in the user's name, so....)
Why not self-host?
Obviously a good idea, but at the same time not 100% feasable for everyone. People like me may not have the spare money to even afford a small server/site/... to run this software on, even if it would be small in RAM, storage and bandwidth.
Disclaimer
This stuff was writter without having any in-depth knowledge about Mastodon's or Twitter's API, so forgive me if any information is wrong, outdated or alike.
Extra info
I originally asked this on Mastodon towards the crossposter account but thought it might be a good idea to make this issue to have a more open discussion where other people could provide their own input on this entire thing.
The text was updated successfully, but these errors were encountered: