Studios agreeing to censorship of any kind is disgusting, whether it be for political reasons (like what China usually demands) or for religious reasons (because some countries still live in the 500 BC).
I mentioned this to yesterday (on the Prime V post).
Your timestamps being off isn’t some minor thing. It’s breaking the Lemmy user experience. It’s common to sort by New, meaning that your posts (which Lemmy thinks come from the future) linger at the top of everyone’s feeds for at least 2 hours, ahead of posts submitted after them.
For example, this post, which you made at 17:20 GMT is above a post made at 18:20 GMT (and it will stay above posts made until 19:20 GMT.
Saw a short video on this scene and I was certain it was a joke. Why would they choose to do that scene? That’s hilarious, but would absolutely take me out of the movie lmao.
This was not THE “now I am become death” scene, the Trinity scene was it. In this scene we see him and Florences relationship sparking and we learn that he did not invent the quote, he got it from the Bhagavad Gita: …wikipedia.org/…/I_Am_Become_Death_(disambiguatio…
Did we watch the same movie? Because my complaint, my only complaint, is that the sex scene was where they used the quote in the movie, NOT the trinity scene.
It doesn’t happen with posts from kbin.social, which suggests it’s a fixable issue at Project Segfault.
I know it’s a bigger problem that needs to be addressed at KBIN & Lemmy codebase level, but - until it’s resolved there - maybe there are solutions within this thread that could be implemented at your end.
It doesn’t happen with all KBIN->Lemmy interactions. I tested it with a KBIN site that I think is located in roughly the same geographical area as Project Segfault (UTC+2) but it didn’t have the same problem: lemmy.world/post/2336003 kbin-u3.vm.elestio.app/u/upstream
It’s the latest post for the KBIN test account (dunno why I can’t link to it, but the point is the timestamps are the same)
Add comment