-
• #9227
Also... get a better internet connection. It is 2017, this page loads in a few seconds on my machine.
-
• #9228
4g only out here in the sticks.
-
• #9229
Hah.
You were one of the ones complaining whenever I did lots of things to optimise for mobiles on bad connections. Things like only loading the images that were viewable in the window... that has a side-effect of making the page a bit jumpy and ultimately the complaints led me to go, "Fuck it... I'll let them have it all". Which is why the current stuff is so simple and just attempts to load everything.
Also, you were one of the ones asking for more posts per page as you moaned about too much pagination and clicking. If you recall I had launched Microcosm with only 10 posts per page exactly because I wanted to strike this balance between heavy pages and fast loading. Complaints led me to shift the default to 25.
Oh well, it will be months before I can surface it as an option now.
-
• #9230
-
• #9231
I'll stick to the reposts...
-
• #9232
-
• #9233
-
• #9234
-
• #9235
Just fill half of each page with complaints about it opening slowly, then there'll be less room for Gifs, and it will open faster :D
-
• #9236
Fuck him.
-
• #9237
Fuck him
This.
-
• #9238
-
• #9239
although maybe that job should be given to someone without a gif as their avatar.
-
• #9240
Snot the download speed that fux it for me, it's the processing power of my phone.
I just save the jif thread for those rare desktop moments.
-
• #9241
^ This. This thread was a lot easier to load before gifs got massive. Maybe the solution is specifying a max embeddable image size?
Edit: that said, works great on desktop, so probably the solution is doing nothing
-
• #9242
-
• #9243
-
• #9244
-
• #9245
That's some seriously terrible cornering on the motorbikes. Not enough leaning and mid corner breaking is the way to bin it into a tree.
-
• #9246
Ktm driver seems to find it difficult to stay in lane as well
-
• #9247
-
• #9248
-
• #9249
-
• #9250
There is no per-conversation setting for this, and whilst the underlying APIs support it the front-end does not.
When I approach completion of the front-end I'll include it as an option.