@Texou @purism I agree that accessibility still needs a lot of work on free software, especially on mobile. It is something we think is important and want to continue to improve as we can!

@kyle @purism thanks, I am ready to help testing or supporting teams. Because yes it is not ideal, but some things ork already, just need a good implementation in the distro (Debian, COmso COmmunicator for mobile). It is probably hard to improve free software itself, and maybe not your job (GTK, Qt, assistive techno devs do), but making the existing things available would be a

@purism @kyle great first step

@roland @purism Our UTM codes are only so we know which *platform* incoming traffic comes from (like referral links in web server logs). If you inspect them you can see there are no random strings or attempts to identify/track individuals.

@kyle @purism Well, I understand that part. Yet still you post it on a mostly privacy-favoring social network, like the #Fediverse and most fedizen are. #UTM is in its origin tracking through Google, not privacy-respecting #Matomo or #Piwik . I found stats.puri.sm and I see it is Matomo, fine. So I still found this a bit halfhearted, by on one side wanting to have a supply/production chain that is as short as possible to avoid tampering (see the #NSA scandal) for privacy/security reasons but on other side wanting to employ social-tracking. Also some Fediverse instances like mine are single-user instances where you can actually track individual people.

@roland @purism We have been open and very public in our thought processes to determine if it were possible to do marketing in the modern age in an ethical way:

https://puri.sm/posts/is-ethical-advertising-possible/

After much thought (and community feedback) we codified some ethical marketing principles we follow (including how we use UTMs).

https://puri.sm/posts/purisms-ethical-marketing-principles/

How we use UTM is not much different from HTTP referrer, it just makes it a bit easier for us to organize data in Matomo. Remove it if you want.

@roland @purism @kyle removing HTTP referrer is best practice nowadays in web development, at least when being serious about privacy.

@marcusosterberg @purism @kyle Here are good ones: stackoverflow.com/questions/68…

@purism @kyle @marcusosterberg <meta name="referrer" content="none" /> should be the proper one according to #w3c

@purism @kyle @marcusosterberg What I have implemented for my PHP script was a "de-referer" script, that accepts an URL, a hash for validation to make sure the script isn't abused and a cryptographic salt to make it even harder. E.g. spammers can now no longer send their URLs to my de-referer to circumvent some URL blocks.