[Return]

Report a post

Preview
Oho. Right. I think it's because I put some html in. Even though there were no links, it's still link-like code, which must have upset it.
Next changereq then - add html filtering in that does more than simply prohibiting posts that include it or similar looking strings?
*edits post* ok that should fix it.
> spoiler: it didn't

*edits again* ... ok, how about now?

>>5709
Ah! Thanks. Actually quite slick. Thing is, using a widescreen machine, and a screen that couldn't really be described as the world's highest contrast, plus rarely if ever using the regular scrollbar now we're in an age where cursor keys, pgup/pgdn, home/end, and of course the mousewheel (& its emulated touchpad flavour), and with most posts being left-aligned to such a degree that they rarely extend much beyond halfway across (even with a lowly 1280 pixel resolution!)... I never ever looked over there, and it didn't stand out enough for me to notice it.

I know it's there *now* of course, but still, any way to have an option to move it to top-left or something like that? Maybe detect screen width and automatically put it halfway up the left hand edge with an extra couple dozen pixels of left border before the images and text posts are drawn on any screen where text doesn't normally extend all the way to the right-hand scrollbar? It'd take up the same amount of screen space overall, after all.

Also, that's fine on a desktop display like the one I'm currently using, but I'll have to reserve full judgement until I can test on mobile again. Fancy floaty features like that have a nasty habit of either not working properly after taking the leap to handheld, or simply don't work at all. The old links as described were plain HTML anchor bookmarks, ie [[data expunged]]. Absolute HTML universal-compatibility 101 grade, any device that can't parse them needs to be thrown in the sea ;)
[original angle brackets replaced with square brackets to try and evade the overzealous bot-hunting code]
[[and now redacted entirely... you can just look up what i mean if you don't know the form already, after all]]

And then there's the matter of how big the shortcut buttons will be on a dinky touchscreen and if they're oversensitive so get triggered by normal scrolling etc...

Anyway, without having tested it yet, that's just conjecture, it may work absolutely 100% fine, so don't take it as a criticism... (yet!)



>>5711
Totally unacceptable, isn't it. Some people have no respect for the classics, or how us weirdos still can't deal with moving into the 21st century. There oughta be a law.

It is pretty cool, though.

Also...
> Is trying to learn n00b-level PHP/MySQL right now

> Reads >>5568

> Fuck.

> That sounds really complicated, have I got the time and mental capacity to deal with all that stuff? I'm not exactly a tech novice but I've not heard of more than 50% of that, and probably 40% of the rest I've heard of but haven't had any direct contact with, or even actually know *what* it is. Presumably the insight would gradually accumulate over time, but if that's the kind of guru level knowledge and analysis exercised just for a niche back-of-the-woods imageboard, what kind of insane wizardry is expected for professional use?

> ... heck of an insight and a resource though

> *select* *copy* *start>notepad* *paste* *find-replace to edit out the bits that point directly to here*

> *fukken saved*


Damn, Enclaved. That sounds like a fuckload of work. I feel like a bit of a dick going "wah, where's the top/bottom links?" now. (The "wtf happened?!" bit was supposed to be a comedic expression of it actually being new and swish, however) ... Thanks for being motivated enough to put in the effort to fix/rewrite it. It looked like just some kind of CSS theme pack initially but I have to say the site seems to be running somewhat quicker and smoother than its previous somewhat clunky self, that sometimes gave the impression that it was running on a C64, on the moon. Probably the strain of trying to serve 10 different people browsing at once, through the fug of the original spaghetti code.

*double thumbs up*
Post number No.5762
Board Discussion
Optional. Describe what's wrong with it.