Glowfic platform

[pedromvilar]

Suggestion: maturity filters for the threads, like on dreamwidth? Unless NSFW RPs are completely forbidden there :P

[rockeye_stonetoe]

I've seen one or two marked [Lewd] on various sites. And they were. Most don't cross that line.

[Throne3d]

But perhaps for ease-of-scraping purposes, if I'm going to scrape the site later, either make a "Yes, I'm over 18" button into a link, so I can follow it without having to have special cookies, or just have it as a really obvious message before the content, without requiring a confirmation to view it? As it is, I really can't think of a nice way to handle how Dreamwidth does it, since it requires cookies when loading the page, and I don't know what it needs in the cookie to let you see the pages, and I can't really work it out from the buttons.

[Marri]

Updates:

• Fixed a bug with the gallery JSON, so now when you are editing a character and change galleries, it'll swap out the images without requiring a page reload
• I now sanitize the html tags I let you use in your posts. I'll post a list on the actual website soon but for now it's using the defaults ["a", "abbr", "acronym", "address", "b", "big", "blockquote", "br", "cite", "code", "dd", "del", "dfn", "div", "dl", "dt", "em", "h1", "h2", "h3", "h4", "h5", "h6", "hr", "i", "img", "ins", "kbd", "li", "ol", "p", "pre", "samp", "small", "span", "strong", "sub", "sup", "tt", "ul", "var"]
• There's actually a link to that fun "tags you owe" page now
• Inbox/outbox page CSS tweaking, it felt overpadded

[DanielH]

I would like to report a bug with the sanitization. When somebody forgets to close a tag, you leave the tag unclosed and (maybe depending on browser; I’ve only checked in Chrome 44.0 64-bit Linux) messing up the rest of the page.

For example, this post has the following HTML:

Code: Select all

<i>I would say it's average but I'm really not sure what to compare it to. I have an audi</i> 
<br>She pauses, crosses out "an audi" and writes 
<br><i>a soundy learning style, so the lectures play to my strengths. 
<br>At one point I went to a school that had the same things but it was all textbooks and slideshows so it didn't work for me. 
<br>I think it's all about how it's taught. 
<br>
<br>What learning style do you have? If it's not soundy I could help, I know how to present things right.

In addition to other problems¹, this does not close the second <i> tag. All the later posts on the page are thus put in <i> tags themselves. In order to keep reading this I need to switch to a paginated view, use Chrome’s tools to edit the received HTML, or read the entire thread in italics.

Also, a feature request: for continuities other than the sandboxes, could you make an ability to go to the next/previous thread? One thing I don’t like about the current Dreamwidth format is that I always need to go back to the ToC to continue reading.

¹ <br><br> is not a good substitute for <p> is probably the only one that’s potentially relevant to the glowfic site. Not at all relevant is that the “different learning styles” theory doesn’t have much evidence for the way it’s commonly interpreted.

[Marri]

I put in a fix for unclosed tags but it wasn't retroactive; I can edit that one by hand when I get home. There's a related bug that's stripping start and end whitespace.

The reason it uses br instead of p is that I convert \n to br manually.

I can definitely add next and previous buttons to my feature list :)

[DanielH]

I think Dreamwidth has the same conversion. I’ve seen better conversions, but I don’t remember if they were open source and it isn’t as simple as replacing \n\n with <p>. As a first idea if I wanted a better one I would special-case two linefeeds. I think that actually works out correctly in practice, but I’m not sure.

[DanielH]

I’m not sure how feasible this is, and I don’t know how much it would help anything, but you could improve the caching. At the moment, the web server tells the browser in at least two different ways that it does not support caching the thread pages. It would be both cheaper to serve and faster for people with slow connections if the server managed to know if the page had actually changed or not.

[Marri]

HmmmMMMmmm. Rails has a bunch of built in caching support, but I don't think it works on pages that need to know if you're logged in or not; I could do cache fragments, but probably not the whole page. I'll look into flat text versions of the page or something, though.

[DanielH]

Should probably be pretty low on the priority list; unless you're running low on bandwidth there are probably more important issues. Especially if you get push notifications working, which would mean we wouldn't need to refresh to check for new content as much.

Then again, supporting last modified date and If-Not-Modified might be relatively easy for logged-out users. You already keep track of post modification dates.