chore: update README

Author: WarningImHack3r

.env.example

@@ -1 +1,3 @@
-PUBLIC_GITHUB_TOKEN=your_github_token
+KV_REST_API_TOKEN=your_kv_token
+KV_REST_API_URL="https://your.api/url"
+GITHUB_TOKEN=your_github_token

README.md

@@ -1,6 +1,6 @@
 # svelte-changelog
 
-[svelte-changelog.vercel.app](https://svelte-changelog.vercel.app/)
+[svelte-changelog.dev](https://svelte-changelog.dev)
 
 Made with SvelteKit, TailwindCSS & shadcn-svelte.
 
@@ -13,37 +13,18 @@ Made with SvelteKit, TailwindCSS & shadcn-svelte.
 - Dynamically computed badges to indicate whether a package is the Latest, a Major version, a Prerelease, or a Maintenance version
 - Hover popups at multiple places across the site
 - "What's new" banner to keep users updated about the latest changes to the website
-- Authenticate with GitHub to bypass rate limits and get access to more features
-- Optional use of a GitHub token to avoid rate limiting in dev mode in a `.env` file (see `.env.example`)
+- ...and more!
 
 ## How does it work?
 
-The site makes requests to the GitHub API on the client side to get the latest releases for all the packages.
-As such, the data is fresh from GitHub every time you refresh the page.
+The site makes requests to the GitHub API on the server side to get the latest releases for all the packages.
+It smartly caches the data, frequently invalidating it to always be up to date while avoiding hitting GitHub as
+much as possible.
 
 Some computations are made to generate the badges, but everything else is a simple cosmetic
 wrapper around GitHub releases.
 **No data alteration is performed by the site other than for styling and rendering purposes**.
 
-### What is that "Log in with GitHub" button?
-
-With the growing amount of features and supported packages, the site went from requesting the GitHub API
-very few times to request it a lot.  
-As such, the rate limit of the GitHub API was quickly reached, and the site became hard to browse.
-
-To solve this issue, I [initially implemented](https://github.com/WarningImHack3r/svelte-changelog/commit/f28218cbf3d57d509e771520e8c02a610dab4b95) a way to input a GitHub token in the website settings.
-This became [the next week](https://github.com/WarningImHack3r/svelte-changelog/pull/27) a full-fledged authentication system with GitHub OAuth, which is what you see today.
-
-**By logging in with GitHub, you can browse the site (almost) without any rate limit issues**.
-You will also get access to more features, such as the ability to see the details of a pull request
-or issue directly on the site.
-
-The site does not store any data about you. The only thing the login system does is store the token given
-by the GitHub authentication process in the browser's local storage to use it for the GitHub API requests.
-
-Logging in is entirely optional but highly recommended. You can remove the token from the website at any time
-by clicking the "Log out" button in your avatar dropdown.
-
 ## Missing a package?
 
 If you think I missed a package, you can either open an issue or directly contribute.