• 0 Posts
  • 22 Comments
Joined 2 years ago
cake
Cake day: August 25th, 2023

help-circle



  • It’s Google analytics, and the meta/twitter/etc tracking pixels. Almost every site uses them because they provide useful data to the site owner and they are free.

    the images in OPs post appear to be designed to match their site theme, meaning umatrix wouldn’t even block them, because they are being served from the sites actual domain/CDN and not from Facebook/Google’s tracking domain.


  • bjorney@lemmy.catoAsk Lemmy@lemmy.world*Permanently Deleted*
    link
    fedilink
    arrow-up
    6
    arrow-down
    3
    ·
    edit-2
    3 months ago

    The buttons don’t do any tracking just from existing. They only exist to encourage a miniscule number of people to repost your content on social media, and in the event a share comes from that, they may include affiliate info

    All the useful information comes from the tracking scripts, which developers are also placing themselves because they are infinitely more useful. They tell you where visitors are coming from, how/if they are converting, everything they are viewing/interacting with on your site, and what the ROI of your ad spend is. In addition to telling you if someone clicked the share button.

    Tracking pixels have been decoupled from the “share” buttons for at least 10-15 years




  • bjorney@lemmy.catoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    4 months ago

    If I was the maintainer, I too would probably reject the PR because it didn’t remove the gender entirely.

    Cool, but that isn’t what happened here. The PR was closed immediately because the maintainer considered using gender neutral pronouns “personal politics” - he had ample opportunity to clarify his stance, or simply comment ‘resubmit in passive voice’, but he didn’t. Clearly the problem wasn’t the active voice, it was the summary of the change, because when that exact same PR was re-submitted much later with a commit message of ‘Fix some minor ESL grammar issues’, it was accepted with no discussion

    As an aside, I absolutely disagree with the use of passive voice. It’s more verbose, and harder for the reader to comprehend. It’s why every style guide (APA, Chicago, IEEE, etc) recommends sticking to active voice, especially in the context of ‘doing things’.


  • bjorney@lemmy.catoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    4 months ago

    If goes against established norms here

    What’s the established norm here. All people compiling software by source are male?

    he said politically motivated changes aren’t welcome

    What’s politically motivated about changing “he” to “they”. As you said, gender doesn’t apply here, so the neutral word is literally preferable.


  • bjorney@lemmy.catoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    3
    ·
    4 months ago

    Yes, I’m sure that PR would have been accepted instead /s

    But you’re right, it doesn’t matter at all, the reasonable thing to do would have been for the guy to spend 3 seconds clicking the accept and merge button, or 6 seconds making your change. instead he wrote a comment stating that inclusive language has no place in his project









  • Abolishing the monarchy would involve rewriting the constitution - if that was happening every province would want to slip in their own terms - Quebec would want specific French language rights and autonomy and if Quebec got their way Alberta would want something similar. We successfully altered the constitution back in 1982 - it took 2 years and the country almost blew up over it.

    Basically it would be a total shit show. Considering the impact the monarchy has on our day to day life (basically zero) it’s easier to just let sleeping dogs lie


  • That assumes that an adversary has control of the browser

    No it doesn’t, if they intercept an encrypted password over HTTPS they can resend the request from their own browser to get access to your account

    The big reason you don’t want to send passwords over https is that some organizations have custom certs setup

    What is the problem with that? The password is secure and only shared between you and the site you are intending to communicate with. Even if you sent an encrypted password, they wrote the client side code used to generate it, so they can revert it back to its plaintext state server side anyways

    It is better to just not send the password at all.

    How would you verify it then?

    If not sending plaintext passwords was best practice then why do no sites follow this? You are literally posting to a site (Lemmy) that sends plaintext passwords in its request bodies to log-in