I think it's more accurate to say that there simply is no wall space, because the walls ARE the stones.
There are ways around it, probably using copious amounts of conduit etc. but it's a lot of work compared to simply living somewhere that already has utility outlets where you need them.
> > Interjections like “oops!” or “uh-oh” are typically unnecessary and can sound insincere.
>
> This is a good observation.
I agree. That reminds me:
> Imagine a doctor performing a procedure and then suddenly saying “Oops! Something went wrong…” That is the last thing anyone wants to hear when the stakes are high, whether it’s surgery or someone’s source of income. That is not the time to be cutesy or fluffy.
> —https://wix-ux.com/when-life-gives-you-lemons-write-better-e...
Not sure this point applies to software, but I find a doctor saying oops to be very comforting. If I know when he screws up I don't have to be suspicious of him the rest of the time.
True story from my rotation on General Surgery during my third year of medical school (UCLA; 1973):
I'm in the O.R. doing what 3rd year med students do, namely holding a retractor to help keep the operative site open and perfectly exposed.
The attending, a very senior surgeon, vice-chair of the department, tells the senior resident, "When you accidentally nick a big blood vessel, instead of saying 'Oops," say "There!'"
My father is a retired surgeon, and has told me he was trained the same way — to say “there” rather than “oops”. The rest of the OR staff know what you mean, and it doesn’t spook a patient or other people who might overhear.
> I also hate websites where they hide your password while typing it in. Who can enter a password like Xaa3$#%^&*JqUIx correctly while blind?
You may consider using a password manager[1] that allows to auto-fill the password field. Use xkcd-based passphrase[2] for the master password to make it easier to type.
[1]: just not LastPass with their regular security breaches. Personally, I recommend Bitwarden.
Wow, it seems promising. Did you have a chance to use their CLI? Is it indeed better (more intuitive, less complex, more idiot-proof) than the GnuPG one?
I'm genuinely curious, what are the reasons you wouldn't pay for Telegram? Is that only a matter of preference, or does Telegram have some critical issues?
> you can only have playlist of songs. There's no way to collapse songs of a single album to one entry.
You could add the whole albums to the playlist, one by one, and then play the playlist w/ shuffle disabled. This last bit makes it a limited workaround, however.
On the other hand, Spotify API could allow to implement the custom solution to shuffle these, similar to https://spotifyshuffler.com/, if you have enough skills, time, and determination to do that.
I'm not using the playlists as a list of songs to listen to in one session. These are issues that come to the fore when you start using them as an organizational primitive. It's more limited than you think in that sense. For example, let's say I have a 20 album playlist. A very usual affair for me as I compile a single playlist for one month or a season. 20 albums comes around at 200 files. That's an ungodly amount of scrolling right there. (my seasonal/monthly actually average around 50 albums). Now imagine how painful it'd be for my long running playlists with hundreds or even that one playlist of mine with thousands of albums?
One workaround that I and other users make use of is to just add the first track of albums as links to the albums themselves. It's whatever. It's a bit stupid this is something I have to fucking deal with in the biggest music interface that the planet makes use of. Anyways, I mainly mentioned that as example of the ethos of Spotify UI/UX and what kinds of user they're primarily catering to. I guess I'm in the excluded group in this implementation of "worse-is-better" or something. (Is there a term for that group? Power user can't cover it because people with disabilities are usually in it.)
That was an interesting read, thank you!