> How is this related to relays?
>
> Relays can be used to get a more complete view of what is going on in the larger
> Fediverse. As such there are some similarities to this proposal.
>
> From an instance operator’s point of view the biggest difference is that using a relay
> comes with a higher cost. The instance needs to ingest and index everything the relay
> sends which takes up processing power and storage. A discovery provider will do that
> work for one or more instances.
>
> Implementation-wise we expect to see some similarities with how relays work, at least
> for real-time data. But discovery providers should be able to index historic data as
> well. So ingesting real-time data from instances is only part of the story.
> Querying instances for historic data is not currently something that relays do.
> Why did you choose sveltekit-i18n instead of another svelte i18n lib?
Mainly for the following argument:
- It is built for SvelteKit and has good SSR support.
And also, the following:
- The translations are loaded for visited pages only. (and only once!)
- As of v2.4.2, the size of the sveltekit-i18n package is 14 kB in the minified form and 4.6 kB in minified + gzipped form
> In my understanding, Nim at the moment is really a transpiled language, instead of compiled. Transpiled to C, then tooling uses clang or gcc to do compilation from C to target platforms.
If I understood correctly, like the Vala language: https://vala.dev/ (Note: Vala is strongly integrated with GObject).