@Infoseepage this is a real problem. My kids are getting to the age where they should be able to go to school or visit a friend by taking public transportation, by themselves. I know that most people with mental health issues are harmless, but this unpredictability is hard to ignore. It makes me distrustful of the commons.
I am on a bus and some guy two rows in front of me is talking to himself (apparently about jalapeños?!) and french kissing some ghost sitting next to him.
It is the type of thing not rare to be seen in Berlin, but nowadays it seems to be a daily occurrence.
Eu sou da opinião que nem tudo precisa ser traduzido. Médicos e cientistas sempre emprestaram palavras estrangeiras para descrever as coisas quando a lingua original não é concisa o suficiente. Teimar em uma tradução literal em 100% dos casos é um tanto xenofóbico. (ironia, acabei usando uma palavra que vem do grego)
Isso posto, diria que "Incompatibilidades com versões anteriores" é a expressão mais sucinta que faz algum sentido.
Ia implicar contigo e dizer que "alterações de quebra" é uma tradução completamente sem sentido, mas puta merda parece que esse termo é usado nos manuais traduzidos das empresas americanas.
Pior a emenda que o soneto. Nota zero pro escritor que teve o desleixo de colocar isso no papel.
@evan then I don't accept the premise that "human cloning technology has been rejected". Is there really strong backlash against in-vitro tissue/organ synthesis?
I think the answer has more to do with good old Capitalism than the technology itself. It is a lot easier to amass and deploy capital at scale for "AI infrastructure and automation" than it would be for cloning.
I know it's not an option, but I'm guessing "none of them", because what would be the point for them? They are all too focused on replicating their closed counterparts
The crux of the issue is that we shouldn't need to talk about "your FEP" when we are talking about "servers focused on implementing the ActivityPub API". The spec as is *is enough*. You are moving the goal posts by pushing a definition of "generic server" when it doesn't need to,and you are creating a "No True Scottsman" by saying that implementation X, Y or Z is "incompatible" with ActivityPub API.
> I think FEP-1b12 Announce is not compatible with ActivityPub. It has different side effects, doesn't update shares collection.
Why?
Updating the shares collection is orthorgonal to the behavior expected from a Group actor that claims to support 1b12.
Sure, you can say that if the server does not update the shares collection, it's not fully compliant with AP APi, but there is nothing a Lemmy server to add every activity to the shares collection.
Also, reading FEP-aea97 and I don't see anything there that my modest little server made with a "dynamic language" doesn't do already.
And It's not even like what I am doing is novel or incredibly diffiicult. If you spent a little time embracing RDF and JSON-LD, you could take a look at what Vocata did and you'd see how easy it can be implement the AP API.