this post was submitted on 16 Feb 2024
304 points (73.7% liked)

Mildly Infuriating

35045 readers
1 users here now

Home to all things "Mildly Infuriating" Not infuriating, not enraging. Mildly Infuriating. All posts should reflect that.

I want my day mildly ruined, not completely ruined. Please remember to refrain from reposting old content. If you post a post from reddit it is good practice to include a link and credit the OP. I'm not about stealing content!

It's just good to get something in this website for casual viewing whilst refreshing original content is added overtime.


Rules:

1. Be Respectful


Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.

Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.

...


2. No Illegal Content


Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.

That means: -No promoting violence/threats against any individuals

-No CSA content or Revenge Porn

-No sharing private/personal information (Doxxing)

...


3. No Spam


Posting the same post, no matter the intent is against the rules.

-If you have posted content, please refrain from re-posting said content within this community.

-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.

-No posting Scams/Advertisements/Phishing Links/IP Grabbers

-No Bots, Bots will be banned from the community.

...


4. No Porn/ExplicitContent


-Do not post explicit content. Lemmy.World is not the instance for NSFW content.

-Do not post Gore or Shock Content.

...


5. No Enciting Harassment,Brigading, Doxxing or Witch Hunts


-Do not Brigade other Communities

-No calls to action against other communities/users within Lemmy or outside of Lemmy.

-No Witch Hunts against users/communities.

-No content that harasses members within or outside of the community.

...


6. NSFW should be behind NSFW tags.


-Content that is NSFW should be behind NSFW tags.

-Content that might be distressing should be kept behind NSFW tags.

...


7. Content should match the theme of this community.


-Content should be Mildly infuriating.

-At this time we permit content that is infuriating until an infuriating community is made available.

...


8. Reposting of Reddit content is permitted, try to credit the OC.


-Please consider crediting the OC when reposting content. A name of the user or a link to the original post is sufficient.

...

...


Also check out:

Partnered Communities:

1.Lemmy Review

2.Lemmy Be Wholesome

3.Lemmy Shitpost

4.No Stupid Questions

5.You Should Know

6.Credible Defense


Reach out to LillianVS for inclusion on the sidebar.

All communities included on the sidebar are to be made in compliance with the instance rules.

founded 2 years ago
MODERATORS
 

This is about the most recent version of LibreOffice on Windows 10. I can't speak for other versions.

My daughter worked hard on her social studies essay. I type things in for her because she’s a really bad typist, but she tells me what to write… but I didn’t remember to manually save her social studies essay yesterday, and for some reason the ThinkPad rebooted, LibreOffice crashed and we lost the whole thing... because autosave was not automatically on when I installed it.

No, recovery didn't work. We just got a blank file.

I rewrote it for her based on the information we had and what I remembered and tried to make it sound like what a 13-year-old would write because it was basically my fault and she did do the work. I did have her sit with me as I wrote it in case she didn’t like something I wrote, but it was sort of cheating. I'm okay with that cheating since I know she worked hard on it.

First, though, I went into the settings and turned on autosave.

I like LibreOffice, but why the hell is that not on automatically? Honestly, I don't really understand why someone wouldn't want their documents autosaved, but I'm pretty sure most people would want that.

This isn't fucking 1993. I shouldn't have to remember to save a document anymore and it shouldn't be lost forever because of it.

Like I said, I like LibreOffice. I don't really want to trust documents to Microsoft or Google. But this was really annoying.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 17 points 9 months ago* (last edited 9 months ago) (2 children)

despite everyone reverting it back to double click

Says who? I'm still using single click and won't go back. This is a very different choice than having autosave on by default.

[–] [email protected] 1 points 9 months ago* (last edited 9 months ago) (1 children)

it is and it isn't

they're both bad UX, which FOSS is generally pretty bad at, probably because there's not as much overlap between people who who are really into FOSS and people who are really into UX

linux-centric communities also tend to be plagued by elitism, which i expect stifles a lot of this kind of thing before proper conversations can take root

[–] [email protected] 6 points 9 months ago* (last edited 9 months ago) (2 children)

it is and it isn’t

It is. Single/double click behavior is a matter of preference. Autosave on is a measure to mitigate risk. Very different "UX" choices.

Edit: just adding context that the clicking behavior on executables is defined by another setting on Dolphin.

[–] [email protected] 0 points 9 months ago* (last edited 9 months ago) (1 children)

And single click drastically increases the risk of running some sketchy executable just because you selected it. Every desktop I've used doesn't do that.

[–] [email protected] 2 points 9 months ago* (last edited 9 months ago) (1 children)

It doesn't, that's another setting. By default Dolphin asks confirmation before running anything with mouse clicks. Also you can double click just as impulsively as single clicking, so it wouldn't even be a good safeguard.

[–] [email protected] -2 points 9 months ago

Well then, you also have large documents or incriminating photos you may not intend to open.

[–] [email protected] -1 points 9 months ago (1 children)

Single/double click behavior is a matter of preference.

And defaulting to the preference that most people prefer or are used to is a matter of UX.

Which is why I say they're both UX decisions.

[–] [email protected] 2 points 9 months ago (2 children)

Which is why I say they’re both UX decisions.

yet very different - binning them into the same category is not helpful. Single click as default is ok, autosave off as default is probably not.

[–] [email protected] 2 points 9 months ago (1 children)

Auto save is extremely dangerous and should be off by default. Computers should never do things, especially with important documents, without the user telling them to. If the user wants to save the file, they'll tell the computer to save the file. If they don't tell the computer to save the file, they clearly don't want the file saved (if they do want it saved and expect the computer to do it for them without being told to, they shouldn't be allowed anywhere near a computer, sharp objects, or open flames, as they clearly could be a danger to themselves and others).

[–] [email protected] 0 points 9 months ago

Computers should never do things, especially with important documents, without the user telling them to

L take. Computers have always done thousands of things in the background. Autosave does not mean "overwrite the original file".

[–] [email protected] 0 points 9 months ago* (last edited 9 months ago) (1 children)

yet very different

which is why my first words to you were "it is and it isn't"

binning them into the same category is not helpful

both are caused by people in the foss space not paying enough attention to ux

increased attention to ux could solve both

personally i think categorising all work solely through the lens of severity is unhelpful

[–] [email protected] 1 points 9 months ago* (last edited 9 months ago) (1 children)

risk mitigation definitely comes before preference, whether you call them both UX or not

[–] [email protected] 1 points 9 months ago (1 children)

or i could argue that an issue 90% of people will run into is a higher priority than one 2% of people will run into

or i could argue than the risk of accidentally opening something you didn't want to is higher than the risk of losing unsaved work

the reason foss sucks when it comes to ux is this attitude of insisting that ux problems are somehow some "other" category of problem, rather than an engineering constraint that needs to be designed around like every other one

case in point, for some reason you're still refusing to acknowledge that they're both ux problems. and if you do, your original reply ceases to even make sense.

[–] [email protected] 0 points 9 months ago* (last edited 9 months ago) (1 children)

you’re still refusing to acknowledge that they’re both ux problems

I'm not - I'm saying calling them both UX problems is unhelpful when one is clearly more important than the other. In fact, single clicks by default does not even rank as a "UX problem", it's preference and habit.

If you're unable to differentiate what's an actual problem from what's mere user preference, you're no better at judging what's worth putitng time into than the open source contributors you're pointing at.

[–] [email protected] 1 points 9 months ago (1 children)

if you aren't refusing to acknowledge they're ux problems, you're saying it's unhelpful to call them what they are, which is obviously nonsense

and again, sane defaults are ux

[–] [email protected] 0 points 9 months ago* (last edited 9 months ago) (1 children)

Naming something accurately does not make the observation helpful. You're the one writing nonsense.

[–] [email protected] 1 points 9 months ago

if you're just going to take us back in circles again this discussion is a bit pointless, isn't it?

[–] [email protected] 1 points 9 months ago

First thing I do when using a new Windows computer is turn single click back on. Well, either that or show file extensions.