Feature suggestions and discussion [READ THE FIRST POST]

If only we had some way to annotate the characters in >>602649, I can’t tell who’s Gawd or Xenith, or if they’re even in there (the former is tagged but the latter isn’t)

@Wiimeiser  
Not a yea/nay to your idea, but throwing my two cents in: I really hate annotations that are visible by default, a la youtube and e621. Sure, sometimes they’re useful, but more often than not they just get in the way.
 
There are two instances I can think of where annotations serve a purpose. One is translations, and the other is facebook-style tagging characters in a photo. For the first, I much prefer our current method of uploading a separate, translated picture. For the second, I could see how assigning an image’s tag to an arbitrary region of an image could work (hover on a tag, rectangle appears) but given how often it’d be needed vs. how easily it could be misused I doubt it’s worth the effort.

Suggestion:  
Add “Foalcon” to the list of “Other important tags” on the Tag Guidelines page, it’s not only pushing the limits of what is legal in many places, but I’m sick of seeing this tag go disregarded as it’s one of the few things I truly cannot stand.
 
Oh, and also fix that one bu- **BANNED.**

So now that apparently the notifications section has been changed to have them appear page by page instead of being one long list, could we maybe have the option to change how many appear per page?

@BK Leonidas  
I chose 11 per page in a very opinionated manner because that’s the most amount at once that can fit on my 1920x1080 screen. Is there a particular reason you want to see more? (Additional page loads run under a second for me.)

i’m not a fan of this new page based notification system.

@byte[]  
It’s more because of a habit I developed during my time on this site to run through them all at once rather than a select few at a time. But also I figured it would be consistant to give users the option to change this since we also have settings for how many comments and submissions can be viewed per page.

@BK Leonidas  
More options usually means added complexity for the code, layout, tests and the ability to cache content.
 
When it comes to design changes in general, I’d recommend trying to get used to them for a few weeks first. Our human instinct is to react negatively whenever something we are very used to changes, but we also tend to adapt pretty quickly.

I had a minor heart attack when I saw that my notification page had suddenly shrank to only a dozen items. This is mildly acceptable though will be nightmarish when I’m trying to catch up on stuff on my phone. Requesting at the very least an option to have them sorted oldest to newest.

@Angrybrony  
I’m not, either.
 
Stop changing things that already work :V

@evan555alpha  
It was a necessary change.  
Just because things seem to be working fine on the surface does not mean there are not deeper problems with them.

@DragonMaus  
Necessary how?

@evan555alpha  
It’s not necessary, per se. I changed it to paginate because first, it is now actually possible to paginate notifications (previously it was not due to the idiotic way it was stored) and second, because I removed the upper bound on how many notifications you may have; there is no longer a hard limit of 100 notifications.
 
I understand that it broke your workflow, but what doesn’t these days. Maybe try reading your notifications more often?

To add to this: limit what you’re subscribed to if you don’t actually care about reading them. If you’ve developed a habit of amassing dozens of notifications and dismissing them all without seeing what they’re about, that really seems pointless and isn’t what notifications are for.
 
We could raise the amount per page, but I think it’s usually preferable to go for not having scrollbars. Also, it’s better for our server to have a limited amount of things to spit out on page request, as it puts a bit of an upper bound on loading times when loading times are dependent mainly on the number of things.

@byte[]  
I check my notifications once a day. I just wanted to know why it was seemingly needlessly changed. Why change it to pagination in the first place? On the rare occasion that I did go in to the double digits, I really didn’t mind just scrolling down, and working my way up. Was it intended to be more of a mobile feature or something?

ugh muh god this new notification interfaces is annoying.

A bug with the new notification feature: If you actually check any notifications (might be all of them) it blanks out all the other pages. Maybe I’m just imagining things…

@DoublePipe  
I mean I’ll go with it for now but I’m just saying that given how we also have settings for how many comments and submissions can be viewed per page, I don’t see why the same can’t be doable for this new notification system.
 
But then again I don’t code this site so what do I know?
 
 
@evan555alpha  
Also this.

It’s not like I ever had more than 10 notifications at once, but 11 per page is really too low. At least 20-25, (as default in comments) maybe even 50 (because they’re simpler than comments)

I check my notifications every day or two but still tend to pile up 50+ of them in that short time frame (even despite having more or less fallen completely off of checking my watchlists for the last several months) just because I’ve commented on thousands of images. I’ll load up the notifications tab first thing in the morning, then go about my internet browsing, waiting to catch up on derpi until I’ve gotten everything else caught up, oldest to newest so I know what time stamp the oldest unread posts in each thread will be so I’m not reading half a comment section over to get caught up. (EG: Oldest one is 23 hours ago. Any comments that are days ago on an image/in a thread have almost definitely already been read)
 
With the paginated system, whelp, guess I’ll just have to keep 4-5 tabs open to do that. At least it’ll be kind of sort of not really any faster to open 10-12 of them at a time because I won’t have to gasp hit page up (the horror)
 
Aaaaall of that said
 
I am supremely thankful that the 100 notification limit is gone because that was part of why I had to work that way, because otherwise on busy periods like new episode days I’d frequently hit 100 before I could catch up. How many days is it, still 3, or no limit?

This all seems like a really artificial “problem”… just go through the notifications as they come at leisure, it’s not like clearing through a few and hitting refresh, or just clicking to a page, is that big a deal =/

@Wesley Foxx  
… days? Notifications older than 30 days are automatically purged, but other than that…

I increased the pagination to 25 notifications per page.

@The Smiling Pony  
I mean. Most places it isn’t an issue, but most places also have notifications bring you back to the oldest unread post instead of the newest. 🤷 So for those of us who are OCD about missing out on unread replies and stuff.
 
@byte[]  
Sweet. Yes, it used to be anything older than 72 hours would be auto purged. Or maybe that was just an unfortunate bug, all I know is that even if it was less than 100 of them I’d still never have any older than just barely 3 days old if I went on vacation or something that left me unable to catch up on things frequently enough so since then I wouldn’t let it go beyond two without using my phone to catch up even if I’m traveling.

The way it seems to be made out to be, we need a pull system instead of a push system for notifications