Shane Brennan

51 Followers
96 Following
26 Posts
Founder, CTO, Advisor. Privacy is possible.
LinkedInhttps://www.linkedin.com/in/shaneebrennan/
Priivhttps://www.theprivacy.co/
In it we discuss #product #operations, #machinelearning, #strategy, and the future of #startups
Had a long conversation with @elijahmurray about the impact of AI, opportunities in AI-related sectors, and the intricacies of product development. Check out the episode on youtube or any podcasting platform! https://youtu.be/qz6reBFXbT4
Behavioral Change, AI as an Equalizer & Startup Opportunities - Shane Brennan | The Long Game #006

YouTube
Why does 0.1 + 0.2 = 0.30000000000000004?

Why does 0.1 + 0.2 = 0.30000000000000004?

Julia Evans

Americans Flunked This Test on Online #privacy

Many consumers want control over their personal details. But few understand how online #tracking works, says a new report from the University of Pennsylvania.

https://www.nytimes.com/2023/02/07/technology/penn-privacy-survey-flunked-consent.html

Americans Flunked This Test on Online Privacy

Many consumers want control over their personal details. But few understand how online tracking works, says a new report from the University of Pennsylvania.

"Password Managers: A Work in Progress Despite Popularity"

With comments from @wendynather & yours truly. Thank you @DanRaywood!

https://www.isms.online/information-security/password-managers-a-work-in-progress-despite-popularity/

Password Managers: A Work in Progress Despite Popularity

The end of 2022 saw LastPass report another security incident, and as we mark a day to change passwords, Dan Raywood asks if another piece of cybersecurity software had suffered so many security incidents, would users have given up on it by now? At the end of 2022, authentication vendor LastPass notified users and the wider world of a  security incident where 'an unauthorized party gained access to a third-party cloud-based storage service, which LastPass uses to store archived backups of .. production data.' The incident created headlines worldwide, including from Wired, which was heavily critical of LastPass's actions - or, to be

ISMS.online

FBI hacked. Not once, but twice.

First, the FBI-run InfraGard program suffered a breach. InfraGard aims to strengthen partnerships with the private sector to share information about cyber and physical threats.

Then, the Russian hacker group, Killnet, breached the FBI’s database and stealing the personal information of over 10,000 U.S. federal agents.

https://securityintelligence.com/news/fbi-database-breach-exposes-agents/

Audacious Breach of FBI Databases Exposes Agents

Recently, two major breaches of FBI databases and Infragard have created concerns about the organization's data security.

Security Intelligence
It looks like Norton LifeLock was breached. https://techcrunch.com/2023/01/15/norton-lifelock-password-manager-data/
Reminds me of that classic Willie Sutton line, that people rob banks because that's where the money is.
TechCrunch is part of the Yahoo family of brands

Hey! Here’s a chance to help make something wonderful: We're hiring a Staff Frontend Engineer for Glitch — an extraordinary opportunity to keep innovating on the frontend experience of Glitch, and to join a deeply caring & thoughtful team. The role is U.S. remote, salary is $169,000 to $245,000, and I've found Fastly's benefits to be exceptional, well-managed & inclusive. Plus, we have a warm, collaborative ethos within both the team and the community. Join us! https://www.fastly.com/about/jobs/apply/?gh_jid=4732318
Jobs at Fastly | Fastly

We’re always looking for humble, sharp, and creative folks to join the Fastly team. If you think you might be a fit, please apply!

@jerry @pauliehedron All good. Shouldn't be an issue in my experience. The resolving server should have tried the next record (dino). Not sure why there is a resolution error for so many right now, but updating the Authority records to only include dino may be the only thing I could see interfering with resolution. the 1 hour TTL should only apply to records that are successfully retrieved, so the caching rules for a missing or error result are per-resolver
@pauliehedron @jerry
Interesting. I didn't think that a failed server result should be cached, so if it is down to a single instance, the retry resolution should have worked. DNS is fickle, but this should just failover gracefully.