It's basically just sending a blank reason for now (which mobile apps and other API clients that haven't implemented the reasons yet will be doing as well). I plan to add support to sending a reason to AutoMod soon, and that will make it so that you can see why it's reporting things (which will be really nice).
Edit: done - https://www.reddit.com/r/AutoModerator/comments/2fia1l/automoderator_update_you_can_now_specify_a_report/
You're telling me that as an unlogged in user, if I clicked on the comments link for a thread, it would have always opened in a new window? No, my friend, it never did that. Let's go back to the beginning of the month: https://web.archive.org/web/20141001001208/http://www.reddit.com/
Click any of the comment links on the front page there. Not one of them is going to open in a new window.
New version looks good!
Which repo/endpoint/site should RES consult for localized versions of the ban message, for live-previewing the message before sending it? Maybe https://crowdin.com/project/reddit?
I like to be aware of interesting live threads that I may be missing out. You can hide that section easily with AdBlocks Element Hiding Helper. With that add-on you can fine tune any website locally, I hide divs that I don't like.
You can still report through the API without passing a reason and it will continue to work. If you want to send a reason, you just need to also pass a "reason" parameter along with your POST to /api/report: https://www.reddit.com/dev/api#POST_api_report
While it still is out of the official app, I'm currently working on an android app for mod-tools (disclaimer: not affiliated with the developers of the toolbox addon). It's in a sort of beta right now (as in not yet promoted, but already released, undergoing polishing), but it's coming along nicely and already has removal reasons and usernotes. You can follow along with progress in /r/mobilemod.
AFAIK it's never been implemented natively. I'm not looking at the blame now, but I did when I worked on this (before leaving to visit family for Christmas), and I usually put that sort of thing in the commit message to augment my memory.
Could I ask what you like about the apps? I read this article and wonder what they have over the web interfaces.
Wikipedia says less than ~~0.3%~~ 3% (see below in thread) of their users are on mobile apps, if I remember right, but their app engineers are something like ~~15%~~ 10% of their developer staff.
edit: fixed link & bad stat
You have to be really careful about how you anonymize data, though (for instance, see this excellent article on deanonymizing taxi cab ride data), and if we just reuse the user id, it'd be pretty easy to get a list of potentials, then narrow them down by public commenting/voting history. Or, if you already have a guess on who it is, to verify it.
So, that sounds like a good idea, but we need to be really careful in how we do it.
> When the Amazon S3 servers die... and they will die as history has shown time and time again.
S3 is one of the most reliable products available. On their product page they state:
Designed to provide 99.999999999% durability and 99.99% availability of objects over a given year.
That's a lot of 9s. And we've not seen anything to disagree with that.
> What happens to the CSS code? Is there another backup of it?
If something did happen to the objects on S3, then your CSS would be safe in the wiki.
Sorry for not responding to your comment posted at 3AM my time :P
If you'd like full control of the ordering of the top bar, the 3rd-party reddit enhancement suite lets you sort them however you wish and even control exactly which ones show up.
Play store link : Relay for reddit
Promo Video : Relay
Reddit was ahead of the curve on this:
https://thenextweb.com/insider/2015/07/06/reddit-came-close-to-becoming-decentralized-last-year/
r/RedditNotes
But then 2015 happened and reddit took the path we're on now; rampant authoritarian censorship.
We'd welcome your contributions to reddit: https://github.com/reddit/reddit/wiki
Can the same be done to "email verification"? I had some issues when I tried to verify my reddit account email. After understanding your commit, seems that the cause of my issue was a low expiration time and the use of "soft cache" to store my verification hash (same causes that created the 404 at 'password resets').
Seems reasonable that both reset and verify hash should have the same expiration time (r2/r2/lib/emailer.py) and be stored at hardcache.
Also, If I want to comment about a commit where should I do it? Here at r/changelog.. Git commit... Git issue tracker... PM to the developer... /dev/null...?
> We thought it would be faster if we put it on Google's servers...
Reddit never put the jQuery library on Google's servers. jQuery is offered by Google as an option among their many hosted JavaScript libraries https://developers.google.com/speed/libraries/devguide.
Hello! I'm not sure how much has changed in a month, but the pixel ratio within the srcset attribute appears to be supported on the major browsers now, with Firefox the only one still requiring enabling the feature.
http://caniuse.com/#search=srcset iOS 8, Chrome on both Android and desktop, Opera, Firefox likely to join soon.
Regarding the new theme:
It's an open source Reddit client. Typically, Reddit clients reimplement pretty much everything about Reddit themselves, so bullshit client-side changes on Reddit doesn't affect them.
https://play.google.com/store/apps/details?id=me.ccrama.redditslide
ok so i went to fonts.google.com picked Noto Sans font size 14px (just like the one new layot uses) and copypasted my previous comment in the preview it looks much better, black, crisp, just like it should be, but here on reddit for some reason its fuzzy and grey. Look again, the top line is from google site, the bottom line is from reddit. Dont mind the black artifacts at the bottom its just another text i just cropped the screenshot badly.
Firefox rejects the linke with the trailing period as not matching the cert while chrome directs you to a insecure page. Firefox's response seems like an expectable solution to me. It is a little more user friendly for chrome to ignore the trailing period because I would be plenty of people accidental add one on after typing out a link. However for whatever reason chromes user friendliness can result in some links being insecure. ssl.redit.com is the only one I know about directly but I bet there are others. Not all are mad insecure such as "https://www.google.com." vs "https://www.google.com"
You could make an exception for the site, otherwise I believe PrivacyBadger will block the viglink stuff (not sure, also depends how reddit sources the viglink js). Good extension to have regardless.