749
'Morale is at an all-time low': Ex-Googler writes scathing latter slamming layoffs and 'eroded' culture
(www.businessinsider.com)
this post was submitted on 24 Nov 2023
749 points (98.6% liked)
Technology
59581 readers
4213 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If you click into mine, all you see are two options both of which only serve to allow Google to Hoover more of your data.
Looking into this more a couple days ago, it seemed that without IP reservations, you can’t get the port forwarding option to appear. Which I haven’t messed with. On principal I refuse to deal with a router that has regressed in functionality and am instead dedicating my time to de-Google my life haha. I bought an openwrt compatible router this weekend.
I do have a bunch of IP reservations. I don't really know how you'd do port forwarding without subs static IP address to forward to. I have not seen any of the data sharing options, but it could be that I gave those permissions years ago and forgot...
IIRC the Google Wi-Fi app had some extremely simple selection process in the port forwarding that allowed you to review the device list with IPs and select for port forwarding. The app would then carry the pf rule regardless of DHCP. Seems very simple functionality that now requires multiple steps to achieve. I’m sure in the product management meetings they assumed the new Nest users were too dumb to handle such logic or just overlooked the functionality in general to speed the migration from Google Wi-Fi to Google Home. Seems like a great mini case study for poor product management.
Ah, you're right. It does work with dynamic addresses.
It works like this for me, currently:
Gotcha, maybe it’s the fact I’m running iOS, I can’t get any type of rule or DHCP assignment options to show up. Just the same two options for telemetry and Nest. Oh well, thanks for the help. I’m getting my new router Tuesday and should be off to the races!