Philomena open beta / breaking API changes

@Angius  

Oh, that kind of paradigm. I thought you were talking about MVC vs MVVC etc. It might surprise you then to hear that we were basically writing Ruby in almost functional style anyway. Most of the method calls in our code (the stuff that does “actual work” as opposed to just database interaction) are to Enumerable and to ActiveSupport::CoreExt. There are vanishingly few class structures we have, and only one or two actually use inheritance or true polymorphism, because it basically isn’t needed. (There’s also some broken STI that I aim to fix… uh, at some point, but that doesn’t really count.)  

If you read my post on why I decided to do this rewrite, it sets out my reasoning. Basically the ORM structure provided by ActiveRecord ended up slowing us down considerably after schema changes where we should have been getting faster, and I had at that point just had enough of it. The reason for this slowing down was due to Ruby object creation overhead. Neither Python nor Ruby are particularly well-known for being fast at object creation, so I can’t see Django being much better here. C# (or even F#, in fact) could potentially be viable, for sure. But Ecto stood out to me because of its fantastic query API support for PostgreSQL, which is the database we use.
 
I’ve also had Elixir on my mind as a Ruby replacement for a very long time, on the order of several years, as I had more or less anticipated this becoming a problem after the Postgres migration. Discussions I had with Rails core developers years ago in IRC had significant sway in my early opinion of the Phoenix framework, and there was a lot of excitement surrounding the framework (Jose Valim even occasionally showed up in those channels discussing it).
 
Earlier this year, someone paid me for and I wrote a “scratch project” (a video hosting site) to get used to Elixir and Phoenix, and by late July I felt that I had the experience with the language and framework that I needed to pull this off. I also of course have gained a lot of experience over the past few months as it takes quite a lot to run a modern imageboard.
 
To be perfectly honest, I did not even consider ASP.NET as a replacement framework. It would certainly work, though. My personal objection is that it’s not really “built” for PostgreSQL the way Ecto clearly is. In addition, ASP is what I was doing at my job over the summer, and I was not having a great time picking through what had been left for me, though I admit that was mostly to do with the code being untouched for about ten years.

https://philomena.derpibooru.org/tags/what+about+discord%3F
 
Try to open second page

is there any huge changes coming/planned or is it just a move?

 
Ow ouchie ouch, my css ruleset

@GenericArchangel  
And I, one of many great Overlords from that majestic state of border hoppers and shitty drivers, also welcome thee, Our new Subjects.

@Mister E.  
Nothing apart from VERY minor cosmetic changes. This is just a move.
 
All of the larger stuff will be implemented post-move, we have a bunch of things on our todo list.

@byte[]  
You got me interested in Phoenix, as Postgre is also my database of choice. I’ll have to start some small project with it and see how’s the experience compared to ASP.NET Core.

@Stellar Dust  

 
@DBot  

fixed

Result numbering at the bottom of search pages is off. The first page says it shows results 1-50 of X correctly, but the second says it’s showing 49-100 instead of 51-100. There are 50 images on the second page, and no images repeated from page 1. Similarly, page 3 says 99-150, and so on.

@T12  
fixed

“Most Commented-on Images” stops searching by “most commented” when you type anything into the search bar.

@Algebroot  
fixed

when Chrome gives the dropdown of previously typed things in the search bar, it turns it a …
 
you know what, I’ll just link some images  

 

@Rainboom Dash  
I have no idea how to fix this

@byte[]  
huh… but it’s fixed on the original Derpibooru just not the new Philomena one  
Oh well… must be different code that makes it harder

dunno, if anybody asked, but I miss informative page titles on Philomena

@byte[]  
You can add this to the CSS
 
@input:-webkit-autofill,  
input:-webkit-autofill:hover,  
input:-webkit-autofill:focus,  
textarea:-webkit-autofill,  
textarea:-webkit-autofill:hover,  
textarea:-webkit-autofill:focus,  
select:-webkit-autofill,  
select:-webkit-autofill:hover,  
select:-webkit-autofill:focus {  
-webkit-text-fill-color: #ffffff;  
-webkit-box-shadow: 0 0 0px 1000px #62a7d9 inset;  
border: none;  
}@
 
to explicitly overwrite the autofill style and, in this case, make it look exactly like the Default header input. (Obviously adjust colors for other themes.)
 
I just adapted it from https://css-tricks.com/snippets/css/change-autocomplete-styles-webkit-browsers/, no idea if there’s a better solution.

@Yoshimon1  
it baffles me that autoprefixer fails to do that automatically…

@Luna  
Eh, makes sense to me, the default usually is ok. Plus, you don’t usually want to change the style of every single autofill on the entire site.
 
That said, I just realized the code I posted also changes the autofill of the username and password boxes at sign in, the tags search box and probably lots of other boxes, too. If you’re changing the style, you most likely should use something more specific than input, textarea and select…

-Missing “I’m feeling poni” button
 
-Names with quotation marks can’t be correctly linked in comments, the link appears as raw text
 
-Derpibooru’s images can’t be hidden with ||spoiler /spoiler ||, it works normally for images from other sources

@byte[]  
Spanish:  
Tengo una duda, es como derpiburu?, Se podrá usar igualmente para la carga y descarga de archivos jpg,svg, Photoshop, etc etc?  
Y una más, se acabará derpiburu?

@catlion3  
Es exactamente derpibooru; es un cambio de como funcciona bajo el capote, pero para usuarios todo deberia seguir igual… pero mas rapido.
 
Y no hay ningun plan para que derpibooru cierre mientras siga existiendo el internet.

data-theme="default" at the body tag even if the theme is not “Default”.

Status: FREAKING FIXED ON PHILOMENA!.  
Scope: Cosmetic issue in how strike is parsed in posts and comments.  
Summary: Hyphens when used to create arrows (ex: -> as happens in the aliasing threads) results in strike if there is another hyphen later in the string from the attempted arrow to the second hyphen.
 
Use Case: In the artist aliasing thread the boilerplate for requesting aliases is X -> Y. We could change, but this has been the standard for long enough that it is undesirable to change.
 
Example raw text:  

Expected result (from Derpi On Rails):  

Instead Philomena renders it as:  

 
This is cosmetic, and doesn’t prevent any work on aliasing, but using the X -> Y format is the standard for the thread so it would be preferable to not change.

Status: FIXED  
Scope: Moderation Only issue  
Summary: Claiming a report opens the report.
 
Use Case: We often have to claim several reports at one time, especially when one moderator is claiming artist takedowns or spam reports or multiple reports of a single comment or image. On BooruOnRails marking a range of reports “In Progress” all happens in one screen and can be done very quickly.
 
Expected behavior: Claiming a report on the report queue screen adds it to that moderator’s “In Progress” queue and the user is returned to the report queue screen.
 
Instead: Claiming a report opens the report itself so you have to go back to the report queue and reload it to see the change and to claim another report.