Should I *GASP* create a reddit account so I can get support from Tuta(nota)?

hedge@beehaw.org to Technology@beehaw.org – 49 points –

Because they're not answering my support queries, and I've been having connectivity issues since the last two versions or so. Most of the time they've been pretty good, but if their desktop client can't sync to their servers it's of no use to me. Is anyone else having this problem?

EDIT: I would downgrade, but they recently changed the version numbers, so that's adding to the confusion!

EDIT EDIT: I was considering going back to Thunderbird, but then the question of course is where to host my email (and please don't suggest that I self host, that's really beyond my capabilities!). Also, I think I read that K9 mail was supposed to rebrand to Thunderbird for Android, but it seems like it hasn't happened yet. I just found this as well, about the supposedly forthcoming Thunderbird Sync:

We plan to support syncing of your email account definitions, credentials, signatures, saved searches, tags, tasks, filters, and most major preferences across multiple installations of Thunderbird on PC.>

Interestingly they don't mention calendars . . .

18

You are viewing a single comment

As a community, can we please stop this behavior? This isn't an article, but even if it was an article, rushing to be the first person to leave a "gotcha"-style message doesn't encourage a conversation. If you have an issue with a headline, it takes a trivial amount of time to explain what, specifically about the headline could be improved or wording that is more relevant to content that the author is presenting. You can also easily start a conversation about why sensationalizing the headline is damaging to individuals. By just pointing at wikipedia, or an xkcd, or leaving a comment like this, we're encouraging reddit and twitter style vapid interactions which consist of who can make the best joke or flame the person who posted it the soonest.

This doesn't promote a nice environment, when every article is met with "LAW OF HEADLINES, NO". It's exhausting to see. In most cases the person sharing the article isn't who wrote the article, so they aren't actually in control of writing it. Yes, they can choose new words to put into their post, but this platform auto-populates most links with the headline from the article, and also focusing on the headline draws attention away from the article itself and any useful or fruitful discussion that can happen as a result of discussing the content, rather than the often <.05% of the content of the article that the headline constitutes.

This isn't an article

Precisely. I'd have expected that would've made the "/s" implicit... and I'd like to point out I did provide a reasoning (short, but still).

By just pointing at wikipedia, or an xkcd, or leaving a comment like this, we're encouraging reddit and twitter style vapid interactions which consist of who can make the best joke or flame the person who posted it the quickest.

Once upon a time, my grandma told me an old joke:


A bunch of guys sit in a bar, and from time to time one shouts a number, then all start laughing. "35!", and everyone laughs. "127!", everyone laughs. A newcomer, after a while of looking at them perplexed, decides to ask what's going on, so one of the guys tells him: "See, we all know each other for a long time, we've told the same jokes over and over, so we decided to just number them to save time". The newcomer thinks for a while and says "That's convenient... 178!", and everyone falls silent. "That's a new one", whispers the guy.


Linking to Wikipedia or saying "XKCD 936", is not (necessarily) a way to "make the best joke or flame", it's (also) a way of not repeating oneself for the thousandth time. XKCD 1053, and all that 🙄

In most cases the person sharing the article isn't who wrote the article, so they aren't actually in control of writing it.

The person who wrote the article, is in control though. A source's bias, what did they decide to highlight, and how they decided to express it, is more often that not a good representation of an article's content, as both content and title usually fall under the control of the same person (except some AB engagement testing shenanigans... which deserve to be pointed out on their own).

However, I agree there might be a fine line between:

  • Criticizing the source
  • Criticizing the poster
  • Linking to a reference explanation

...which sometimes might get lost in connotations. Should I edit it to add the "/s"?

To be clear this was not meant as a criticism of you, specifically. I'm simply asking that we collectively stop this kind of behavior in general on this instance, for the reasons I outlined. If there is still a desire to criticize, that we do so in a way that is not simply stating the 'law of headlines; no', as that's something that I've seen happen on Beehaw dozens of times.

Ah... then I agree. Although personally, a link to a "question headline article" already makes me less willing to even check a conversation, and there are some on the frontpage right now... I've only checked this one because it was not a link. Could the low effort comments, indicate a criticism of the article selection itself?

Could the low effort comments, indicate a criticism of the article selection itself?

If we create a culture in which those who are upset about "question headline article" enter these threads to vent their frustration through low effort comments, it's not necessarily a criticism so much as it is a culture we've created. Think about what kind of content does well on Reddit or Twitter - often times people are engaging in a way because they know the community will respond in a way and they're looking for that particular kind of validation or engagement.

We need to take a step back from time to time and think about what we're encouraging and whether that's helpful. If you are uninterested in interacting with "question headline article" than simply don't. If many people share your opinion and don't want to interact with these threads, they'll die off and not get engagement and discussion whereas articles which don't suffer from the same problem will have active and healthy discussions.

Not every discussion is for you, and that's okay, but engaging with content in a way that can be easily seen as negative is generally not helpful. In fact, it's a lot worse than "not helpful" - we talk quite a bit about how we want to have an explicitly nice space and how nice spaces evaporate quickly in the face of behavior like this. There's a good deal of nice people who don't like being told "law of headlines, no" and will quickly leave the space if that's the kind of engagement they see. In order to encourage these kinds of people to stick around, we need to be careful about when we choose to criticize them.

I understand that you care a lot about whether a headline is reflective of the content and are triggered easily by headlines which are clickbait-y. But this isn't a sentiment shared by everyone and some of the people who don't share that sentiment are great people with lots to offer to this community. They may simply not have the time or the energy to correct what the author did, and are simply excited or happy to share an article they found interesting and aren't as easily triggered by poor quality headlines. They might be doing so because they're particularly interested in some insights and want to share in the joy of those insights with others. Or they may want to spur a discussion on which is elaborated upon within the article. The hyperfocus on the title and how it's presented and leaving an ultimately negative comment which discourages discussion and can leave the poster disheartened is not helpful to creating a nice environment.

Good points, and a FAQ quality answer. 👍

If many people share your opinion and don't want to interact with these threads, they'll die off and not get engagement and discussion

I guess a good rule of thumb (for anyone feeling put off by clickbaity headlines) would be to look at the number of comments, then only check the thread if there is already a discussion going on.

1 more...