Posts

The parser is stupid and requires whitespace immediately outside the control symbols..

When I try to write a comment/post, parsing for bold or italics is nullified when a quotation or exclamation mark is placed next to the syntax. For example:
 
Strike this! “bold “italic “This should be underlined.
 
That above is not using anything to prevent parsing; As of now, it simply doesn’t happen when I use quotation or exclamation marks there. However, it does parse correctly when the syntax is not placed near quotation marks:
 
Striking this ! “the bold text “the italic text “ This is underlined.

@Bytewave  
It was also misspelled. Thanks for the catch.

@byte[]  
I did notice one thing just now, actually: the href for image-response for search/reverse is missing the #. Minor pedant, but still.

@byte[]  
Awesome! Glad to see something more substantial than 2 routes with ~3 documented query parameters each. :P
 
Really though, it’s good to see the API getting more love.

@Background Pony #EE55  
Commenting resets the current image scope. It’s certainly not intended, and you’re right, the old site didn’t do that (because it posted comments using a fetch request, instead of using default browser form submission).

Not sure if this is the right place, but here’s what just happened:  
I searched for a specific term (e.g. “apples”), clicked on one of the results, and navigated all the “apples”-related images using the “previous” button. Then, I commented on one image in the results. Next, after the comment was submitted, I try to navigate the search results using “previous” or “next”. However, this time, the button directs me to the previous/next image by the number, and forgets that I entered the commented image through searching the term “apples”.  
Not sure if this is new for Philomena. The old version didn’t have the same behavior.

@Joey  
New

@byte[]  
Is /api/v1 the old API or the new API?

API docs have been updated
 
Yes we’ll probably be adding more stuff

@Jarkes  
Userstyles are your own responsibility. If it breaks and you made it, you fix it.

@Joey  
Oh! Didn’t realize that at first as well, I’ll try that.
 
@Boxless  
Same here. Gonna keep this thread on the watch if that happens again.

@Joey  
Mm. I’ll keep you lot posted if it happens again.

@Boxless  
We’re using a new authentication library, so all of the cookies set by the old codebase no longer work. That’s why everyone was logged out Friday morning. Stale cookies can cause issues.
 
Out of everyone I’ve told to clear their cookies, probably about 20% have said that worked, 10% said it didn’t, and 70% stopped responding (which in the IT world normallyed means it worked and they don’t want to talk to you anymore)

@Damaged  
Generally doesn’t come to mind immediately.

@Boxless  
Ah, okay. It’s just that has actually been solving the problem for a lot of people (and is the reason Joey made the image).
 
Edit: Also, you didn’t mention trying it in your comment.

@Damaged  
Wow! Such a new and innovative concept!
 
Of course i have.

@Boxless  

The auto-signout seems to persist despite ‘Remember Me’ being ticked and activity in an hour timeframe. Might want to lengthen that timer, lads, or disable it for those that actually tick the box.

Still kind of wondering why my “hide certain threads” userstyle no longer works on the new API… it doesn’t feel like this should be a problem…
 
(I use the Stylus add-on for Firefox btw)

@Gameplay The Pony  
It’s that little eye with a / through it you see along with the other things like Favorite, Upvote, Downvote, and Comment.  
It’s the last option. You click on it, then refresh the page, and the image will no longer be visible to you.

How does the hide button work?

@Gameplay The Pony  
The dislike button is NOT going to be removed.  
I already told you in that thread you made, this was heavily discussed by lots of mods, some admins, and the community 2 years ago. and I mean HEAVILY discussed.
 
The discussion lasted for the better part of a month, possibly 2 months if I remember correctly.  
The HIDE button was introduced instead.

Dislike Button wasn’t removed, but you moved the bans up?

Why the added extra click/page load to edit filters? And why make it a link that doesn’t stand out instead of a button? The edit button on my filters list was convenient.