They should've just moved the other twitter domains too ๐ซ
cyrus
joined 1 year ago
This is a deliberate decision to force people to turn off tracking protection.
No this is a hilarious fuckup where they forgot to move twitter.com, pbs.twimg.com and more off of the Twitter domains, so Firefox started blocking it because to Firefox it looks like Social Media trackers.
Mozilla already pushed a fix.
This issue comes from the fact that even though the domain is now changed to x.com, it still tries to load content from twitter.com which Firefox thinks is social media tracking because it's coming from a different domain than the one you're on.
It's a hilarious and dumb oversight with this change.
Yeah but logically speaking that's what EX looks fort, and chances are that it'll work (because why else would it be in the response?)
Yes, the entire point is that it is the client where Sliding-Sync is being developed and tested.
Open https://yourserver.example/.well-known/matrix/client and see if this part exists in it:
"org.matrix.msc3575.proxy": {
"url": "https://slidingsync.lab.matrix.org"
}
if so, chances are it'll just work.
FYI: xManager itself is Open-Source, Spotify obviously isn't.
I won't properly reply to this, I'm biased cuz a friend of mine works on this ๐ฅด
That's just fine.
no I don't believe a damn word of what apple's gonna say on this, I just wanted to get the message out there that generally file deletion works by allowing data to be overwritten, so if the images are local this could very well just be that either it's showing data that hasn't been overwritten yet or it accidentally brought things out of the "recently deleted" depending on how long ago it was deleted.
no when I say "overwritten" I mean that the area is set as deleted in the filesystem and the next time something writes to that area the data that was there before is disregarded.
They're at @[email protected]