I've been having some trouble cleaning out my closet and getting rid of t-shirts that I've received at conventions, but I'm glad that Ghostery just made it really easy for me to get rid of the...
I've been having some trouble cleaning out my closet and getting rid of t-shirts that I've received at conventions, but I'm glad that Ghostery just made it really easy for me to get rid of the like four shirts they gave us at PAX South. Glad I never downloaded their app or anything.
Edit:
“In one of the most stunning displays of humanity I have ever seen, no one has yet reply-all’d with a snarky comment,”
One of the best parts of the PiHole is that because it's at the router level, it also blocks all the ads in mobile apps/browsers for devices that are using your wireless. I've had a few friends...
One of the best parts of the PiHole is that because it's at the router level, it also blocks all the ads in mobile apps/browsers for devices that are using your wireless. I've had a few friends wonder why they're not seeing any ads while they're over at our house.
I have a Pi 1 model B+ and found it too slow for acting as my DNS. DNS resolutions could easily take an extra second with it. I should probably set up a pfSense box to do the same job.
I have a Pi 1 model B+ and found it too slow for acting as my DNS. DNS resolutions could easily take an extra second with it. I should probably set up a pfSense box to do the same job.
I second the PiHole recommendation; I wasn't using my Pi for anything, so I set PiHole up and it worked really well. Installation is pretty easy, and they have good docs.
I second the PiHole recommendation; I wasn't using my Pi for anything, so I set PiHole up and it worked really well.
Installation is pretty easy, and they have good docs.
Of course because developers took one email at the time and write those emails. Smh.
It does make me think their dev team is maybe not great at protecting my personal information. So I’d be less likely to allow them to collect usage data or something.
Of course because developers took one email at the time and write those emails. Smh.
No one thinks that they send out each email individually. People are upset because throwing emails into CC instead of BCC doesn't really exhibit an attention to detail or a concern for the privacy...
No one thinks that they send out each email individually. People are upset because throwing emails into CC instead of BCC doesn't really exhibit an attention to detail or a concern for the privacy of users.
I knew I should have been more specific. What I meant is that this kind of errors are done either by someone that access those emails to do user management jobs or by a script that some "manager"...
I knew I should have been more specific.
What I meant is that this kind of errors are done either by someone that access those emails to do user management jobs or by a script that some "manager" or "lead" should have approved once committed.
Either way it's more a "middle level" screwup than developer's.
I'm just tired of seeing screwup being nailed on the last link of a chain and good thing being recognised as success of the leadership's probably.
I think one should read "dev team" as in "product team" ( encompassing mgmt, if there is any at Ghostery ;) ). Ultimately, the underlying issue stays the same: Ghostery - as an entity - boasts on...
I think one should read "dev team" as in "product team" ( encompassing mgmt, if there is any at Ghostery ;) ). Ultimately, the underlying issue stays the same: Ghostery - as an entity - boasts on its own homepage that they "anonymizes your data to further protect your privacy." and in their actions end up cc-ing its users. There was a fuck-up and - as a user - it doesn't really matter whether it was from the last link in the chain and/or the middle: the entire chain is at fault.
Oh yes, I totally can get to it but if you think of the general audience, it's says developers and it's good enough if the general audience knows that developer != hacker. I mean, a long lost...
Oh yes, I totally can get to it but if you think of the general audience, it's says developers and it's good enough if the general audience knows that developer != hacker.
I mean, a long lost acquaintance (aka ex primary school "friend") of mine contacted me back on facebook some years ago asking me how I was doing. When I told him i was a software engineer he concluded I was an hacker and didn't want to be involved in dangerous stuff so he blocked me.
That's when I decided Facebook wasn't going to give me anything useful btw.
I mean, that's the average people online that is going to read this kind of articles :)
I've been having some trouble cleaning out my closet and getting rid of t-shirts that I've received at conventions, but I'm glad that Ghostery just made it really easy for me to get rid of the like four shirts they gave us at PAX South. Glad I never downloaded their app or anything.
Edit:
Beautiful.
What's a good alternative to Ghostery?
I use those two in combination with HTTPS Everywhere and they have been serving me well so far.
Have you heard of PiHole? I just installed one. It blocks the DNS requests at your router, and can't be blocked by websites.
One of the best parts of the PiHole is that because it's at the router level, it also blocks all the ads in mobile apps/browsers for devices that are using your wireless. I've had a few friends wonder why they're not seeing any ads while they're over at our house.
I have a Pi 1 model B+ and found it too slow for acting as my DNS. DNS resolutions could easily take an extra second with it. I should probably set up a pfSense box to do the same job.
I second the PiHole recommendation; I wasn't using my Pi for anything, so I set PiHole up and it worked really well.
Installation is pretty easy, and they have good docs.
Is it much better than pfBlockerNG? Like is it worth it to spin up an extra VM for it.
Of course because developers took one email at the time and write those emails. Smh.
No one thinks that they send out each email individually. People are upset because throwing emails into CC instead of BCC doesn't really exhibit an attention to detail or a concern for the privacy of users.
I knew I should have been more specific.
What I meant is that this kind of errors are done either by someone that access those emails to do user management jobs or by a script that some "manager" or "lead" should have approved once committed.
Either way it's more a "middle level" screwup than developer's.
I'm just tired of seeing screwup being nailed on the last link of a chain and good thing being recognised as success of the leadership's probably.
I think one should read "dev team" as in "product team" ( encompassing mgmt, if there is any at Ghostery ;) ). Ultimately, the underlying issue stays the same: Ghostery - as an entity - boasts on its own homepage that they "anonymizes your data to further protect your privacy." and in their actions end up cc-ing its users. There was a fuck-up and - as a user - it doesn't really matter whether it was from the last link in the chain and/or the middle: the entire chain is at fault.
Oh yes, I totally can get to it but if you think of the general audience, it's says developers and it's good enough if the general audience knows that developer != hacker.
I mean, a long lost acquaintance (aka ex primary school "friend") of mine contacted me back on facebook some years ago asking me how I was doing. When I told him i was a software engineer he concluded I was an hacker and didn't want to be involved in dangerous stuff so he blocked me.
That's when I decided Facebook wasn't going to give me anything useful btw.
I mean, that's the average people online that is going to read this kind of articles :)
You're right! I'm sorry, I misinterpreted your comment. It's not the developers faults, it was definitely a mid-level screw up.