Installer Steam
se connecter
|
langue
简体中文 (chinois simplifié)
繁體中文 (chinois traditionnel)
日本語 (japonais)
한국어 (coréen)
ไทย (thaï)
Български (bulgare)
Čeština (tchèque)
Dansk (danois)
Deutsch (allemand)
English (anglais)
Español - España (espagnol castillan)
Español - Latinoamérica (espagnol d'Amérique latine)
Ελληνικά (grec)
Italiano (italien)
Bahasa Indonesia (indonésien)
Magyar (hongrois)
Nederlands (néerlandais)
Norsk (norvégien)
Polski (polonais)
Português (portugais du Portugal)
Português - Brasil (portugais du Brésil)
Română (roumain)
Русский (russe)
Suomi (finnois)
Svenska (suédois)
Türkçe (turc)
Tiếng Việt (vietnamien)
Українська (ukrainien)
Signaler un problème de traduction

It was all a lot of manual work that was required.
Then the server hosting which was frankly at the time not implemented in a way that took properly care of resources available and would just be a constant CPU hog. (I believe the Laravel backend was running in debug mode rather than release mode, the redis server was exposed publicly and was somehow had gotten malware)
Sure we can re-implement this today with much better technologies and servers (causing less CPU usage as well as horizontal scaling), however there's still the issue of all the manual labour of verifying as well as having server hosters to actively use it.