Interesting links to Three Body Problem there.

In not exactly sure what you mean by inside an instance. But your post is

https://lemmy.ml/post/8102580

Which someone not on Lemmy could use.

Your client probably has a share or copy link option for a post.

Apparently it’s a tax write off.

It’s risky though because a) Star Trek is no longer all in one place b) if it’s a hit then Netflix benefit.

Voyager has been updated to support 0.19 and other changes in earlier version that Liftoff doesn’t support. Avelon (TestFlight version on iOS) also supports 0.19

I think the other thing to remember is that in different English speaking countries the word as a verb causes a different level of offence.

In British English it’s not offensive at all to say someone was b***ing about something.

It is odd that community bans don’t come with any communication.

I think the situation is:

Lemmy V0.19 uses a different authentication method to 0.18 and earlier.

It isn’t possible for a web app to know the Lemmy version initially.

So a web app can be compatible either with 0.18 or 0.19.

When most instances have updated to 0.19 or higher then the web app will switch to 0.19 only

Native apps aren’t affected

I think it’s a pretty accurate answer. The OP asked why it’s sometimes calked poaching and sometimes boiling. The answer being that they aare different things.

Boiling and poaching are not the same. Frying and sautéing are not the same.

Why in these videos is it always someone so out of it they can only say the same thing over and over. Pointless waste of time

Good question, I was thinking about this the other day. The reason being that development of several fediverse apps has seemingly stalled because the previously active developers have life issues. (I’m not moaning about it, just a straightforward account)

It seems to me that FOSS developers wouldn’t want their projects to be popular. Because that comes with pressure to constantly improve or expand and it takes up more time. So they start a Patreon or similar but that adds more pressure.

When projects are community developed then I see disagreements and personality clashes which increases stress for lead developers.

It’s to do with a change in timestamps going forward in Lemmy. Some apps have already updated to cope with it.

But how far is that?

You’ve inadvertently hit on the beginnings of an apparent paradox to do with the relationship between numbers and the counting numbers

Suppose the largest number you can have is X and the smallest number you can have is -Y. Then between -Y and X, you can count X+Y numbers which is clearly larger than X. But X is the largest possible number so X+Y doesn’t exist.

Have a look over on Matrix. Some have had short breaks but there are other reasons

From a users point of view, I understand your concerns. When other clients are undergoing significant development. It’s a little disconcerting to see the pace of Liftoff development slow and bugs not getting fixed.

Have you seen the discussion over on Matrix in Liftoff Development. From what I can tell, someone new has been doing things that hasn’t merged. Other than that not much has happened.

But really none of that matters because what matters to end users is seeing the bugs they encounter squashed and that’s not happening.

I’ve suggested before that this might be a funding issue and offered that users could donate.

This seems to happen quite often. I don’t know if it’s a bug in Liftoff or the error message could be improved to better describe a problem with the instance.

I don’t get the link. What have smart cars got to do with phone screens breaking. Surely the people who design smart cars will be different than the people who design phone screens ?

It literally says that it’s due to ageism!