F-Droid Offtopic

79 Members
Offtopic chat for the F-Droid project29 Servers

Load older messages


SenderMessageTime
9 Sep 2024
@cleared:matrix.orgCrepe joined the room.19:52:18
@cleared:matrix.orgCrepe left the room.19:52:32
14 Sep 2024
@bolnav:matrix.orgbolnav joined the room.19:09:45
@bolnav:matrix.orgbolnav

Matrix now requires authentication to view Matrix-sent images and media. Details on the changes at the blog for a summary + MSC3911 for the new upload API + MSC3916 for the new download API.

The IRC/XMPP bridges sections of MSC3911 and MSC3916 say that bridges will need to be updated, because today IRC / XMPP users cannot receive images (they receive the now-broken https download URL) and very long text messages (to workaround the IRC limit, which is server-dependent, but usually around 512 bytes, the server converts to image and sends the https URL).

All this applies to newly uploaded media. The old uploaded media is still available unauthenticated via the previous, deprecated API.

19:13:11
@bolnav:matrix.orgbolnav* IRC / XMPP issues with viewing Matrix-sent images Until now, Matrix's API endpoints for viewing images and media were unauthenticated and accessible via an HTTPS URL. Whoever had the URL could see the picture. IRC / XMPP bridges, as I read in MSC3911 and MSC3916, relayed the image's URL which points to the Matrix HS. Users downloaded the image directly from the Matrix HS. The bridges also auto-generated images in place of long text messages, to workaround the IRC limit (which is server-dependent, but usually around 512 bytes). Now, authentication is mandatory on all endpoints to view images and media. This breaks the above uses, as noted in the `IRC/XMPP bridges` sections of MSC3911 and MSC3916. All this applies to newly uploaded media. The old uploaded media is still available via the previous, unauthenticated, deprecated API. Details on the changes are at [the blog](https://matrix.org/docs/spec-guides/authed-media-servers/) for a summary + [MSC3911](https://github.com/matrix-org/matrix-spec-proposals/pull/3911) for the new upload API + [MSC3916](https://github.com/matrix-org/matrix-spec-proposals/pull/3916) for the new download API. (edited for clarity)21:08:21
15 Sep 2024
@rdfg77:kde.orglinsui🤦05:04:46
@rdfg77:kde.orglinsuiSo this feature doesn't only break old client but also bridge?05:05:08
@eatham:waffle.techEatham
In reply to @rdfg77:kde.org
So this feature doesn't only break old client but also bridge?
Unauthenticated media was being abused by pedos to use morg for storage, it needed to be fixed
05:14:08
@eatham:waffle.techEathamBut yeah, they could have waited for not support before enforcing it05:14:41
@eatham:waffle.techEatham* But yeah, they could have waited for bot support before enforcing it05:14:54
16 Sep 2024
@enigma9o7:envs.netenigma9o7So now pedos have to create a matrix account to access that storage? Great plan. 00:20:22
@rdfg77:kde.orglinsui🤣05:42:43
@bolnav:matrix.orgbolnav It's a long-awaited requirement for proper server-side purging of orphan media and for GDPR compliance of universities and national bodies who self-host or have a contract with EMS. Yes the timing is a bit tight, maybe something happened that needed a quick reaction. 06:47:55
@bolnav:matrix.orgbolnav* A breaking change was expected sooner or later, it's a requirement for *proper* server-side purging of orphan media and for GDPR compliance of universities and national bodies [who](https://en.m.wikipedia.org/wiki/Matrix_(protocol)#Adoption) self-host or have a contract with EMS. Yes the timing is a bit tight, maybe something happened that needed a quick reaction.06:52:14
@eatham:waffle.techEatham
In reply to @enigma9o7:envs.net
So now pedos have to create a matrix account to access that storage? Great plan.
They still needed an account before, they were posting to matrix and using the link to spam somewhere else. (I forgot what platform, maybe discord?)
12:22:50
@eatham:waffle.techEathamDiscord also did a similar thing but in a uniquely scuffed way a while back12:24:07
@eatham:waffle.techEathamNo clue why discord and matrix allowed linking it in the first place12:24:49
@eatham:waffle.techEatham* No clue why discord and matrix allowed linking it in the first place, and both messed by fixing it12:25:20
@eatham:waffle.techEatham* No clue why discord and matrix allowed linking it in the first place, and both messed up while fixing it12:25:32
@enigma9o7:envs.netenigma9o7Right, but now the discord people won't be able to see it, they'll have to register for Matrix.15:19:01
@enigma9o7:envs.netenigma9o7So we should be expecting an influx of pedos I imagine.15:19:30
@enigma9o7:envs.netenigma9o7 * Right, but now the discord people won't be able to see the stuff posted on matrix anymore, they'll have to register for Matrix.15:19:58
@bolnav:matrix.orgbolnav
In reply to @eatham:waffle.tech
No clue why discord and matrix allowed linking it in the first place, and both messed up while fixing it
Matrix was smaller at the time and it was known that "the URL is the password" was not going to scale. It has taken years of discussion before this proposal (linking images to events).
18:12:44
@bolnav:matrix.orgbolnav If anyone is interested in the past attempts, check here. 18:32:01
@eatham:waffle.techEatham
In reply to @enigma9o7:envs.net
So we should be expecting an influx of pedos I imagine.
They were spamming in random discord servers to annoy people iirc. Unlikely the people who got annoyed are gonna join matrix.
20:45:11
@enigma9o7:envs.netenigma9o7Ah, well that's different. I thought they were sharing images, and used matrix servers as a filehost.22:31:57
@lucasmz:tchncs.delucas! ∞ changed their display name from lucasmz ∞ to im bitter (you wonder why).22:46:28
@lucasmz:tchncs.delucas! ∞ changed their profile picture.22:53:54
17 Sep 2024
@lucasmz:tchncs.delucas! ∞ changed their display name from im bitter (you wonder why) to bitter (you wonder why).10:00:08
18 Sep 2024
@lucasmz:tchncs.delucas! ∞ changed their display name from bitter (you wonder why) to lucasmz.03:33:28

Show newer messages


Back to Room ListRoom Version: 9