>I don't like the new design, i think it's ASS (ﾟ血ﾟ#)
I SHALL HAS U KNOW that Sakomoto is teh original Heyuri design as used on our original Sakomoto software, which was (previously very poorly) ported over to our later software! "Heyuri Classic" is actually the newer one! and the latter totally sucked ballz (until now) cuz it used to use a retarded site-hosted MacOS font that had been converted to TTF and generally looked like shit despite being a totally generic sans-serif font - now it at least has a sensible font-family that uses your system's own fonts!

>Using the big reply box at the top of the page was one of those Heyuri-distinctive things that only now that it's gone i realize is part of our identity
Just disable quick reply in the settings. BTW, this is a feature we had from the start, and it was only disabled because "somebody" b0rk'd it a few years ago and never fixed it

>let's resurrect the netiquette page
Let's not... but we should probably add moar stuff to teh FAQ

>>68672
Sakomoto FTW

heyuri is heyuri bcs of its content. i think it looks sharper now and its way more functional on phone too

>its way more functional on phone too
Thats a good thing!?

>>68674
I actually find the older Heyuri design better on smartphones somehow

There's a lot of room for improvement with the quick reply box, but JS is hard to make compatible with everything else.

>we should probably add moar stuff to teh FAQ
The FAQ is quite outdated (I didn't rly touch since I became the admin), there's a lot to change there... It's a work that's being stalled for years now

>I actually find the older Heyuri design better on smartphones somehow
Old design was better at emulating the desktop experience but that's not what u expect by default (and you can always request desktop view). Stuff like unwanted margins are removed now
But feel free to share what exactly you think used to be better on smartphones b4 the change

When overhauling teh HTML/CSS, I was primarily testing on PC, but also frequently testing on phone and tablet along the way (and occasionally other things liek terminal browsers, Raspberry Pi, and Windows XP too - I would have tested on TV as well if I had access to one that's less than 10 years old!). The same cannot be said for anyone who previously touched kokonotsuba - sans things that were changed at my suggestion

I'll be the first to admit it's not yet perfect (10"+ tablet in particular is still kinda awkward), but I strongly believe that a well-designed site should look good on any display without ghey compromises or an entirely different UI. A site that works poorly at various resolutions just has shitty HTML/CSS!

Making a site worse/unusable for mobile displays (either through neglect or active countermeasures) is just plain dumb - it doesn't keep out crappy users or bad actors, nor does it ever truly prevent mobile users from accessing the site (desktop view and user-agent spoofing exist). In the worst cases, it backfires entirely and prevents users with lo-res PC monitors from accessing the site (*cough* mootxico *cough)

All it really serves to do is limit the number of users frequenting a site, which is antithetical to Heyuri's various goals and purposes:
1. be the place to be
2. attract hawt girls
3. TOTAL INTERNET DOMINATION!!!1

I hate teh new design. It looks like shit in internet explorer and trinity konqueror and when I click on an image it opens a new tab instead of making it bigger on the page which I find really annoying

there is no "new design" besides Sakomoto being the default theme
Everything looks fine on IE (besides few minor CSS here and there, but it was a necessary change) and from my testing, the img.js was never properly supported on IE anyways.

Opening files in a new tab is how Futaba does it too anyways, and if you use those browsers you're probably capable of writing your own userscript/style if u really want to

I don't turn on javascript so everything looks about the same

As far as I recall, the vast majority of kokonotsuba's JS never worked in any version of IE to begin with - even pre-overhaul. That includes the ability to expand images when clicking thumbnails, which cannot reasonably be done with HTML/CSS alone (not to mention that the settings window to enable/disable the feature never worked in IE either...)

A large part of teh HTML overhaul was making koko HTML5-compliant rather than the mixture of various older standards and totally invalid crap it previously was - and without relying on extremely new features or breaking compatibility just for the sake of it. Styling done with HTML tags/deprecated attributes was largely replaced with IDs/classes + CSS, so if ur browser happens to not support certain CSS features, things will look less "styled" than they used to. The essential functionality for browsing and posting should still totally work however (or at least as well as it previously did)

Another aspect of teh overhaul was utilizing CSS variables, which we decided were worth adopting despite being a "newer" feature (and by that I mean it became widely available 10-ish years ago). For compatibility with older browsers (IE9+, Firefox 6+), a script called css-vars-ponyfill was added which converts CSS variables to "regular" CSS - sadly it does not work with alternative styles as far as I could tell

The oldest browser I routinely tested teh overhaul with was SeaMonkey 2.49.5 for Windows XP, released in 2019 - I believe it's roughly equivalent to Firefox 52.9.0 ESR from 2018. 99.9% of features and styling works as expected on it except for a couple of extremely minor things (from what I remember: the SVG window close/minimize button icons are a little visually b0rked but still functional, and the "gap" property for flexboxes is not supported so a couple of things appear to be unspaced). If you run Supermium on XP instead, it's flawless