Skip to content

Commit

Permalink
typos
Browse files Browse the repository at this point in the history
  • Loading branch information
shrivaths16 committed Dec 14, 2023
1 parent 304e80e commit 7a74bfd
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -109,4 +109,4 @@ Pushing to main is blocked unless all of the above steps pass and the code is ap
# Additional Documentation

- [Testing](admin/Testing.md)
- [Trending Specification][specs/Trending posts specification.md]
- [Trending Specification](specs/Trending%20posts%20specification.md)
4 changes: 2 additions & 2 deletions specs/Trending posts specification.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
# Trending post specification

> To get the trending posts from the mastodon instances, we first perform an API call to `https://mastodon.social/api/v1/` to get the trending tags in the mastodon instance. You could replace the URL with the URL of the preferred instance. Once the trending tags are fetched, a line of API calls are made to `https://mastodon.social/api/v1/timelines/tag/:` with each of the tags appended to the URL to get the trending posts for each of the tags. Initally, this was done serially which caused the page to load really slow. To overcome this, we parellized API calls to reduce the load time to one-fourth.
- To get the trending posts from the mastodon instances, we first perform an API call to `https://mastodon.social/api/v1/` to get the trending tags in the mastodon instance. You could replace the URL with the URL of the preferred instance. Once the trending tags are fetched, a line of API calls are made to `https://mastodon.social/api/v1/timelines/tag/:` with each of the tags appended to the URL to get the trending posts for each of the tags. Initally, this was done serially which caused the page to load really slow. To overcome this, we parellized API calls to reduce the load time to one-fourth.

> For getting the trending posts from lemmy, it is much simpler as there is only one API call to `https://lemmy.ml/api/v3/post/list?sort=Hot` to get the trending posts from. The URL for the API call could be changed accordingly to get the trending posts from the required Lemmy instance.
- For getting the trending posts from lemmy, it is much simpler as there is only one API call to `https://lemmy.ml/api/v3/post/list?sort=Hot` to get the trending posts from. The URL for the API call could be changed accordingly to get the trending posts from the required Lemmy instance.

0 comments on commit 7a74bfd

Please sign in to comment.