Like content recognition can’t recognize text, if that’s what it’s been configured to look for?

That would require us to deal with both Reagan and Nixon over and over again, though.

I guess their bullshit would be reverted when each loop resets. But still.

I’ve got my tricorne hat on and everything.

Right under the Tree Of Liberty.

religious reasons

I’ve just remembered. We’re all Shakers.

A revocable license for a virtual “product” whereupon they absolutely do not give you back your real world dollars if they terminate said license.

There’s no power imbalance in this transaction at all, no siree.

Anyway, I’m all for making backups of things. So you de-licensed me. Big whoop. I still have the file and I can still play it, and nobody can physically stop me.

You should probably have some safeguard to prevent jokers from uploading 14.2 gigabytes of absolute nonsense into your system’s password field just to see if they can make it crash. But I think limiting it to, like, 8 kB ought to be quite lenient for anything with a modern internet connection.

As others have noticed, various hashing functions have an upperbound input length limit anyway. But I don’t see any pressing reason to limit your field length to exactly that, even if only not to reveal anything about what you might be feeding that value into behind the scenes.

Ooh, ooh. And for implementing any Javascript or jQuery or whatever that pops up some kind of smarmy message when you right click: Believe it or not, straight to jail.

Plus, that kind of thing is not going to prevent anyone from scraping images from anywhere if they have the capability to lift a finger to press F12.

Characters are characters. The system I just wrote will accept anything, because the first thing I do with it is hash it. If you want to make your password:

░▒▓█ ʥ۞ݔݯݲݸݴݺ '; drop table users; 🤣💩ʩ █▓▒░

Then go for it. More power to you for typing that out or, more likely, letting your password manager remember it. Make your password as entropic as you can manage, I don’t care how you arrive there.

Leopards? Eating my face???

I meant without printing anything, for anyone without access to a 3D printer. This was in response to the above comment about freehanding it.

To use an ordinary box cutter for this purpose all you need is something to use as an endstop and something to use as a fence, and they have to be parallel to each other.

Ah. Another sterling strategy from Donald “Neville” Trump.

That works great until some dickhole implements the old, “New password cannot contain any sequence from your previous (5) passwords.”

This also of course necessitates storing (multiple successive!) passwords in plain text or with a reversible cipher, which is another stupid move. You’d think we’d have gotten all of this out of our collective system as a society by now, and yet I still see it all the time.

All of these schemes are just security theater, and actively make the system in question less secure while accomplishing nothing other than berating and frustrating its users.

You can also vent your printer outside, which is what I currently do, using this.

That’s the “zero width space,” Alt + 200B for Windows users. Another favorite of mine is the nonbreaking space, Alt + 0160, which a staggering majority of web sites and other systems fail to account for.

Don’t bug users to change passwords periodically. Only do it if there’s evidence of compromise.

This is a big one. Especially in corporate environments where most of the users are, shall we say, not tech savvy. Forcing people to comply with byzantine incomprehensible password composition rules plus incessantly insisting that they change their password every 7/14/30 days to a new inscrutable string that looks like somebody sneezed in punctuation marks accomplishes nothing other than enticing everyone to just write their password down on a Post-It and stick it to their monitor or under their keyboard.

Remember: Users do not care about passwords. From the perspective of anyone who isn’t a programmer or a security expert, passwords are just yet another exasperating roadblock some nerd keeps putting in front of them that is preventing them from doing whatever it is they were actually trying to do.

Who cares? It’s going to be hashed anyway. If the same user can generate the same input, it will result in the same hash. If another user can’t generate the same input, well, that’s really rather the point. And I can’t think of a single backend, language, or framework that doesn’t treat a single Unicode character as one character. Byte length of the character is irrelevant as long as you’re not doing something ridiculous like intentionally parsing your input in binary and blithely assuming that every character must be 8 bits in length.

I mean, you could make a jig to use a box cutter to make consistent width strips very easily with three pieces of scrap wood. But this commenter coming in here for the express purpose of trying to shit on 3D printer hobbyists was a stupid move on his part.

Things like this give us… balance.

Otherwise known as, “Justification for ownership of printer.”

Look, I totally didn’t just buy this thing as a hobby to make more parts for itself! See, I actually do occasionally make useful things with it!!!

That’s what I tell myself, anyway…

• Comes into a 3D printing sub.
• Insults 3D printing hobbyists.

For your next trick, you should try going into a biker bar and loudly proclaiming that motorcycle riders are sissies.