-
Notifications
You must be signed in to change notification settings - Fork 9
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
Twitter API changes #139
Comments
@jdyke any opinion on the matter? |
Hey hey! I can't imagine the cost of premium tier is worth it. Last I checked it was a thousand or so a month? I'm actually not sure what the current status is because they were supposed to start charging by now and the bots are able to tweet. re: mastodon: I think that's a good idea and if twitter never changes their policy, or adds a free tier, maybe it makes sense to have both twitter and mastodon! Having a larger presence on social media is not a bad thing in this scenario. I haven't looked into the API docs for mastodon but I don't believe its too complicated. |
I saw a headline about them going back on it and the docs still say pending
so we'll see. I'll get clearance on which mastodon server to use, I'm
leaning towards infosec.exchange. the API is super simple, only outstanding
thing I see it whether mastodon supports the nice gh cards or if we need to
recreate those. Not a deal breaker either way. I'll try to get some work done on this in the next few days.
|
Look into Threads? |
Good thought. I'll take a look at the threads api.
I'm tempted to just convert it to a Jekyll page with an rss feed. Not
trying to be philosophical over practicality but the trend of shielding
posts behind a login modal is a little too popular at the moment.
@jdyke Any thoughts?
…On Thu, Jul 6, 2023, 23:23 TheFoxMac ***@***.***> wrote:
Look into Threads?
—
Reply to this email directly, view it on GitHub
<#139 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEAGP76YK5PD2A2LWKTTYTXO56LDANCNFSM6AAAAAAUYHABFM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
@jdyke @TheFoxMac @twenny thoughts on scrubbing |
They rolled back the login reps. Twitter as a whole has degraded but my
other bot still works with the new api updates. Have you logged into the
dev UI recently? Could be something to acknowledge. I don’t have the creds
to check.
…On Mon, Jul 24, 2023 at 10:54 AM Aaron Rea ***@***.***> wrote:
@jdyke <https://github.com/jdyke> @TheFoxMac
<https://github.com/TheFoxMac> @twenny <https://github.com/twenny>
thoughts on scrubbing twitter X integration completely? I haven't had
time to refit this and I'm not convinced the value outweighs the effort now
that you are required to log in to see any content.
—
Reply to this email directly, view it on GitHub
<#139 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AESDV5LOZORIZGD422XYTOLXR2ECHANCNFSM6AAAAAAUYHABFM>
.
You are receiving this because you were mentioned.
|
analyze recent changes to the twitter api and determine a course of action to include:
The text was updated successfully, but these errors were encountered: