plhery / unfollowninja Goto Github PK

We just have to call "docker-compose up" inside of unfollowNinja-server/tests (instead of npm test)

Currently, to fight false notifications, we double-check some information to confirm an unfollow, and in some cases (e.g "left twitter") we wait 15min and check that the user is still unfollowed before sending the notification.

We could create a task triggered 20min after each unfollow notification, check that the user is still unfollowed, and gather stats to help us fight the cases where we notice the user is not unfollowed anymore.

Some ideas:

• do some cases (e.g "left twitter") happen more often than others?
• can cross-checking with another user's tokens help?
• can cross-checking with another twitter IP help?
• are these always the same users? Do these have something in common? (private, soft-blocked...)
• (more difficult) how much time happens before they're refollowed?

Started logging in, authorized, and the site throws out an error before going back to homepage

Relogged into twitter, same thing

For the users who don't want to give access to their DMs (which is understandable)

Could be useful for the UI / stats / a 2020 unwrapped...

depends on #11

A new UI made with react was made https://unfollowninja.netlify.com, but never finished.

I connected unfollow monkey to my accounts a few days ago and I have not gotten one notification for any unfollow or anything

I can't see the graceful shutdown logs in docker logs when I restart the docker container... Is there something wrong, is the SIGTERM signal correctly sent?

UnfollowNinja sends a notification that @userSoftBlocked unfollowed you if you block @userSoftBlocked for a moment and then unblock them.

Expected Behavior

A notification that the user (I) blocked @userSoftBlocked.

Current Behavior

A notification that @userSoftBlocked unfollowed the user.

Steps to Reproduce

1. Find a user that follows you ;
2. Block them for a second ant then unblock them ;
3. Wait for the DM from your unfollowNinja instance.

Recheck every unfollows 15min later and possibly send a "@xxx follows you again".

Currently to share work between the (currently 8) node workers/threads/CPUs, I use a task queue.
Which means every minute, ~10 000 tasks should be created in redis then dequeued then marked as done then deleted.
I believe we could make these faster by making each thread process one (twitterID % 8). One worker may finish slightly before the others, but with that amount of users, it should not be that significant, and things should go faster.

Currently the backend is a bit mixed with the legacy express.js UI, which can generate pages with the users's information by wildly/hackily sharing a cookie with the API.

Instead of loading everyone's whole list of followers from the DB, store a hash of them, and load them only if there was a change.
We'd still need to download that whole list from Twitter

Kudos to @GeoffreyFrogeye for the idea https://twitter.com/GeoffreyFrogeye/status/1282637796168081408

Can you please create an docker image for the UI?

It's been years the backend can switch a param to send DMs in English, but it never made its way to the UI

Though I'm not sure if it's wise as there is a 100 000 limit for Twitter apps (there may be exceptions?).
So it may be better to create a separate i18n twitter app/account/website.

All twittos usernames are currently stored in redis, to retrieve them if some of them leave Twitter.
I estimated that these were using 25% of redis space.
There is not that much read/write operations so there is no reason to store these in an in-memory db.

(We should copy/keep/update our users's usernames in redis though, as these are currently accessed ~10 000 times/minute)

I temporarily deleted my account. I re-stored my account about a few weeks ago. Once I tried to gain access to this service it kept giving me the same message, it’s saying I need to log out & log back in. I do that, then it repeats the message. Not sure what else I need to do.

As Kue is deprecated https://github.com/Automattic/kue