Report site bugs here
Algebroot Neogears 
Sci-fi & Dragons
Shown on posts are the reason for the most recent edits, but the exact same edit (most recent) on the post’s history instead shows the reason for the second-to-most recent edit. This continues through previous edits so it’s impossible for the first edit to have a reason given despite being clearly an edit.
See the quoted post’s edit reason, and then its edit history.
Yoshimon1 
yay(){ yay|yay & };yay
I just noticed the formatting buttons/shortcuts produce wrong syntax before/after empty lines.Without an empty line, it correctly applies brackets and everything works.test
test
test[*test
test
test*]
test*]
When there’s an empty line, however, it adds another piece of markup before and after the empty line which get parsed as regular text.*test__test*[_test_
_test_]
If you remove the two tags(?) again, everything works.__testtest__[+test
test+]
Background Pony #4B52
I’ve been trying to change my password, but it always displays a “failed to update password” message. I’ve made sure that I’m not just mistyping the old password and tried on both desktop and mobile. I saw mentions of a similar issue from several years ago, but there didn’t seem to be any solution posted.
byte[] 
Philomena Contributor
@Background Pony #4B52
Are you entering in the right order?
Are you entering in the right order?
- new password
- confirm new password (must be same as 1)
- current password
Cloppershy 
On that note, when I changed my password a while ago, I stumbled over this as well. I’m used to the current password always being the first field. Also, the “Confirm…” and “Current…” look so visually similar that it ties the last two boxes together. I’m usually not that stupid, but it took me longer than I’d like to admit until I saw my mistake. Maybe some visual seperation between the old password field and the two new password fields would make this more clear.
Pone Addict
@Background Pony #4B52
Are you entering in the right order?
On that note, when I changed my password a while ago, I stumbled over this as well. I’m used to the current password always being the first field. Also, the “Confirm…” and “Current…” look so visually similar that it ties the last two boxes together. I’m usually not that stupid, but it took me longer than I’d like to admit until I saw my mistake. Maybe some visual seperation between the old password field and the two new password fields would make this more clear.
Background Pony #4B52
@byte[]
Yep, that’s the order that I put them in. I’m pretty sure that this isn’t just user error.
Yep, that’s the order that I put them in. I’m pretty sure that this isn’t just user error.
byte[]
Philomena Contributor
@Background Pony #4B52
Is the new password at least 12 characters long? It seems that I forgot to put the length constraint on that input field, oops.
Is the new password at least 12 characters long? It seems that I forgot to put the length constraint on that input field, oops.
byte[]
Philomena Contributor
@Wiimeiser
Yes, and it has been for a while. I don’t remember how long exactly. Increasing length requirements is the most effective way to protect against hash cracking attacks, which are getting more and more feasible due to the ever-rising hash speed of GPUs.
@byte[]
I added the missing minlength attribute.
Yes, and it has been for a while. I don’t remember how long exactly. Increasing length requirements is the most effective way to protect against hash cracking attacks, which are getting more and more feasible due to the ever-rising hash speed of GPUs.
@byte[]
I added the missing minlength attribute.
byte[]
Philomena Contributor
@Wiimeiser
You are confusing encryption and hashing. The distinction is beyond the scope of this thread, but in general, encryption is some reversible process E=Fk(D) that depends on a small key and a large amount of data. Hashing is an irreversible process H=F(D) that can be used to verify the integrity of the data D without actually storing a second copy of it.
You are confusing encryption and hashing. The distinction is beyond the scope of this thread, but in general, encryption is some reversible process E=Fk(D) that depends on a small key and a large amount of data. Hashing is an irreversible process H=F(D) that can be used to verify the integrity of the data D without actually storing a second copy of it.
BigBuggyBastage
Go fsck yourself
This is why it’s a good idea to enable 2FA, as well as using a decent password.
By ‘decent password’, I mean it should include non-alphanumeric characters, be randomly generated, and be as long as practically feasible.
Speaking of, what’s the maximum password length allowed on Derpibooru?
By ‘decent password’, I mean it should include non-alphanumeric characters, be randomly generated, and be as long as practically feasible.
Speaking of, what’s the maximum password length allowed on Derpibooru?
The Smiling Pony 
( ͠° ͟ʖ ͡° )
@BigBuggyBastage
For the love that all that is holy, do not openly encourage people to use 2FA without explicitly stating that losing access to one’s 2FA device or their backup codes guarantees the irrecoverable loss of their account.
Do you have any idea how many people don’t understand the concept of 2FA? How many people email the staff saying they never saved the backup codes or didn’t realize what it is they agreed to?
People that actually want 2FA will find the option on their own; too many others are just another unactionable support email down the line.
Yes I’m bitter.
Also, max PW length is 80 characters.
For the love that all that is holy, do not openly encourage people to use 2FA without explicitly stating that losing access to one’s 2FA device or their backup codes guarantees the irrecoverable loss of their account.
Do you have any idea how many people don’t understand the concept of 2FA? How many people email the staff saying they never saved the backup codes or didn’t realize what it is they agreed to?
People that actually want 2FA will find the option on their own; too many others are just another unactionable support email down the line.
Yes I’m bitter.
Also, max PW length is 80 characters.
BigBuggyBastage
Go fsck yourself
@The Smiling Pony
LoL Thanks.
I guess I took for granted that people kept the backup codes, but now that I think of it, it’s 2021, and people still don’t even make proper backups of their data – I should know better, because of the number of times I received the text message “My hard drive died, can you get my data off it?” this past year. There seems to be no time limit for PEBKAC.
Everyone else: don’t enable 2FA unless/until you KNOW what you’re doing. Oh, and FFS, save the damn backup codes. 😛
LoL Thanks.
I guess I took for granted that people kept the backup codes, but now that I think of it, it’s 2021, and people still don’t even make proper backups of their data – I should know better, because of the number of times I received the text message “My hard drive died, can you get my data off it?” this past year. There seems to be no time limit for PEBKAC.
Everyone else: don’t enable 2FA unless/until you KNOW what you’re doing. Oh, and FFS, save the damn backup codes. 😛
TheQuietMan
House of the Arcana
@byte[]
That explains something I was wondering about.
@The Smiling Pony
Is there a way to disable 2fa if I changed my mind?
That explains something I was wondering about.
@The Smiling Pony
Is there a way to disable 2fa if I changed my mind?
The Smiling Pony
Yes, but only by using 2FA or one of your backup codes. Once you enable it, you’re tied to those until you disable it.
Also, backup codes are single use only; if you use one, it can’t be used again.
( ͠° ͟ʖ ͡° )
@The Smiling Pony
Is there a way to disable 2fa if I changed my mind?
Yes, but only by using 2FA or one of your backup codes. Once you enable it, you’re tied to those until you disable it.
Also, backup codes are single use only; if you use one, it can’t be used again.
Blissful690
Violet Frost Fan
Okay, there’s something wrong with the reverse image search. For whatever reason, it thinks this image (G5 spoilers)…
…is this completely unrelated image:
Even adjusting the fuzziness level doesn’t seem to work, and always comes back with that image.
…is this completely unrelated image:
Even adjusting the fuzziness level doesn’t seem to work, and always comes back with that image.
The Smiling Pony
( ͠° ͟ʖ ͡° )
@Blissful690
Perceptual image dupe reports are based on splitting images into their four quadrants’ luminosity values. That means it’s entirely possible for two completely different images to register as a possible match if the average black/white scale on each quadrant is within a certain margin of error of each corresponding quadrant of another image.
This makes it a very fast check; of course, it also produces a tiny number of false positives, which site staff can quickly resolve. Rest assured that there is no automated merging of images based on any of these reports.
Fancier solutions are possible, but they’re more resource intensive, and more complicated to implement (namely stuff involving edge detection, that would run on top of existing checks).
Perceptual image dupe reports are based on splitting images into their four quadrants’ luminosity values. That means it’s entirely possible for two completely different images to register as a possible match if the average black/white scale on each quadrant is within a certain margin of error of each corresponding quadrant of another image.
This makes it a very fast check; of course, it also produces a tiny number of false positives, which site staff can quickly resolve. Rest assured that there is no automated merging of images based on any of these reports.
Fancier solutions are possible, but they’re more resource intensive, and more complicated to implement (namely stuff involving edge detection, that would run on top of existing checks).
Interested in advertising on Derpibooru? Click here for information!
Help fund the $15 daily operational cost of Derpibooru - support us financially!