@pipedream/twitter 0.3.10 → 1.0.0

package/actions/unlike-tweet/unlike-tweet.mjs

@@ -1,40 +0,0 @@
-import twitter from "../../twitter.app.mjs";
-
-export default {
-  key: "twitter-unlike-tweet",
-  name: "Unike Tweet",
-  description: "Unike the tweet specified specified in the ID parameter. [See the docs here](https://developer.twitter.com/en/docs/twitter-api/v1/tweets/post-and-engage/api-reference/post-favorites-destroy)",
-  version: "0.0.2",
-  type: "action",
-  props: {
-    twitter,
-    id: {
-      propDefinition: [
-        twitter,
-        "tweetID",
-      ],
-    },
-    includeEntities: {
-      propDefinition: [
-        twitter,
-        "includeEntities",
-      ],
-    },
-  },
-  async run({ $ }) {
-    const {
-      id,
-      includeEntities,
-    } = this;
-
-    const params = {
-      $,
-      id,
-      includeEntities,
-    };
-
-    const res = this.twitter.unlikeTweet(params);
-    $.export("$summary", "Successfully unliked tweet");
-    return res;
-  },
-};

package/actions/upload-media/upload-media.mjs

@@ -1,114 +0,0 @@
-import twitter from "../../twitter.app.mjs";
-import fs from "fs";
-import mime from "mime";
-
-export default {
-  key: "twitter-upload-media",
-  name: "Upload Media",
-  description: "Upload images or other media types to Twitter. Returns a `media_id_string` to be used with the Create Tweet action. [See the docs here](https://developer.twitter.com/en/docs/tutorials/uploading-media)",
-  version: "0.0.2",
-  type: "action",
-  props: {
-    twitter,
-    file: {
-      type: "string",
-      label: "File",
-      description: "The file to upload to Twitter, please provide a file from `/tmp`. To upload a file to `/tmp` folder, please follow the doc [here](https://pipedream.com/docs/code/nodejs/working-with-files/#writing-a-file-to-tmp)",
-    },
-    mediaType: {
-      type: "string",
-      label: "Media Type",
-      description: "The MIME type of the media being uploaded",
-      options() {
-        return Object.values(mime._types);
-      },
-    },
-    mediaCategory: {
-      type: "string",
-      label: "Media Category",
-      description: "The category that represents how the media will be used",
-      options: [
-        "amplify_video",
-        "tweet_gif",
-        "tweet_image",
-        "tweet_video",
-      ],
-    },
-  },
-  async run({ $ }) {
-    // INIT
-    const fileContent = fs.readFileSync(this.file, {
-      encoding: "base64",
-    });
-    const fileSize = (fs.statSync(this.file)).size;
-    const params = {
-      command: "INIT",
-      total_bytes: fileSize,
-      media_type: this.mediaType,
-      additional_owners: this.twitter.$auth.oauth_uid,
-    };
-    if (this.mediaCategory) {
-      params.media_category = this.mediaCategory;
-    }
-    const { media_id_string: mediaId } = await this.twitter.uploadMedia({
-      params,
-      $,
-    });
-
-    // APPEND
-    const size = 9000;
-    const numSegments = fileContent.length / size;
-    let segment = 0;
-    let startIndex = 0;
-    let endIndex = startIndex + size;
-    while (segment <= numSegments) {
-      const chunk = fileContent.substring(startIndex, endIndex);
-      const params = {
-        command: "APPEND",
-        media_id: mediaId,
-        media_data: chunk,
-        segment_index: segment,
-      };
-      await this.twitter.uploadMedia({
-        params,
-        $,
-      });
-      segment++;
-      startIndex += size;
-      endIndex += size;
-    }
-
-    // FINALIZE
-    let response;
-    response = await this.twitter.uploadMedia({
-      params: {
-        command: "FINALIZE",
-        media_id: mediaId,
-      },
-      $,
-    });
-
-    // STATUS
-    while (this.mediaCategory?.includes("video")) {
-      response = await this.twitter.uploadMedia({
-        params: {
-          command: "STATUS",
-          media_id: mediaId,
-        },
-        method: "GET",
-        $,
-      });
-      const { processing_info: info } = response;
-      if (info?.error) {
-        throw new Error(JSON.stringify(info.error));
-      }
-      if (info?.state === "succeeded") {
-        break;
-      }
-      setTimeout(() => {}, info.check_after_secs * 1000);
-    }
-
-    response && $.export("$summary", `Successfully uploaded media with Media ID ${mediaId}`);
-    return response;
-  },
-};

package/old.md

@@ -1,169 +0,0 @@
-<p align="center">
-
-<img width="124" height="100" src="/images/twitter/TwitterLogo.png">    
-</p>
-<h1 align="center"><strong>Twitter Workflow Automation</strong></h1>
-
-
-<p align="center">Patterns for processing streams of tweets and interacting with the Twitter API</p>
-
-<p align="center">
-    <a href="#example-workflows"><img width="30%" src="/images/twitter/ExampleWorkflow.png" alt="Getting Started"></a>
-    <a href="#twitter-event-sources"><img width="30%" src="/images/twitter/TwitterEventSources.png" alt="Example Worksflows"></a>
-    <a href="#sse-and-rest-apis"><img width="30%" src="/images/twitter/SSE_RESTAPI.png" alt="SSE + REST API"></a>
-</p>
-
-&nbsp;&nbsp;
-
-## Example Workflows
-Workflows are linear sequences of steps — just Node.js code —hosted and run by Pipedream.
-
-**You can copy the workflows below and run them in your Pipedream account** [**for free**](https://docs.pipedream.com/pricing/ ). They run code on new tweets and interact with the Twitter API in creative ways. You can modify or extend them in any way you'd like, [**running your own Node code**](https://docs.pipedream.com/workflows/steps/code/) or using [**pre-built functions**](https://docs.pipedream.com/workflows/steps/actions/) to connect to [**200+ integrated apps**](https://docs.pipedream.com/apps/all-apps/).
-
-On copy, you'll be asked to create a [**Twitter event source**](#twitter-event-sources) that triggers your workflow on new tweets matching your target search.
-
-A single Twitter source can trigger multiple workflows. If you already created a source you want to use as a trigger, click **Select Another Trigger** near the bottom-left of the source selector.
-
-<p align="center">
-    <a href="https://pipedream.com/@dylan/twitter-to-email-p_zACral/readme"><img alt="Twitter to Email" src="/images/twitter/T2Em.png" width="45%"></a>
-    <a href="https://pipedream.com/@dylan/send-an-http-post-request-on-new-tweets-p_6lCRoN/readme"><img alt="Twitter to Webhook" src="/images/twitter/T2We.png" width="45%"></a>
-</p>
-<p align="center">
-    <a href="https://pipedream.com/@dylan/twitter-to-aws-sqs-p_vQCraZ/readme"><img alt="Twitter to AWS SQS" src="/images/twitter/T2AS.png" width="45%"></a>
-    <a href="https://pipedream.com/@dylan/twitter-to-aws-eventbridge-event-bus-p_ZJCWpg/readme"><img alt="Twitter to AWS EventBridge" src="/images/twitter/T2AE.png" width="45%"></a>
-</p>
-<p align="center">
-    <a href="https://pipedream.com/@dylan/twitter-to-aws-lambda-p_wOCAdP/readme"><img alt="Twitter to AWS Lambda" src="/images/twitter/T2AL.png" width="45%"></a>
-    <a href="https://pipedream.com/@dylan/twitter-to-telegram-p_QPC8JP/readme"><img alt="Twitter to Telegram" src="/images/twitter/T2Te.png" width="45%"></a>
-</p>
-<p align="center">
-    <a href="https://pipedream.com/@pravin/twitter-mentions-slack-p_dDCA5e/edit"><img alt="Twitter to Slack" src="/images/twitter/T2Sl.png" width="45%"></a>
-    <a href="https://pipedream.com/@dylan/twitter-to-discord-p_MOCQ9Y/readme"><img alt="Twitter to Discord" src="/images/twitter/T2Ti.png" width="45%"></a>
-</p>
-<p align="center">
-    <a href="https://pipedream.com/@dylan/twitter-to-s3-p_KwCZGA/readme"><img alt="Twitter to S3" src="/images/twitter/T2S3.png" width="45%"></a>
-    <a href="https://pipedream.com/@dylan/twitter-to-pipedream-sql-service-p_brCMA9/readme"><img alt="Twitter to SQ:" src="/images/twitter/T2Sq.png" width="45%"></a>
-</p>
-
-&nbsp;&nbsp;
-
-## Twitter Event Sources
-
-Pipedream [**event sources**](https://docs.pipedream.com/event-sources/) emit Twitter events in real time: tweets, follows, likes, and more. Sources can trigger [**Pipedream workflows**](#example-workflows), and can be accessed via [**SSE or REST APIs**](#apis).
-
-Click on a source below to get started.
-
-<p align="center">
-    <a href="https://pipedream.com/sources?action=create&amp;url=https%3A%2F%2Fgithub.com%2FPipedreamHQ%2Fpipedream%2Fblob%2Fmaster%2Fcomponents%2Ftwitter%2Fsearch-twitter.js&amp;app=twitter"><img alt="Search Mention" src="/images/twitter/SM.png" width="45%"></a>
-    <a href="https://pipedream.com/sources?action=create&amp;url=https%3A%2F%2Fgithub.com%2FPipedreamHQ%2Fpipedream%2Fblob%2Fmaster%2Fcomponents%2Ftwitter%2Fmy-tweets.js&amp;app=twitter"><img alt="My Tweets" src="/images/twitter/MT.png" width="45%"></a>
-</p>
-<p align="center">
-    <a href="https://pipedream.com/sources?action=create&amp;url=https%3A%2F%2Fgithub.com%2FPipedreamHQ%2Fpipedream%2Fblob%2Fmaster%2Fcomponents%2Ftwitter%2Fnew-follower-of-user.js&amp;app=twitter"><img alt="New Follower for User" src="/images/twitter/NFfU.png" width="45%"></a>
-    <a href="https://pipedream.com/sources?action=create&amp;url=https%3A%2F%2Fgithub.com%2FPipedreamHQ%2Fpipedream%2Fblob%2Fmaster%2Fcomponents%2Ftwitter%2Fnew-follower-of-me.js&amp;app=twitter"><img alt="My New Followers" src="/images/twitter/MNF.png" width="45%"></a>
-</p>
-<p align="center">
-    <a href="https://pipedream.com/sources?action=create&amp;url=https%3A%2F%2Fgithub.com%2FPipedreamHQ%2Fpipedream%2Fblob%2Fmaster%2Fcomponents%2Ftwitter%2Fmy-liked-tweets.js&amp;app=twitter"><img alt="My Liked Tweets" src="/images/twitter/MLT.png" width="45%"></a>
-    <a href="https://pipedream.com/sources?action=create&amp;url=https%3A%2F%2Fgithub.com%2FPipedreamHQ%2Fpipedream%2Fblob%2Fmaster%2Fcomponents%2Ftwitter%2Ftweets-liked-by-user.js&amp;app=twitter"><img alt="Tweets Liked by User" src="/images/twitter/TLbU.png" width="45%"></a>
-</p>
-<p align="center">
-    <a href="https://pipedream.com/sources?action=create&amp;url=https%3A%2F%2Fgithub.com%2FPipedreamHQ%2Fpipedream%2Fblob%2Fmaster%2Fcomponents%2Ftwitter%2Fuser-tweets.js&amp;app=twitter"><img alt="New Tweets from User" src="/images/twitter/NTfU.png" width="45%"></a>
-    <a href="https://pipedream.com/sources?action=create&amp;url=https%3A%2F%2Fgithub.com%2FPipedreamHQ%2Fpipedream%2Fblob%2Fmaster%2Fcomponents%2Ftwitter%2Fnew-trends-by-geo.js&amp;app=twitter"><img alt="New Trends by Geo" src="/images/twitter/NTbG.png" width="45%"></a>
-</p>
-
-Let's see how sources work with an end-to-end example:**running code on new mentions**.
-
-Most Twitter bots react to other tweets. For example, you might want to reply to a user with a specific message every time they mention you. Or you may want to store every tweet with a specific hashtag in an Amazon S3 bucket.
-
-When you create a Twitter bot, you typically have to sign up for a Twitter developer account, create your own app, host it somewhere, and run code to poll for new tweets. This is a means to an end:**all you really want to do is run code on new tweets**.
-
-```js
-// Don't care how I get tweets
-for (const tweet of tweets) {
-    // Just want to run code
-}
-```
-
-Pipedream lets you create a stream of tweets you can process programmatically in seconds, avoiding the app setup entirely. These are called [**event sources**](https://docs.pipedream.com/event-sources/).
-
-Pipedream runs the code to poll for new tweets matching your search terms, emitting them as events you can run code on.
-
-<p align="center">
-    <img alt="pipeDream" src="/images/twitter/TwitterPipeDream.png">
-</p>
-
-Then, you can immediately process those tweets in a few different ways:
-
-+ Trigger a Pipedream workflow for each tweet, running hosted Node.js code in real time
-+ Subscribe to a private SSE stream, which also publishes tweets in real time
-+ Access tweets in batch using Pipedream's REST API
-
-To get started, [**create a new Twitter search source in the Pipedream UI**](https://pipedream.com/sources?action=create&amp;url=https%3A%2F%2Fgithub.com%2FPipedreamHQ%2Fpipedream%2Fblob%2Fmaster%2Fcomponents%2Ftwitter%2Fsearch-twitter.js&amp;app=twitter&amp;src=twitter.pipedream.com). Name the source, connect your Twitter account, and add your search term:
-
-<p align="center">
-    <kbd><img alt="Twitter Source in Pipedream UI" width="700" src="/images/twitter/twitter-source-in-ui.png"></kbd>
-</p>
-
-You can also visit [**https://pipedream.com/sources**](https://pipedream.com/sources) and click the **Create Source** button, then choose the **twitter/twitter-search.js** source from the modal that appears.
-
-Then, you can trigger a [**Pipedream workflow**](https://pipedream.com/new) — a serverless Node.js script — on every tweet:
-
-<p align="center">
-    <kbd><img alt="New workflow source" width="550" src="/images/twitter/new-workflow-source.png"></kbd>
-</p>
-
-
-They should work as is, but you can modify them in any way. For example, you can add a step to [**run any Node.js code**](https://docs.pipedream.com/workflows/steps/code/) or use [**pre-built functions**](https://docs.pipedream.com/workflows/steps/actions/) to send data to other destinations.
-
-
-&nbsp;&nbsp;
-
-## SSE and REST APIs
-
-Pipedream provides two other interfaces for accessing events produced by sources:
-
-+ A private SSE stream specific to your source
-+ A REST API
-
-This way, you can run an event source in Pipedream but access its events in your own application.
-
-### SSE
-
-SSE —[**Server-sent events**](https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events)—defines a spec for how servers can send events directly to clients that subscribe to those events, similar to [**WebSockets**](https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API) and related server-to-client push technologies. If you listen for new items using SSE, **you can run any code in your own application, in real time, as soon as those items are added to the feed.**
-
-Streams are private by default. You authenticate by passing your Pipedream API key in the Authorization header:
-
-```js
-$ curl -H "Authorization: Bearer API_KEY" \
-
-    https://api.pipedream.com/sources/SOURCE_ID/sse
-```
-
-[**See the Pipedream SSE docs**](https://docs.pipedream.com/api/sse) for more information on authentication, example Node code, and other details on the interface.
-
-### REST API
-
-If you prefer to process tweets in batch, you can fetch them using [**Pipedream's REST API**](https://docs.pipedream.com/api/rest/):
-
-```js
-$ curl -H "Authorization: Bearer API_KEY" \
-
-    https://api.pipedream.com/v1/sources/SOURCE_ID/event_summaries?limit=1
-```
-
-Note the?limit=1query string. You can vary the number of events returned (most recent first) by setting this param.
-
-Please [**reach out**](https://docs.pipedream.com/support/) with any questions or feedback. We're happy to add other Twitter-specific developer resources to this list, and we'd love to hear what can be improved about event sources or the example workflows.
-    
-&nbsp;&nbsp;
-
-___
-
-<p align="center">
-Pipedream, Inc. — San Francisco, CA
-</p>
-<p align="center">
-<a href="https://twitter.com/PipedreamHQ">Twitter</a> | <a href="https://pipedream.com/community">Community</a> | <a href="https://docs.pipedream.com/">Docs</a> | <a href="https://pipedream.com/terms">Terms</a> |
-    <a href="https://pipedream.com/privacy">Privacy</a>
-</p>
-
-___

package/sources/common/followed.mjs

@@ -1,38 +0,0 @@
-import twitter from "../../twitter.app.mjs";
-import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";
-
-export default {
-  props: {
-    twitter,
-    db: "$.service.db",
-    timer: {
-      label: "Polling interval",
-      description: "Pipedream will poll the Twitter API on this schedule",
-      type: "$.interface.timer",
-      default: {
-        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
-      },
-    },
-  },
-  methods: {
-    _getPreviousIds() {
-      return this.db.get("previousIds") || [];
-    },
-    _setPreviousIds(previousIds) {
-      this.db.set("previousIds", previousIds);
-    },
-  },
-  async run() {
-    const previousIds = this._getPreviousIds();
-    const followedItems = await this.getFollowed();
-    for (const item of followedItems.reverse()) {
-      if (previousIds.includes(item.id)) {
-        continue;
-      }
-      previousIds.push(item.id);
-      const meta = this.generateMeta(item);
-      this.$emit(item, meta);
-    }
-    this._setPreviousIds(previousIds);
-  },
-};

package/sources/common/followers.mjs

@@ -1,159 +0,0 @@
-import twitter from "../../twitter.app.mjs";
-import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";
-
-export default {
-  props: {
-    db: "$.service.db",
-    twitter,
-    timer: {
-      label: "Polling interval",
-      description: "Pipedream will poll the Twitter API on this schedule",
-      type: "$.interface.timer",
-      default: {
-        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
-      },
-    },
-  },
-  hooks: {
-    async activate() {
-      await this._provisionFollowersCache();
-    },
-  },
-  deactivate() {
-    this._clearFollowersCache();
-  },
-  methods: {
-    /**
-     * This method returns the size of the internal cache used by the event
-     * source to keep track of the latest Twitter followers of the corresponding
-     * account.
-     *
-     * The size represents the maximum amount of entries/ID's that will be
-     * cached at any given time (or 0 for unlimited). Keep in mind that the
-     * Pipedream platform itself imposes size limits as well in terms of DB
-     * usage.
-     *
-     * @returns The maximum amount of Twitter followers entries to be cached at
-     * any given moment (or 0 for unlimited).
-     */
-    getFollowersCacheSize() {
-      return 0;
-    },
-    getScreenName() {
-      // When screen name is not explicitly provided, the Twitter API defaults
-      // it to the user making the API request
-      return undefined;
-    },
-    /**
-     * This function provides the list of relevant, follower-related, user ID's
-     * that are used by the event source to emit events. How each event source
-     * that implements it depends on the purpose of the event source itself. For
-     * example, an event source that emits an event for every new follower will
-     * implement this function in such a way that its result is a list of user
-     * ID's for each new follower detected.
-     *
-     * @returns the list of relevant user ID's for this event source to process
-     */
-    getRelevantIds() {
-      return [];
-    },
-    generateMeta(data) {
-      const {
-        timestamp,
-        user,
-      } = data;
-      const {
-        id_str: id,
-        screen_name: summary,
-      } = user;
-      // Event timestamp is expressed in seconds, whereas Javascript timestamps
-      // are expressed in milliseconds
-      const ts = timestamp * 1000;
-      return {
-        id,
-        summary,
-        ts,
-      };
-    },
-    _clearFollowersCache() {
-      this.setFollowersCache([]);
-    },
-    async _provisionFollowersCache() {
-      const screenName = this.getScreenName();
-      const followerIdsGen = this.twitter.scanFollowerIds(screenName);
-      const maxFollowerListSize = Math.max(this.getFollowersCacheSize(), 0);
-      const result = [];
-      for await (const id of followerIdsGen) {
-        if (maxFollowerListSize !== 0 && maxFollowerListSize === result.length) {
-          break;
-        }
-
-        result.push(id);
-      }
-
-      this.setFollowersCache(result);
-      return result;
-    },
-    getFollowersCache() {
-      return this.db.get("followers");
-    },
-    setFollowersCache(followers) {
-      const followersCacheSize = Math.max(this.getFollowersCacheSize(), 0);
-      const trimmedFollowers = followersCacheSize !== 0
-        ? followers.slice(0, followersCacheSize)
-        : followers;
-      this.db.set("followers", trimmedFollowers);
-      console.log(`
-        Updated followers cache: ${trimmedFollowers.length} records
-      `);
-    },
-    /**
-     * This generator method scans the list of Twitter followers until it finds
-     * the ID of a follower that was already processed.
-     *
-     * @param {string[]} processedFollowerIds a list of the ID's of the most
-     * recent Twitter followers processed by the event source
-     * @yields the ID of a new Twitter follower
-     */
-    async *scanNewFollowers(processedFollowerIds = []) {
-      const processeedFollowerIdsSet = new Set(processedFollowerIds);
-      const screenName = this.getScreenName();
-      const followerIdsGen = this.twitter.scanFollowerIds(screenName);
-      for await (const id of followerIdsGen) {
-        if (processeedFollowerIdsSet.has(id)) {
-          break;
-        }
-        yield id;
-      }
-    },
-    async getUnfollowers() {
-      const prevFollowers = this.getFollowersCache();
-      const currFollowers = await this._provisionFollowersCache();
-      const currFollowersSet = new Set(currFollowers);
-      return prevFollowers.filter((pf) => !currFollowersSet.has(pf));
-    },
-  },
-  async run(event) {
-    const { timestamp } = event;
-    const relevantIds = await this.getRelevantIds();
-    if (relevantIds.length <= 0) {
-      console.log(`
-        No changes in followers data for this event source to emit a new event
-      `);
-      return;
-    }
-
-    const users = await this.twitter.lookupUsers({
-      userIdArray: relevantIds,
-    });
-    users.forEach((user) => {
-      const data = {
-        timestamp,
-        user,
-      };
-      user.profile_url = `https://twitter.com/${user.screen_name}/`;
-      const meta = this.generateMeta(data);
-      this.$emit(user, meta);
-    });
-  },
-};

package/sources/common/tweets.mjs

@@ -1,155 +0,0 @@
-import twitter from "../../twitter.app.mjs";
-import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";
-
-export default {
-  props: {
-    db: "$.service.db",
-    twitter,
-    count: {
-      propDefinition: [
-        twitter,
-        "count",
-      ],
-    },
-    maxRequests: {
-      propDefinition: [
-        twitter,
-        "maxRequests",
-      ],
-    },
-    timer: {
-      label: "Polling interval",
-      description: "Pipedream will poll the Twitter API on this schedule",
-      type: "$.interface.timer",
-      default: {
-        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
-      },
-    },
-  },
-  methods: {
-    _compareByIdAsc({ id_str: a }, { id_str: b }) {
-      const A = BigInt(a);
-      const B = BigInt(b);
-      if (A < B) return -1;
-      if (A > B) return 1;
-      return 0;
-    },
-    sortTweets(tweets) {
-      return tweets
-        .sort(this._compareByIdAsc);
-    },
-    /**
-     * This function returns the Twitter screen name of the subject account
-     *
-     * @returns a string containing the relevant Twitter screen name
-     */
-    getScreenName() {
-      throw new Error("getScreenName is not implemented");
-    },
-    /**
-     * This function provides the list of options for the `tweetId` user prop.
-     * It is meant to be called by Pipedream during the setup of the user prop
-     * and not during normal operations of the event source.
-     *
-     * @param {object}  context the context object for the pagination of the
-     * prop options
-     * @param {object}  context.prevContext the context object of a previous
-     * call to this method
-     * @returns an object containing the list of Tweet ID options for the
-     * `tweetId` user prop and the context for pagination
-     */
-    async tweetIdOptions(context) {
-      const { prevContext = {} } = context;
-      const {
-        screenName = await this.getScreenName(),
-        sinceId = "1",
-      } = prevContext;
-
-      const userTimelineOpts = {
-        screenName,
-        sinceId,
-        count: 10,
-        trim_user: true,
-        exclude_replies: false,
-        include_rts: false,
-      };
-      const tweets = await this.twitter.getUserTimeline(userTimelineOpts);
-      if (tweets.length === 0) {
-        // There are no more tweets to go through
-        return {
-          options: null,
-          context: prevContext,
-        };
-      }
-
-      const sortedTweets = this.sortTweets(tweets);
-      const { id_str: lastId } = sortedTweets[sortedTweets.length - 1];
-      const options = sortedTweets.map(({
-        full_text: fullText,
-        id_str: idStr,
-      }) => ({
-        label: fullText,
-        value: idStr,
-      }));
-
-      return {
-        options,
-        context: {
-          screenName,
-          sinceId: lastId,
-        },
-      };
-    },
-    getSinceId() {
-      return this.db.get("sinceId") || "1";
-    },
-    setSinceId(sinceId = "1") {
-      this.db.set("sinceId", sinceId);
-    },
-    generateMeta(tweet) {
-      const {
-        created_at: createdAt,
-        full_text: fullText,
-        id_str: id,
-        text,
-      } = tweet;
-      const summary = fullText || text;
-      const ts = this.twitter.parseDate(createdAt);
-      return {
-        id,
-        summary,
-        ts,
-      };
-    },
-    /**
-     * The purpose of this function is to retrieve the relevant Tweets for the
-     * event source that implements it. For example, if the event source emits
-     * an event for each new Tweet of a specific user, the implementation of
-     * this function will perform the retrieval of such Tweets and return it as
-     * a list of [Tweet
-     * objects](https://developer.twitter.com/en/docs/twitter-api/v1/data-dictionary/object-model/tweet)
-     *
-     * @returns a list of Tweet objects for which to emit new events
-     */
-    retrieveTweets() {
-      throw new Error("retrieveTweets is not implemented");
-    },
-  },
-  async run() {
-    const tweets = await this.retrieveTweets();
-    if (tweets.length === 0) {
-      console.log("No new tweets available. Skipping...");
-      return;
-    }
-
-    const sortedTweets = this.sortTweets(tweets);
-    const { id_str: lastId } = sortedTweets[sortedTweets.length - 1];
-    this.setSinceId(lastId);
-
-    // Emit array of tweet objects
-    sortedTweets.forEach((tweet) => {
-      const meta = this.generateMeta(tweet);
-      this.$emit(tweet, meta);
-    });
-  },
-};