So, looks like the 16.02 site upgrade is mostly going to be a features upgrade rather than a bugfix upgrade, though there's some of that as well. There's one thing going in that there's an outside chance may annoy some people though: the new mobile layout. To be very clear on this, the mobile layout will be served to anyone with a horizontal screen (not browser window) resolution of 800 pixels or less. The only way you'll see it on your desktop is if you're still running 800x600 or lower resolution, in which case you really should get with the whole 21st century technology thing.
We're going to be doing the site upgrade the first weekend of February but if you want to give it a look early head over to https://dev.soylentnews.org/ and have a look around. Bear in mind we ain't foisting beta code on you lot with this, we're foisting pre-alpha code that took all of maybe half an hour to do up on you. This is not what the finished product will look like, it's just something to make life easier on mobile users while we write up something that doesn't suck. If it sucks too hard and you all bitch that you want the old layout back though, it's a matter of minutes to fix and revert until we have something worth calling a proper mobile interface.
Let me know what you think here.
(Score: 1) by DonkeyChan on Wednesday February 03 2016, @07:18PM
Hmmm, yes.
How about turning it into a ?= that can be statically bookmarked?
(Score: 2) by The Mighty Buzzard on Thursday February 04 2016, @02:58AM
Doable but it would need to persist into all the local links on the page or those pages would default to the mobile layout. Lot of extra work there. At this point I'm thinking it might be easier to just set up another vhost and have it accessed via m.soylentnews.org or some such.
My rights don't end where your fear begins.
(Score: 2) by paulej72 on Thursday February 04 2016, @11:47PM
I am thinking we use a pref to allow people to load the mobile css. Still have it only work for smaller screens so they can use both small and large screens and get different results. This way if people want a normal screen they don't have to activate it.
Team Leader for SN Development
(Score: 1) by DonkeyChan on Friday February 05 2016, @09:41PM
Haha, I did not think through to that end.
It would have to persist hu?
So you're basically saying that once it's triggered that the viewer will start being served from a different vhost? Or that m. as a whole will be from the get go?
(Score: 2) by The Mighty Buzzard on Saturday February 06 2016, @01:23AM
It's an idea. Of course it would cost us for another ssl cert so another way of doing it would be more ideal.
My rights don't end where your fear begins.
(Score: 1) by DonkeyChan on Saturday February 06 2016, @12:21PM
I'm not very proficient at a lot of things, but I'd like to submit this for consideration.
Turning the override link into a form action (posting a hidden field) then using some code behind to turn every link into a form action that maintains a hidden field when that hidden field is set in the POST variables.
The code behind would need to either encapsulate blocks of hrefs within a form action, which may (would likely) break things or encapsulate every href within one.
I've not looked at slashcode in almost 10 years so forgive any oversights I've made.
(Score: 2) by JNCF on Friday April 29 2016, @10:43PM
Of course it would cost us for another ssl cert so another way of doing it would be more ideal.
Is there a reason you can't use free (as in beer) certs from letsencrypt?
(Score: 2) by The Mighty Buzzard on Saturday April 30 2016, @10:21AM
Actually, we are on dev at the moment. But that's dev. We do our best not to try new things out on production boxes.
My rights don't end where your fear begins.