0 3 * * * reboot

20 seconds, Germany. Waiting while they checked if my name was on the list.

https://lemm.ee/comment/13112418

Maybe start rendering pages right?

Vanilla Music – the music player I use.

Interesting.

Not
in
markdown

(Pressed Shift+Return after every word.)

Not in markdown.

But it works in other word processors (like Word, libreoffice) that distinguish between line breaks and paragraph breaks.

Example: Type

Once upon a midnight dreary  
While I was pondering, weak and weary  
Over many a quiant and curious volume of forgotten lore  

To get:

Once upon a midnight dreary
While I was pondering, weak and weary
Over many a quiant and curious volume of forgotten lore

(You can highlight the source code to find the extra spaces at the end of each line). Note that this is different from paragraphs, which add spacing between them:

Once upon a midnight dreary

While I was pondering, weak and weary

Over many a quiant and curious volume of forgotten lore

Once upon a midnight dreary

While I was pondering, weak and weary

Over many a quiant and curious volume of forgotten lore

This is how markdown works. There is no way to disable that. This is an old convention from when text editors didn’t wrap lines automatically and enables you to write long paragraphs of text, breaking the lines as it makes sense to you, without creating a paragraph each time.

See the Lemmy help page on markdown or the Markdown Guide.

Even international waters (or, as I just googled, the “high seas”, as is the more appropriate term) have laws. Usually you are subject to the laws of the ship’s flag state.

Too bad being dead gives the −100% strength debuff.

[Edit:] Sorry, I didn’t realize that this was the thread that took “die in funeral” part literally.

Not the corpse, but those who helped him.

Heavily depends on the jurisdiction that applies to you when you die. People will be better able to help you if you disclose that.

Do they think

no.

maybe everyone here is just a rude little shit.

Or maybe you’re just a snowflake that can’t handle criticism.

Wow, you are touchy. All I said was that I never experienced these two issues you report.

why be a white knight for Atlassian if you’re not employed by them

I don’t know. I’ll never share an opposing view ever again. All points I encounter shall from now on be taken as the one and only truth. I will never again engage in discourse, I promise.

ever had to rebuild a sprint because Jira failed to properly migrate the old cards over to the new one, but instead throws them all into the backlog randomly and now you have to hunt them down over the next hour?

No, never. Did you maybe not select the ‘move to new sprint’ option when closing the old one?

how about when you’re writing an update to a card and you’re two paragraphs in with log examples and the UI decides to dump your entire content when you accidentally click outside the wysisyg?

That has never happened to me, either.

constantly dropping calls, video quality is awful […], audio is terrible,

I have none of these issues with Teams. Maybe your internet connection sucks?

Just to provide some data on the radiation dose. It’s everyone’s own decision whether a ‘willy-nilly’ PET scan is worth it.

From the English Wikipedia:

FDG, which is now the standard radiotracer used for PET neuroimaging and cancer patient management, has an effective radiation dose of 14 mSv.

The amount of radiation in FDG is similar to the effective dose of spending one year in the American city of Denver, Colorado (12.4 mSv/year). […T]he whole body occupational dose limit for nuclear energy workers in the US is 50 mSv/year.

https://en.wikipedia.org/wiki/Positron_emission_tomography#Safety

From the German Wikipedia:

Es ist bei einer Strahlendosis von 1 Sievert (Sv), der 100 Menschen ausgesetzt sind, mit 5 Todesfällen durch Strahlenkrebs zu rechnen […]. Man müsste also 100.000 PET-Untersuchungen durchführen, um 35 Todesfälle an Strahlenkrebs (nach einer mittleren Latenzzeit von etwa 15 Jahren für Leukämie und etwa 40 Jahren für solide Tumoren) zu verursachen, das heißt etwa eine auf 3000 Untersuchungen

If 100 people received a radiation dose of 1 Sievert (Sv), one would expect 5 deaths due to radiation-induced cancer […]. One would need 100,000 PET scans in order to cause 35 cancer deaths (after a median wait duration of 15 years for leucemia and 40 years for solid tumors), which is about 1 in 3000 scans.

https://de.wikipedia.org/wiki/Positronen-Emissions-Tomographie#Strahlenexposition

Is this not rude:

I checked the code and I’m appalled. There are more BLOBs than source code

No. The commenter is voicing their own feelings and explains why they have them. There is neither blaming nor rudeness here.

And this:

I understand that removing BLOBs isn’t a priority over new and shiny features. But due to recent events, this should be rethought.

It would have been nice if you had explained why you think this is rude. The author expresses understanding that the maintainers’ priorities don’t align with the author’s. This seems to be an uncontroversial statement to me.

Then the author explains (I agree, it’s more a hint than an explanation) why they think the priorities should be changed. In my view their argument is sound. Again, there is no blaming or rudeness here.

They should have opened with a complement

I assume you mean “compliment”.

I’ve often heard of the “sandwich technique” – start with a compliment, then voice criticism, end with another positive thing. I find this is an appropriate procedure when voicing open feedback, that is, good things and bad things. However, this is a Github issue. Its whole point is to point out a perceived problem, not to give the maintainers a pat on the back or thank them.