summaryrefslogtreecommitdiffstats
path: root/assets/js/app.js.bvr (follow)
Commit message (Collapse)AuthorAgeFilesLines
* def.lang=sl&update ne zbriše lang,theme,errorrepsijanec2020-10-041-1/+1
|
* removed jitsi! ):sijanec2020-09-271-0/+1
|
* added tracking jssijanec2020-09-231-1/+3
|
* so users don't have to stay on a single page for 300 seconds for an updatesijanec2020-06-091-10/+16
|
* forgot a semi-crucial thingysijanec2020-06-081-2/+4
|
* killing the cache ... good to gosijanec2020-06-081-1/+1
|
* added some protection, proby can merge nowsijanec2020-06-081-15/+19
|
* DNM+in case you haven't read the prev. commitsijanec2020-06-081-7/+14
|
* added update mechanism, DO NOT MERGE b4 seeing commit notes!sijanec2020-06-081-45/+70
| | | | | | | | | | | | | | | | | this "update mechanism" only deletes old caches. old means caches that are caches with names other than the name in cache_name.txt. It is important not to cache cache_name.txt and always serve it with HTTP headers that allow no HTTP level caching. Update checking occurs every 300 seconds and if a new cache is released and sw.js is not reinstalled, this timer will clear the cache. the old update method did not work since it relied on sw being reloaded often, which is not the case on iPhone devices, where Safari runs almost the whole uptime of the phone and it's not common for people to shut down their precious little iPhones. it worked on android as android is known for killing apps and chrome is no exception.
* i should check code before pushingsijanec2020-05-201-1/+1
|
* syntax errro fixsijanec2020-05-201-1/+1
|
* report usernames toosijanec2020-05-201-1/+5
|
* DO_NOT_MERGE; still testing error reporting optoutsijanec2020-05-201-5/+15
|
* made error reporting asyncsijanec2020-05-201-1/+1
|
* fix for onunhandledrejectionsijanec2020-05-201-1/+4
|
* err reportingsijanec2020-05-201-0/+63