-
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
move to self hosting #62
Comments
17 requests? I do remember we were discussing 50 isn't it? |
@mesb1 Elon keeps reducing it, that's why I suggested a self-hosting solution. For every user they would register their X app and manage their own hosting and have their own plan. But that would require creating a new project lol cause the current one was built counter the idea of self-hosting and it was never been considered while coding it. |
it's also fairly easy if you know enough about OAuth 2.0 |
Huh, i will try to reduce my posting via your app. |
Using own vps isn't big deal, if your app self contain everything and just needs to be started for x86\x86-64\arm machines. |
So do you have any plans? |
It doesn't really need a vps. it's just a program that executes when you try to post a tweet. making a request to the API and the Access token is stored locally somewhere in the config files. But it just needs some work and I'm not currently free. |
I have plans for later yeah. |
yeah it's mostly the registration part the requires that OAuth 2.0 knowledge and after that it's just 2-3 requests to the X API |
fully self hosted - no db - no authentication server
every user should create an app and use it.
due to 17 requests per day per app dummy pricing API plan
.x.json
The text was updated successfully, but these errors were encountered: