-
-
Notifications
You must be signed in to change notification settings - Fork 408
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
t list add LISTNAME USERNAME says page not found #437
Comments
yeah same issue here, anyone find a fix? |
same
|
Ran into this as well. Looks like the issue is actually in list creation -- I can add members to lists I already have, but if I create a new list, its name in the twitter API has a number appended to it:
and then,
and it does what you'd expect: So as a workaround:
I suspect the issue is an upstream change and thus belongs in https://github.com/sferik/twitter and not here but I've only glanced at it so far. |
Okay, now that I've looked around I don't believe that anymore! sferik/twitter correctly notes that
The problem is that That's easy to fix one way or another, but before I do anything I'd love @sferik's thoughts on how this should work, esp. since you can now(?) have two lists with the same name (but different slugs). Perhaps |
working for me now. on a slightly related note, i think i hit a 24 hour rate limit (although I'm not sure where this is documented for lists) Maybe some how broke the 15000 / 24 hour because: the first time i used so then i decided to split things up into chunks, and doing it in 50 increments seemed to be working. i got to around 600 users in the list, and then it stopped working.and now nothing works. surely there is a more efficient way to do this, but this is the closest 'working today' solution i've come across so far. |
Hah, yep, I hit it too while I was testing this out more! There is apparently an undocumented list rate limit which is approximately(?) 1000/12 hours (although it might be something like 1000 members/12h + 300 members grace period after you hit it). Unfortunately it looks like when you hit that rate limit, the Twitter 1.1 API does nothing and returns success, so there's no way to tell that you hit it other than it not doing what you requested. Some details here, although I only saw the "104" error there through the browser console on twitter.com, not through the API. |
Hmmm @wlonkly, grep doesn't output anything for me when doing this here. Any ideas? |
@cprkrn looks like something else changed, probably upstream again. Here's what I see when I create a list and then list all my lists: ~ t list create following-`date "+%Y-%m-%d"`
@chadoh created the list "following-2022-08-23".
~ t lists
@chadoh/1561891375242547202 @chadoh/1562067642759843841
@chadoh/blockchain @chadoh/citrusbyte
@chadoh/codes @mattdlockyer/interesting-crypto-peeps-46301
@chadoh/lancaster-14909 @chadoh/near
@chadoh/philly @chadoh/politik
@chadoh/remote @chadoh/space If I go to https://twitter.com/chadoh/lists/, I can see the "following-2022-08-23" list. If I click on it, I can see So list names are no longer part of the list slug/id at all. That's why piping to grep and searching for the name you used shows nothing. To make things easier, you can create a variable with the id of your list. This uses bash/zsh syntax; if you're on windows or in some other shells, you might need to look up how to set variables in that context: ~ export LIST=1562067642759843841
~ t list add $LIST account-name |
No combination works.
Am able to create a list, but not add any users.
The text was updated successfully, but these errors were encountered: