> I don't have my own kids, but my experience with people with kids is that they're often desperate for social interaction, they feel limited in their ability to go out of the house, and they really don't want the extra work from having guests over.
It depends on the age of the kids and situation, but visiting people can be helpful if done carefully.
From reading (likely too much) internet commentary about having babies I assumed I'd be completely exhausted and worn out from constantly giving the baby attention for the first few months. Then I discovered that newborns sleep literally 3/4 of the day.
The hard part is the disrupted sleep schedule when their newborn stomachs are small and they need to eat every few hours. It can be really hard to adjust for people who have lived their lives with 8 hours of uninterrupted sleep all the time.
Funnily enough, having lived with middle of the night insomnia and disrupted sleep my life I wasn't really bothered by the newborn feeding schedule (via pumped milk in bottles, my wife did the real work during the day).
The value of socializing for us, which I didn't expect at all, was to fill the boredom. We were lucky enough to both be able to take a lot of time off work at the same time, which combined with the newborn sleeping 2/3 to 3/4 of the day left us feeling unplugged from the world.
Everyone is different, though. I've had friends who just didn't want to see anyone or have other people in their house for the first few months, so we respected that. I know some people who got tired of endless visitors trying to help, while others lamented not having enough help. It can be tough to feel it out so try to be especially intune with subtle social signals and look for hints to take.
I've started disregarding any AI take that is all-or-nothing. These tools are useful for certain work once you've learned their limitations. Anyone making sweeping claims about vibecoding-style use being viable at scale or making claims that they're completely useless is just picking a side and running with it.
Different outlets tilt different directions. On HN and some other tech websites it's common to find declarations that LLMs are useless from people who tried the free models on ChatGPT (which isn't the coding model) and jumped to conclusions after the first few issues. On LinkedIn it's common to find influencers who used ChatGPT for a couple things at work and are ready to proclaim it's going to handle everything in the future (including writing the text of their LinkedIn post)
The most useful, accurate, and honest LLM information I've gathered comes from spaces where neither extreme prevails. You have to find people who have put in the time and are realistic about what can and cannot be accomplished. That's when you start learning the techniques for using these tools for maximum effect and where to apply them.
"They're perfectly justified: the majority of hot new whatevers do turn out to be a waste of time, and eventually go away. By delaying learning VRML, I avoided having to learn it at all."
>> The most useful, accurate, and honest LLM information I've gathered
>> comes from spaces where neither extreme prevails
Do you have any pointers to good (public) spaces like this? Your take sounds reasonable, and so I'm curious to see that middle-ground expression and discussion.
> The most useful, accurate, and honest LLM information I've gathered comes from spaces where neither extreme prevails. You have to find people who have put in the time and are realistic about what can and cannot be accomplished. That's when you start learning the techniques for using these tools for maximum effect and where to apply them.
This requires the level of professionalism that 97.56% of SWEs do not have
> If I find out that management is being adversarial to ICs (eg. not offering to pay 75th percentile salaries
I find this funny because it suggests an equilibrium point where 75% of management must be adversarial by definition.
Adversarial is a loaded word. In my experience, the management I’d call most adversarial occurred at companies paying 80th to 90th percentile or higher. The attitude is that they’re paying employees enough that they need to shut up and put up with anything that comes their way. If you don’t like it, we have a list of qualified applicants who will gladly take your place in a heartbeat and won’t complain as much because those paychecks are larger than what they made at their last company.
> To be brutally honest, the stereotypical snarky HNer who is promoted to Staff Eng with an option to become an EM is the worst hire in any organization.
I think the trend where companies made Staff Eng into a pseudo-management role without reports was a mistake. It gets defended heavily by people who hold that role, but in the real world the Staff Eng people I’ve worked with who don’t really write code but float around and tell people what to do and how to do it become bad for an organization over time. It’s a trap because those people are often very valuable right after they’re promoted, but the roles where they become disconnected from writing code but retain the engineer title leads to a disconnectedness that flips toward counterproductive after a few years. It goes from having an experienced person coaching others to having someone with outdated and mostly abstract knowledge who gets to gatekeep everyone’s activities based on how things worked several years ago when they were still hands on.
> companies paying 80th to 90th percentile or higher. The attitude is that they’re paying employees enough that they need to shut up and put up with anything that comes their way. If you don’t like it, we have a list of qualified applicants who will gladly take your place in a heartbeat and won’t complain as much because those paychecks are larger than what they made at their last company
Well, yes in a way.
Criticism is expected and encouraged, but if it is done so while ignoring the 3 primary goals of a business:
1. Drive revenue growth
2. Expand TAM
3. Land strategic deals (not all customers are equal)
and is provided without a solution, you will be replaced. I don't care about prioritizing a bug fix or codebase refactor if the alternative means not being able to release feature X to help land Acme's mid 7 figure TCV deal.
The best Engineers I've worked with learnt how to merge valid engineering concerns with the top-line concerns mentioned above as well as being able to provide solutions. It's also how I was able to go from an IC to management.
If an employee thinks they know better, they can try to become a PM or start a competitor.
The bad experiences mentioned above really took off shortly before and during COVID, and this is why we are seeing the pendulum swing the opposite direction.
> I think the trend where companies made Staff Eng into a pseudo-management role without reports was a mistake. It gets defended heavily by people who hold that role, but in the real world the Staff Eng people I’ve worked with who don’t really write code but float around and tell people what to do and how to do it become bad for an organization over time.
I partially agree.
I think a Staff Eng role where it is someone who is deeply technical but helps align their team's delivery with other teams is extremely valuable (basically Staff+ as an architect role).
What I feel is the severe title inflation that arose during COVID turned "staff" into the new "senior", with too many people who floated into the role without aptitude.
> Yes exactly. I've forked many a library to meet my own needs. Usually temporary,
This isn’t really what the article is about. Doing a temporary fork for your own needs is equivalent to maintaining some personal patches.
The article is talking about running a forked project as an active fork that other people are using. That comes with the social overhead and community complications.
> you have the right to do that work without kowtowing to the authority of other people who did the work before you ("just fork it").
> The important point lost in many of these anti-fork posts is that forks usually aren't hostile, and "just fork it" isn't usually a dismissal of people's input
In my experience, forking a semi-active project can often be viewed as hostile by the maintainers. Some of those maintainers may turn it into a holy war where they try to throw their weight around to push back on the fork. I’ve seen claims of “trying to stealing our project” to mobilizing users of their Discord to warn people to avoid the fork across Reddit and other social media.
It doesn’t always go that way, as you experienced with the project you forked. The situation you described is about as non-threatening as it gets, though, because you forked for a single client and you don’t want to become a maintainer of a new project.
Come on now. This is a readily observable phenomenon; everyone notices it on both sides of the spectrum. It doesn't deserve your aggressive polemic.
From Wiktionary, "The observation that the longer it takes the media to identify a mass shooter in the United States, the less likely it is to be a white male."
> You cannot buy a dedicated MP3 player today with the software polish and quality of life that an iPod had in the early 2000s
I could see how many people would assume this, but it’s actually false.
There’s actually a big selection of dedicated audio players that do the job very well now. The battery life and audio quality are extremely good because there’s a niche market for them with a lot of competition.
If you think the iPod software experience in the early 2000s was good then you and I had very different experiences with iTunes during that time.
The resurgence of retro gear has a simpler explanation: Retro is cool. Vintage is cool. Has been for a long time. The reason we’re noticing it now is because the tech things we remember are finally passing that threshold where they go from being outdated to being retro. Just like clothes and styles that went out of fashion but are now retro-cool.
I looked pretty hard - I specifically don’t want an android OS called an mp3 player. I want a dedicated media player that has physical button controls (not touch screen), is very snappy, has a good UI, and has a purpose-built OS specific to only playing songs and podcasts, and maybe movies, which I can sync with my computer (maybe with rsync or whatever else). No apps.
The only option that I could find was an iPod classic, modded with an SD card and better battery.
If something else exists, especially brand new, I’d love to know! But I couldn’t find hardly anything that wasn’t just an Android phone with no cell service.
> I looked pretty hard - I specifically don’t want an android OS called an mp3 player. I want a dedicated media player that has physical button controls (not touch screen), is very snappy, has a good UI, and has a purpose-built OS
There are a lot of DAPs in this style. They're just not popular because the Android-based units are perfectly fine and don't feel like Android phones with an MP3 player app installed. Most buyers don't have arbitrary OS requirements, they just want a device that works well.
Hold on. You wear headphones while at the dentist? How are you supposed to carry on a conversation where they ask you question and you respond HOAYRA AH OT AH HA AH
I think Fiio and Hiby are the closest that exist today. They have dedicated hardware and physical buttons for the things listed in your comment. However, they do still ship with a custom Android OS and you need the touch screen to navigate your library and such. On the upside, this lets you choose your media library app. On the downside, it still isn't as good as the touch wheel on old iPods. I, too, am waiting for something like this to return. The Hiby is good enough until then for me.
Shanling uses a custom OS although it feels very primitive compared to iPods (e.g. the iPod Nano had VoiceOver for touch navigation). So I'm not really a fan of these dedicated single-function players; modern media player apps can be fast and convenient (more so than a clickwheel, honestly), and Android devices can still have dedicated control buttons. If only these devices weren't so bulky...
Fair argument, these devices (the Hiby R4, in particular, which is the one I have) are absolute tanks. Way too heavy and big to throw in your pocket for any reason, especially if you use a case. Still, it's nice to be able to (sort of) carry my own library around and never need internet to listen to it.
For me it's not arbitrary. An android device is a general purpose handheld touchscreen computer that happens to be used for music. That means a bunch of things to me:
1. "Touchscreen first" UX
2. Heavier than it needs to be
3. Worse battery life compared to a non-Android device
Using a touchscreen in the rain is impossible. Running out of battery sucks. Going for a run with a 240g brick is no fun, it'll pull your pants down to your knees and trip you.
Compare the specs:
Hiby R1
Dimensions: 86.9 x 60.6 x 14.5 mm
Weight: 118g
OS: HibyOS
Battery: 19 hour play time
Price: $159.00
Hiby R4
Dimensions: 129.6 x 68.3 x 18.5 mm
Weight: 231g
OS: Android 12
Battery: 11 hour play time
Price: $249
These are the things matter to me, in addition to the UX, sound quality, Bluetooth support, expandable / removable storage and sane file-based playlists.
> For me it's not arbitrary. An android device is a general purpose handheld touchscreen computer that happens to be used for music
Android is just an operating system. I’ve developed and shipped Android based devices that have no screen at all.
Android and Linux are both used for a wide variety of embedded systems. Saying they’re all general purpose computing devices isn’t true.
> Going for a run with a 240g brick is no fun, it'll pull your pants down to your knees and trip you.
Then don’t pick the largest device with a big screen? There are many smaller DAPs and phones that run Android. The reason that device is so large isn’t because it runs Android.
Generally, across most DAP manufacturers, the android devices are all of those things that I don't want, and the non-android devices tend to be cheaper, lighter, with better battery life. I don't specifically choose non-android, I specifically chose those other parameters and have simply noticed a pattern. I don't doubt you, but you haven't given any examples and I'm not going to spend my life searching for the exception that proves the rule.
My first Android phone was a Samsung Galaxy S2. It weighted two grams less than that Hiby R1. Of course it was much larger, but tiny by today's standards.
Now that I think about it, going no-buttons might have been a driver towards larger screens. Having at least a few buttons seemed to make it much less necessary.
Though I stand by my implied argument that older devices were not as heavy as we might remember them to be. And it is okay to consider 240g a bit too heavy in the context of a digital music player with no need for cassettes or mechanical parts.
Battery: 1AA gets 30h
Dimensions: 111.4 x 29.1 x 80.7 mm
Weight: 132g
Ok, so you were limited to 90 minute tapes with slow seek. But aside from that compare it to the specs I posted for the android vs non-android mp3 players. Remember, this cassette player has some seriously impressive clockwork inside that case and it's still smaller and much lighter than the android.
Also remember you can just buy another AA battery, and keep a few spares in your bag.
Whats wrong with some Nokia brick? Has bluetooth, probably 3.5mm jack too, lasts a week, has more physical buttons than you need for playing mp3s. Costs little
I have a few, and for managing and playing music the UX is absolute ass. Fine for dialing a number and occasionally switching to silent mode, but that's about it.
I can't vouch for it personally since I don't own one, but I saw a video on YouTube mentioning the Innioasis Y1[0], which supposedly does a decent job of replicating the iPod experience with some modern features like USB-C and Bluetooth at a decent price. Can be flashed with RockBox. No external SD slot, but it can be opened to swap out the SD card it comes with. Reportedly doesn't feel nearly as nice in hand as a real iPod does but that's pretty standard at this price point.
Damn this looks great. I'd guess the main difference in feel is the weight. iPod classic was about 2-3x heavier, which seems to be the main factor in premium feel.
This is a problem with "single-purpose" devices for kids, too. Drawing tablets, music players. They're all actually full Android phones (sans cell modem) and tablets. It sucks.
The issue isn't really Android, it's the touchscreen and the way the UX is a regression from many analog single-purpose devices.
If you gonna have a single-purpose device - make it analog (or close to analog)!
Don't give it a perceptible boot-time and all the other flaws that come with general-purpose computing. Don't make the user have to "wake up the device", let alone have to visually confirm that it is woken-up, before they can switch to the next song.
It represents a general purpose computer on your network which will accumulate vulnerabilities and never be patched or otherwise secured, making it a persistent insider threat as a launchpad for attacks on your network
Yes, I want these for my kids so very badly. They have Yotos (similar to Tonie) for bedtime, and iPads for school work, but those are not ideal for a number of reasons. I want them to be able to experience music like I was able to with an FM+cassette walkman clone in the '80s and early '90s, or with my Nomads and iPods in the late '90s and early aughts. Hopefully someone here can suggest something!
ETA: OK, there are quite a few highly-rated options on Amazon, so I just need to solve the "putting music on there" problem and the "dropping it and immediately destroying it problem".
For what it’s worth I love mine. I have app pinning enabled in android so it’s completely locked to just my music app. Feels like a great compromise of customizability while also feeling like an all in one device
This is my time to shine. I never stopped using dedicated mp3-players. After my trusty Philips Gogears died and became unavailable for purchase, I settled on Ruizu branded mp3-players. The Ruizu X02[1] is an absolute baller, cheap as hell, trustworthy and limited to the basic functionality you would expect from an mp3-player (music, movies, radio, pictures). You put stuff on it via USB + drag-and-drop just like the ol' days. Damn trustworthy too I had one soaked in water for 15 minutes - flinging it was like using a water pistol. Did it die? Pfft, this is a Ruizu we're talking about. Only thing that can destroy these are weights in the gym and even then they still play music: 'I have no light but I must play' style. No biggie, new one is 20-30 euro's it's like I'm robbing them
Not sure if this would fit the bill for you, but I really like it:
96GB Mp3 Player with Bluetooth 5.0 - Aiworth Portable Digital Lossless Music MP3 MP4 Player for Kids with FM Radio HD Speaker for Sports Running Super Light Metal Shell Touch Buttons (Actual Amazon description)
The "touch screen" is only for moving around the menu. The menu is easy to remember. Sound quality is really good and it takes a mini SD card. Right now, $40.
How hard did you look? You can type "MP3 Player" into an Amazon search box (and I'm sure Aliexpress and other competitors) and find many devices that are exactly what you say you want.
So i may install "Rockbox" again (yes - that was an upgrade), on an Kinese express-device? But, but, but...that may sound offending -sry, just for a moment i thought, "you were missing the topic completly" so... my 2 cents OT....
Platforms, globally synchronized making the Uniform, and bland?
"A Timex ad went viral this year: 'Know the time without seeing you have 1249 unanswered emails.'"
An Opinon-Refusal-Portal; the 'Wise people Of Gotham"-Citizen-Advice-Agency, the 120%-Normality, the Blue-Milk-Canal-Logic (Kishon)
I like watches cos, there once was a time, machines got that big and heavy, that wind-like waterpowered-energy couldn't make them start, nor keep them go, and therefore a 'need' of steam-engines...
"Cos nostalgia revealed a massive, underserved Service-economy-demand."
I have a Fiio M3K with Rockbox, it's great. My demands are not high though; I just want something light that I can put in my pocket, which shuffles a bunch of lofi music. It helps me tune my monkey brain out.
That brought back memories... Used to daily drive Rockbox on my old 80 GB iPod decades ago. Got a lot of use out of the FLAC support.
Latest project updates are dated 2025. Blows my mind that this project is still alive. Feels oddly out of place in today's computer industry where chips are locked down to prevent projects like these from existing.
Not sure why you want to have purpose-built OS as the hill to die on since many of those Android-based mp3 players absolutely outclass the old iPod classics in snappiness and compatibility and output quality.
Plenty of choices that meet your other criteria once you're OK with it being Android powered.
Like a SnowSky is very obviously stripped down Android that can only run the music app it's shipped with, but it's otherwise everything you want.
There's no way to win in these threads. It's a very common pattern on HN that somebody will say, "X doesn't exist!" And then people will proceed to point out that in fact does exist. And then you'll find out that the original poster has a bunch of non-functional requirements that were baked into their original request that they didn't state, and I usually don't agree with (typically because they are either not practical or only of theoretical concern).
They'll typically defend them using highly charged language, like claiming that having to carry a 200 gram device will pull their pants down because it's so heavy, or that managing a Bluetooth stack and USB doesn't require an OS, but rather just a couple of event loops that a non-professional could code directly in firmware.
I've simply stopped participating because in my efforts to try to help people, I find that I just get into silly arguments.
Only speaking for myself, but the problem with Android is that it and the hardware needed to make it run acceptably are absurd overkill for the use case, which drives up cost, cuts down on battery life, and adds a layer of unnecessary complexity (suddenly you need to think about what player app to use, for example).
Basically part of the charm of a single-purpose device is that it can be built to serve it purpose ridiculously well and do nothing else, and the second general purpose software enters the picture much of that is lost.
The endless amount of Chinese Android-based single purpose mp3 player devices that are obviously iPod Nano/Classic clones basically cost ~$30 and have 50hr+ of battery life. You don't have to think about what player app to use, they ship with the only one that runs. The rest of the Androidness is stripped out.
Then yes, there's obviously the other end of the extreme where the mp3 player is very obviously a phone without a radio with a price tag to match. And everything in-between.
I'd say there's actually too many choices cause the silicon and battery cost required to simply play music has gotten so cheap that it doesn't make sense to optimize the OS further than Android. I'm sure the economics of scale means the actual hardware wouldn't be cheaper by any noticeable amount either.
> Only speaking for myself, but the problem with Android is that it and the hardware needed to make it run acceptably are absurd overkill for the use case, which drives up cost, cuts down on battery life, and adds a layer of unnecessary complexity (suddenly you need to think about what player app to use, for example).
The battery life is fine on modern DAPs. Excellent, even.
I understand why an engineer would want a completely application specific, built-from-scratch OS that does one thing perfectly, but that's a pipe dream for a niche market.
A powerful and efficient SoC that runs Android is ultra-cheap these days. Less than $1. Hiring an engineering team to write and maintain a custom OS for a niche product would incur so much R&D cost that it would wipe out any money you'd save by using a smaller microcontroller and drive the final cost up.
Just think: How much salary would you have to pay a team of engineers to write the custom OS and maintain it? If you could optimistically sell 500,000 of these devices (good luck) then how much would you have to save in order to pay for the R&D?
You don't need "OS" to play some music, drive display and talk via USB/BLE. It's trivial task and could be done with a few event loops. A lot of firmwares is being written without OS. May be FreeRTOS/Zephyr to somewhat simplify the programming, but that's definitely not "OS" in a commonly accepted sense. You don't need team of engineers, one hobbyist could easily do that. I wrote firmware for a device of similar complexity (work with ADC, implements USB, BLE, some UI with buttons and leds) and I'm not even a professional.
Ohh that's interesting. Never heard that quote from him I don't think. I like Alan Moore's perspective on life. Seems like he had an interest more in the ancient arts, but more from an intellectual perspective.. Thanks for the reminder. I need to look at his behind the scenes stuff. I remember watching a documentary on the Watchmen (2009 film) DVD when I was a kid. Maybe it was in that. Looks like he is doing short courses this days [0]
Sure, you can find new MP3 players on Temu and Alibaba, but they are almost invariably nearly unusable instant e-waste (like most things on those sites) And iTunes was great back in the day -- it only got awful when Apple made it support iPhones, Apple Music, etc. When it just did what it was supposed to (rip CDs and put the contents, neatly labeled and organized on your iPod) it was unsurpassed to this day.
Yeah, people hating iTunes seem to have no clue how bad all the "alternatives" were back then.
I'll be the first to shit on current Apple, but seriously, it was very successful for a reason.
Agree. I think folks are romanticizing the iPod. It synced only with Mac via iTunes, had 5 GB of storage for $400 and had 10 hours of battery life and weighed 184 grams.
Today you can get a music player whose battery lasts five times as long, weighs one sixth as much, costs one-tenth the price, and stores 25 times as much, while also offering full wireless connectivity, supporting more audio formats, video playback, and reading books.
I think the ipod being so common has helped it remain useful 20 years on. There's a lot of them being sold cheaply as people clean out old drawers, spares/replacements and upgrades are readily available, how to work on them is common knowledge and tools to work on consumer electronics is common, and rockbox is available for most of the range. MP3 players were a commodity good with a huge range of models available from practically any company capable, but most won't have the market around it. My ipod has a 128GB SD card instead of a HDD and a battery that lasts at least 5.5 days playback instead of whatever the original 650mAH allowed
I agree on the some fronts. MP3 players that support a variety of other formats, including lossless, and have far better playback quality than any iPod ever did are out there.
But the last time I bought one I remember a mixed experience. On the one hand, it sounded incredible. On the other, as soon as I loaded all 9500 tracks in my library onto it, the UI ground to a halt. Storage wise I could have crammed many times the number of tracks on there but there was no way the user interface would cope.
And I had to organise it all manually on my computer in order to avoid a mess on the device.
And the sync experience absolutely sucked balls. There was nothing close to plug it in and forget about it.
So, with some regrets, I returned the device and got a refund. I still use Spotify[0] in the car, and CDs at home.
> Back in the day hackernews had some fire and resistance.
Most of the comments are fire and resistance, but they commonly take ragebait and run with the assumptions built-in to clickbait headlines.
> Too many tech workers decided to rollover for the government and that's why we are in this mess now.
I take it you've never worked at a company when law enforcement comes knocking for data?
The internet tough guy fantasy where you boldly refuse to provide the data doesn't last very long when you realize that it just means you're going to be crushed by the law and they're getting the data anyway.
> I take it you've never worked at a company when law enforcement comes knocking for data?
The solution to that is to not have the data in the first place. You can't avoid the warrants for data if you collect it, so the next best thing is to not collect it in the first place.
The technology exists to trivially encrypt your data if you want to. That's not a product most people want, because the vast majority of people (1) will forget their password and don't want to lose their data, and (2) aren't particularly worried about the feds barging in and taking their laptop during a criminal investigation.
That's not what the idealists want, but that's the way the market works. When the state has a warrant, and you've got a backdoor, you're going to need to give the state the keys to the backdoor.
There are some errors in what you write, and despite that, it is not clear to me what the supposed ‘realization’ would be.
1. The famous 2016 San Bernardino case predates Advanced Data Protection technology of iCloud backups. It was never about encryption keys, it was about signing a ‘bad’ iOS update.
2. Details are limited, but it involved a third-party exploit to gain access to the device, not to break the encryption (directly). These are different things and should both be addressed for security, but separately.
Evidently, after this case ended, Apple continued its efforts. It rolled out protecting backups from Apple, and the requirement of successful user authentication before installing iOS updates (which is also protecting against Apple or stolen signing keys).
Plenty of companies would do that if they could. The problem is it has become illegal for them to do that now. KYC/AML laws form the financial arm of warrantless global mass surveillance.
Where I live, government passed a similar law to the UK's online identification law not too long ago. It creates obligations for operating system vendors to provide secure identity verification mechanisms. Can't just ask the user if they're over 18 and believe the answer.
The goal is of course to censor social media platforms by "regulating" them under the guise of protecting children. In practice the law is meant for and will probably impact the mobile platforms, but if interpreted literally it essentially makes free computers illegal. The implication is that only corporation owned computers will be allowed to participate in computer networks because only they are "secure enough". People with their own Linux systems need not apply because if you own your machine you can easily bypass these idiotic verifications.
In Brazil, where I live, it's law 15.211/2025. It makes it so that the tech industry must verify everyone's identity in order to proactively ban children from the harmful activities. It explicitly mentions "terminal operating systems" when defining which softwares the law is supposed to regulate.
If you design it so you don't have access to the data, what can they do? I'm sure there's some cryptographic way to avoid Microsoft having direct access to the keys here.
If you design it so you don't have access to the data, how do you make money?
Microsoft (and every other corporation) wants your data. They don't want to be a responsible custodian of your data, they want to sell it and use it for advertising and maintaining good relationships with governments around the world.
> If you design it so you don't have access to the data, how do you make money?
The same way companies used to make money, before they started bulk harvesting of data and forcing ads into products that we're _already_ _paying_ _for_?
I wish people would have integrity instead of squeezing out every little bit of profit from us they can.
People arguably cannot have integrity unless all other companies they compete with also have integrity. The answer is legislation. We have no reason to allow our government to use “private” companies to do what they cannot then turn over the results to government agencies. Especially when willfully incompetence.
The same can be said of using “allies” to mutually snoop on citizens then turning over data.
> I'm sure there's some cryptographic way to avoid Microsoft having direct access to the keys here.
FTA (3rd paragraph): don't default upload the keys to MSFT.
>If you design it so you don't have access to the data, what can they do?
You don't have access to your own data? If not, they can compel you to reveal testimony on who/what is the next step to accessing the data, and they chase that.
Doesn't sound like it tells you now that it's default, but I'll see what it says next time. If they make the key-sharing clear and make it easy to disable, then it's fine.
With all due respect to Raspberry Pi and everything they’ve accomplished in the educational and hobby space,
I felt that one in my bones. I suspect a lot of people with embedded experience who worked with Raspberry Pi over the years feel it too.
reply