Site Development Notification and Feedback Thread

Please don’t pull a DeviantArt on us.

The new color themes sound cool ^u^  
The mobile redesign was much needed, I no longer use Derpi on mobile but it wasn’t great when I did.  

@TheGlitchedWolf  
I’ll create a subdomain like beta.derpibooru.org or something. It’ll be connected to the main database, so you’ll be able to use the site like normal using it.

Whatever you do, do not take Trixie Blue from us, or change its colors. And please please please do not destroy the desktop site for mobile users.
 
Is Markdown support enabled already in new comments/posts? A quick test indicates no, but I’d like a confirmation.

@JP  
Desktop will not be molested… too hard.  
Main accent color will remain the same, but its “mutations” (like slightly darker tone, etc) will definitely change.
 
Markdown is not enabled and won’t be for a few days/weeks at least.

On one hoof, one of the few Textile holdouts succumbs to the Markdown madness. Since it’s GH-MD, will we get headers and tables?
 
On the other hoof, I’m excited for the mobile improvements.

@PUBLIQclopAccountant  

 
I prefer BBCode. Much less accidental formatting and fiddling to escape it.

Are there gonna be normal line breaks, or markdown “line breaks”?  

@PUBLIQclopAccountant  
Tables and headers will be supported.
 
@Background Pony #5126  
Hardbreaks flag will be on. So, normal line breaks.

@Princess Celestia  
Can’t wait.

@Background Pony #5126  
TIL about treating MD like\  
a shell script and using\  
backslash to terminate\  
your lines.
 
That sure is less fussy (especially on mobile) than two spaces.
 
@Princess Celestia  
Now I’m genuinely excited for a move to MD, especially if proper bulleted lists are also planned to be incorporated. It’s not often that I find myself wanting them here, but I miss them on the rare occasions that I do.
 
@Background Pony #5126  
My dislike of BBCode is that it requires too much ceremony for common tasks, numbered lists are the #1 case. [list=1][*]At this point, why not just use HTML?[/list]

Markdown stuff is progressing faster than anticipated. It’ll probably be live fairly soon.
 
We deviate from GFM a bit and add our own extensions. In reality, our Markdown will feel a lot more like that on Discord (but with far more features) rather than the “pure” MD spec (such as using __text__ for underline, or not allowing “>text” to become a blockquote, rather requiring it to be “> text”)
 
I’ve also made it so you can resize external image embeds (the ones you currently would embed like !url.com/image.png!), by simply specifying size in alt text, like so:
 
 
Valid sizes are: tiny (64px), small (128px), medium (256px) and large (512px). Entering anything else will not constrain image size and will instead display full image.

As a detour from Markdown and The Redesign, we switched over external image proxying service from Camo to Go-Camo as the former is no longer maintained. The change is seamless and should not impact your experience, the only real difference is that previously external images had the format of “camo.derpicdn.net/<digest>/?url=http://external-url.here”, while now they’d have the format of “ext.derpicdn.net/<digest encoded as base64>/<target URL encoded as base64>”.
 
Old camo will continue to work for approximately a week before I’m going to shut it off, so if you have anything that depends on it - please change it.
 
P.S.  
oops, wrote this from my user account

@Luna  
Ooh. Interesting.

@Luna  
What would happen to FiMFiction images? It depends on it.  
Edit: nevermind

@Background Pony #5126  
Nothing? They use direct CDN URIs. The system we replaced was only for making external images linked here appear like site assets.

@Princess Celestia  
Ahh.

Code for Markdown change is finished and we’ll be deploying it shortly. We’ll put up a site notice once Markdown is live. The change will happen in several stages, first of which is simply translating current Textile into Markdown and then rendering the output using Markdown. You will be able to write Markdown directly, however keep in mind that things will be getting translated from Textile along the way too, so some Markdown may not function correctly just yet. It will function fully once we actually start the conversion that would write changes to the database.

@Princess Celestia  
Awesome.

@Luna  
The proxy might be having some kind of trouble. For example, in this comment, if I try to view the proxied URL, I have gotten at times a Cloudflare error, or the image only partially loads. If I quote that comment so I can see the original URL and visit it directly, it loads fine.
 
I’ve also had it happen that a proxied image won’t load the first time, but if I refresh or right-click->Load image, then it will.

@Princess Celestia  
If the new CSS styles make different color themes so easy, wouldn’t it be easy to implement a separate “classic” and “high contrast” theme as well ?

@Lead Pie  
True.

@Lead Pie  
I’ll leave those to userstyle makers :p
 
@Background Pony #1057  
The URL looks really weird. It might just be a very large file that doesn’t like being loaded from the proxy…

@Princess Celestia  
:/

@Luna
The response to request is missing header:

Content-Disposition: inline; filename="filename.jpg"

Because of this, browser’s “Save image as…” dialog uses the wrong filename.
Example:
original url: https://dl.dropboxusercontent.com/s/x3z01y7neuwxe03/g5_new_mcs_upscaled.png?dl=0
proxy url: https://ext.derpicdn.net/4ml3yy_jXU1rFMhHaq34tku4rCA/aHR0cHM6Ly9kbC5kcm9wYm94dXNlcmNvbnRlbnQuY29tL3MveDN6MDF5N25ldXd4ZTAzL2c1X25ld19tY3NfdXBzY2FsZWQucG5nP2RsPTA
Browser saves image as "aHR0cHM6Ly9kbC5kcm9wYm94dXNlcmNvbnRlbnQuY29tL3MveDN6MDF5N25ldXd4ZTAzL2c1X25ld19tY3NfdXBzY2FsZWQucG5nP2RsPTA.png" instead of "g5_new_mcs_upscaled.png".