eidolon @shaderphantom@awoo.space

@kaniini ugh, *concept of authority

@kaniini folks are gonna have to reconcile that FOSS inevitably attracts this shit. the F is the point. they're gonna have to accept either having free software without barriers to access or selectively choosing who has the right to access that software by some authority.

where people fall on that debate largely depends on their relationship to the concept authority. and i am willing to bet a number of people will be surprised by themselves if they thought about it.

If a developer must consider the implementation of a component in order to use it, the value of encapsulation is lost. If someone other than the original developer must infer the purpose of an object or operation based on its implementation, that new developer may infer a purpose that the operation or class fulfills only by chance. If that was not the intent, the code may work for the moment, but the conceptual basis of the design will have been corrupted, and the two developers will be working at cross-purposes.

You can't expect people to want to improve your software if its foundational design is sloppy and tightly coupled. The model with which components of code within the same application interact with each other is just as important to its robustness as it is to its future maintenance and interaction with other software. Inward and outward, design even at the "internal details" is of utmost importance.

To have a project accelerate as development proceeds—rather than get weighed down by its own legacy—demands a design that is a pleasure to work with, inviting to change. A supple design.

Domain Driven Design, p244

Wow... I've had a utility service serve my credit card number back to me, but never have I had it serve my SSN.

@noiob rather specific requirement on Apple's part for favicons to work huh? looks good nonetheless

@flussence@nulled.red possibly a compatibility option for buggy displayport devices that incorrectly recognize the high refresh rate modeline?

@Duende@snouts.online so it would seem

I have strong feelings about this because of how horrifically managed FFXI was and frankly still is with regard to account management.

I really, really wish that SquareEnix didn't come up with a proprietary 2FA solution. It all but guarantees that I won't use it because I absolutely do not trust them to maintain their proprietary mobile app for it.

If you want Auto Fill in KeePassXC to work in the FFXIV Launcher, make sure Remember ID is turned off and use the following Sequence:

{TAB}{PASSWORD}{ENTER}{USERNAME}{ENTER}

The window title is FFXIVLauncher.

This only works if you don't use a 2fa token, and takes advantage of a weird quirk where pressing Enter on the Password field when the Username field is empty places the cursor focus on the Username field.

Double fucking whammy: The launcher overrides the use of Ctrl+A and Ctrl+Z in the credential fields?

Why?

SquareEnix, it's fucking 2019.

@noiob I copy in the generated password from KeepassXC desktop rather than using the fill option in the extension, because it is unreliable for some pages.

It is almost as if it was fundamentally designed to discourage good password management habits in the first place to sell their proprietary 2fa token instead of allowing you to use your own TOTP.

The password change form on SquareEnix's Account Management site has JavaScript that disables pasting into the "Re-enter your password" field by checking if the combination Ctrl+V was pressed on keydown.

This does not give me confidence.