Early in January Google started telling users of the free tier of Google Workspace (previously G Suite and Google Apps for Work) that they had until July 1st of 2022 to pay up or the service would shut off. I’ve been a user of that service for years, and the various projects I work on used it too. Google Workspace was almost perfect for a free email service that worked with custom domains, but I always kept a regular gmail account in my back pocket to use for Google’s services because I thought this day might come.
The one good thing about Google deciding that one of the richest companies in the world can’t afford to give email services to small open source projects, small businesses, and individuals, is that it was the impetus to finally switch all of those projects away from Google’s services and support smaller businesses that don’t make the majority of their money from being a slimy advertising middleman.
So, off to Fastmail it was, signing up, importing mail from Google, and updating the MX records was easy enough after I realized I had forgotten a period at the end of one entry but there was still one large problem with Google’s services: Even after a week of changed records, long enough to bypass the time-to-live many times over, some automated corporate e-mail was still being delivered to a Google account that had no MX records pointing to it.
Turns out, that unless you go into the Google Workspace administration panel and specifically shut off the GMail service for all users, Google continues to receive some mail despite the MX records being set to go to Fastmail. It is truly bizarre that either Google or some automated senders ignore the MX records and I’m still not sure if it was only for mail delivered using Google’s services or what, but that was the final trick to getting all mail delivery go to the new service provider instead of the old one.
Epic is skipping Google’s Android app store (the advertising publisher calls it Google Play as if that meant anything) for their upcoming Android version of the free-to-play Fortnite (which is already on iOS and almost every gaming and computing platform.) There’s a beta signup here and the compatibility situation on Android is already a nightmare, check out the list of supported devices. It is extremely specific and the few Android devices I have aren’t supported.
There’s typically a 30/70 split, and from the 70 percent, the developer pays all the costs of developing the game, operating it, marketing it, acquiring users and everything else. For most developers that eats up the majority of their revenue. We’re trying to make our software available to users in as economically efficient a way as possible. That means distributing the software directly to them, taking payment through Mastercard, Visa, Paypal, and other options, and not having a store take 30 percent.
I’m not sure how well this is going to work out for people playing Fortnite. Google’s app store security is awful and routinely distributes software that compromises user privacy and security already, but at least they can moderate that. To get started with Fortnite on Android users are going to have to disable built-in security functionality that disallows third-party apps. Sideloading applications is useful and should be possible on any computer we use, but there are going to be negative consequences for users who don’t fully understand the risks involved.
Parents and tech savvy folks helping their friends and family are going to be busy when they realize their devices are compromised by installing a phony version of Fortnite, or a version that works but steals their credit card data. Try searching your favorite web search engine for the premium currency in the game, “Fortnite Free V-Bucks”, those scammers are oiled up and ready for anyone who falls into their trap.
Since Fortnite’s meteoric rise, there have been multiple YouTube videos running as ads that pitch Fortnite players easy ways to get free V-Bucks. (V-Bucks are Fortnite’s premium in-game currency, which lets them purchase limited-edition skins, gear and weapons.) Search “free V-Bucks” in YouTube’s search bar, and more than 4.3 million results will populate.
Google is selling a DIY smart speaker kit in the US through Target stores. They call it an AIY Voice Kit with the sub-heading of a “Do-it-yourself intelligent speaker.” Is it a kit that lives up to what the box promises for only $50? Let’s find out, together.
I’m not super fond of Google, they’re great at search but really make their money today by selling advertising space on websites. In my opinion, their “don’t be evil” motto has shifted as their priorities changed. There’s always the upfront cost of a product ($50) but with any smart speaker device there’s also the intangible cost of allowing a company to listen to, and process, whatever it can hear.
Ideally a smart speaker would only listen after a physical input, or most smart speakers also have a wake word to summon the device to interpret your speech and do something with it. This kit has an arcade button on top for physical input if that’s your game.
The do-it-yourself aspect is mostly fun, you assemble the included bare speaker, wires, cardboard, arcade button, and a Raspberry Pi Zero WH with Google’s Voice Bonnet add-on board to make the smart speaker. It’s not very difficult to put this kit together, the instructions are clear, but it is missing two things you’ll need, and one critical component of the setup requires other tools or devices.
You’ll need a very small flathead screwdriver to connect the speaker cables to the terminals. I happen to have the right screwdriver, but these terminal screws are incredibly tiny. Your regular household tools aren’t going to work with them.
It only takes about an hour before you’re putting the included Micro SD card in and powering the speaker up, or you would be. If there were a power supply included. You get a USB cable in the box, but no power connection.
Why not include the power supply and the screwdriver in the box? The screwdriver is almost understandable, because you could own one already if you’re into technology. The power supply is just necessary for the device to function, it makes no sense to me that it isn’t included in a general-purpose kit.
There’s one other small issue with the connections inside the kit. The wires to connect the arcade button are not friendly to the color blind. I am only mildly color blind, so I can’t differentiate between some colors with red and green in them. The arcade button wires are blue, green, grey, black, red, and orange. I had a hard time picking out the green from the grey and the red from the orange.
Okay you’ve got the kit assembled, and you’ve found a power supply to turn it on.
How do you connect to the box so that you can get it on your home WiFi?
The Rapsberry Pi Zero WH included with the kit has USB, it has HDMI, but they’re all mini connectors that need adapters and a hub to connect a keyboard and mouse. The other option, and this is what I chose, is to use an app that is only available for Android devices to get the diy smart speaker onto WiFi and find out the IP address so you can connect to it via SSH.
Once you get that IP address, and learn SSH and the Linux shell, you’re in business with a shell prompt at a Linux terminal running a variant of Raspian that Google’s engineers modified to support their Voice Bonnet.
Finally, you’ve got a smart speaker, right?
This is the real thing that kills this project, it doesn’t include any kind of hot-word, or wake-word, detection. Just like hotkeys, hotwords like “Hey, Siri,” and “Okay, Google” tell our phones and other smart speakers to start listening. Ideally the processing for these prompts happens on the device so they’re not just uploading everything you say to Apple’s, Google’s, or Amazon’s, servers.
This AIY smart speaker box promises, on the back, a “…smart device that understands and responds when you speak.” I don’t think that is truthful. It is not at all a smart speaker that listens when you speak, you have to press the arcade button before the included Python code will fetch Google’s assistant to start listening and interpreting your words into a reply. It’s an infuriating experience to have to press that button, especially whenever Google’s assistant demands interaction.
Google’s assistant can play a MadLibs game with you. Just like the real game, you supply the nouns, verbs, and adjectives and the assistant fills in a virtual MadLibs sheet to make a silly story. Unlike the real game, you have to press the stupid button each time the assistant needs the next word.
The times when I’d press the button there was no guarantee the assistant would listen. Many times it would just ignore me and I’d have to press the button again. I ended up pressing the button about 25 times to get 18 words into the MadLibs game. I don’t think I will ever do that again.
This built-in python-based assistant code was just slow to react and frustrating to interact with.
It was also incredibly limited compared to other assistants and even the iOS version of Google’s assistant is easier to use. This smart speaker version of Google’s assistant can’t even access your calendar or other information tied to your Google account.
Some of the replies from Google engineers on these forums indicate that more functionality could come to the device soon, but I don’t think they have any plans to add hot-word detection.
The most surprising thing I’ve found on that forum is that there was an older version of this project that included hot-word detection. This was possible when version 1 was based on the more capable Raspberry Pi 3 single-board computer. Apparently this is version 2 of their voice kit.
I don’t understand a lot of the choices Google made here, but the most important question is: Why did they drop the hot-word detection? Why don’t they mention anywhere on the box that you need an Android device or a bunch of adapters so that you can get this device on the network?
Maybe parents buying this kit for teenagers (the box lists it as appropriate for ages 14 and up) were concerned about it listening to them all the time. That’s the only reason I can think of as to why Google decided to drop the smartest feature of a smart speaker, otherwise it’d just be down to cost. The Raspberry Pi Zero WH is about $10, the Raspberry Pi 3 is about $35.
When I first saw this project in the store I knew there had to be some limitations to hit that $50 price point, and it went lower than even my wildly low expectations. I don’t think most people would be happy with the device as a “smart speaker.” Years ago, when you assembled a transistor radio kit, you ended up with a radio. What you end up with here is a very versatile Linux computer kit with microphones and a speaker that could be incredibly useful in the right hands. I turned it into an AirPlay speaker without having to write any code at all, and I haven’t even remarked about the quality of the sound yet — it’s fine in general, but turn it up loud and you’re gonna get distortion — but without hot-word detection this kit is just too dumb to be called smart.
Many people realize that smartphones track their locations. But what if you actively turn off location services, haven’t used any apps, and haven’t even inserted a carrier SIM card?
Even if you take all of those precautions, phones running Android software gather data about your location and send it back to Google when they’re connected to the internet, a Quartz investigation has revealed.
Since the beginning of 2017, Android phones have been collecting the addresses of nearby cellular towers—even when location services are disabled—and sending that data back to Google. The result is that Google, the unit of Alphabet behind Android, has access to data about individuals’ locations and their movements that go far beyond a reasonable consumer expectation of privacy.
Quartz observed the data collection occur and contacted Google, which confirmed the practice.
Google claimed they weren’t doing anything with the data received from Android devices, and says they’ll stop doing it (at the end of the month) now that they’ve been caught by Quartz.
I’m not sure why anyone should trust Google’s word about what they were doing with this information when they explicitly use location information to target ads and were pulling this shit with no way for a user to disable it.
You can bet that companies like Google (photos), Facebook and their subsidiaries such as Instagram, and Twitter, also scrape location information whenever you upload photos to their services by reading the EXIF data attached to every photo. You can download apps like Metapho on iOS to remove the EXIF information from your photos before you share them.
Google argued that it was too financially burdensome and logistically challenging to compile and hand over salary records that the government has requested, sparking a strong rebuke from the US Department of Labor (DoL), which has accused the Silicon Valley firm of underpaying women.
Google officials testified in federal court on Friday that it would have to spend up to 500 hours of work and $100,000 to comply with investigators’ ongoing demands for wage data that the DoL believes will help explain why the technology corporation appears to be systematically discriminating against women.
Noting Google’s nearly $28bn annual income as one of the most profitable companies in the US, DoL attorney Ian Eliasoph scoffed at the company’s defense, saying, “Google would be able to absorb the cost as easy as a dry kitchen sponge could absorb a single drop of water.”