This directive was issued in January of this year, what is relevance of being posted today?
I love all the instances where it says, we will not do this or infringe in this way... unless it is a matter of national security, which we don't have to disclose to you. So basically, do what you want as long as you write it up properly.
And this part:
5.3 Review and Handling of Passcode-Protected or Encrypted Information
5.3.1 Travelers are obligated to present electronic devices and the information contained therein in a condition that allows inspection of the device and its contents. If presented with an electronic device that is protected by a passcode, encryption, or other security mechanism, an officer may request the individual's assistance in presenting the electronic device and the information contained therein in a condition that allows inspection of the device and its contents. Passcodes or other means of access may be requested and maintained for the duration of the search if needed to facilitate the examination of an electronic device or information contained on an electronic device, including information on the device that is accessible through software applications present on the device that is being inspected or has been detained, seized, or retained in accordance with this Directive.
I had thought (and Supreme Court ruled) you could not be compelled to unlock an encrypted device, which is why I always powered mined down before crossing. That goes against the obligated to present devices in a condition that allows inspection portion.
The number is not associated with your account, it is just used to verify legit account creations. Retroactively nuking an account due to using a "banned" phone for account creation verification would be wild and not in Google's best interests.
I'm constantly spinning up new accounts for clients and I've used my number on way more than 4 accounts, so maybe it is on a rolling basis over some time period?
You can reach a point where the phone number you used for 2FA has been "used too many times" and then you're stuck in the middle of registration. There doesn't seem to be any documented limit anywhere and the only solution people have been able to use is find someone else to help you verify with their phone number. What makes this more difficult is when you get logged out of one of your accounts, they ask for a phone number for 2FA to login, you provide the same phone number you used originally (even though it is not officially associated with your account, just to verify registration), but that fails because your number has apparently been used too often. So now you can't even log in to your valid account that already exists. Sure, should have added some other form of 2FA or a passkey to the account, but why can't I verify with the same number I used originally? And just to top things off, you can't use your Google Voice number for 2FA account verification when signing up for another Google service.
>> I have wasted a significant chunk of my life counting out small numbers of parts into bags and posting them to people.
So, small parts like this are always counted by weight, and I'm wondering why you would spend so much time on a counting solution when "buy a scale" is right there.
I’m building an app that facilitates discovery and eases payments for roadside stands that sell produce, honey, maple syrup, eggs, firewood, crafts, etc. The concept is that any roadside vendor can sign up for free (forever, no add-ons or upsells) and they have an online home for their home business. The vendor can list up to 3 stands and show off the products they sell in each stand. Users can discover stands near them by list, search, or map, view the vendor and stand details, ratings, payment methods accepted, etc. When arriving at a stand the user can scan a QR code which opens a web cart, allowing them to add products they are going to purchase and then “check out” using one of the vendor’s stated payment methods like Venmo, CashApp, PayPal, Apple Cash, Zelle, or good old hard currency. We make these payments easier by standardizing the check out experience but we do not facilitate payments at all - these stands have always been and will continue to be self-serve on the honor system. Once you’ve paid, you get a receipt and take your goods. The vendor gets an alert that a sale intent was started and by which method so they know where to look for their revenue. In the future we may help with some basic reporting and very light inventory management if vendors ask for it. We allow users to alert the vendor if a stand is out of stock, which is also reflected in search so other users are informed as well. Users can then ask to receive re-stock alerts as the vendor restocks.
Then of course users can favorite stands and products, share them, rate them, and create shareable collections of stands they curate (The Honey Trail or Summer Sweet Corn All-Stars, etc.). Eventually we will be adapted for events like farmer’s markets, craft fairs, and christmas markets.
I built this because I am a maple syrup producer (tapping starts in a few short weeks from now) and I’m starting to get into mass sales of my syrup. I felt like people who produce and sell these products put a lot of hard work into the process and deserve a legit discovery tool as well as a basic stand management system that does not make them change their process or get in their way. An app like this costs basically nothing to run and I will ensure it is free to use as long as I am in charge. I’m testing this week and likely soft-launching in the next couple weeks - the goal is to be online around March 1.
It was just going to be web-only (Supabase with a Svelte front end) but after Claude put me in timeout last week I tried Antigravity and now have 80% of an iOS app and will scaffold my Android app in the next month - so native apps will follow a web release pretty quickly.
It's easy to see the word Waymo and think clanker autonomous car, but there are very often people inside that car - they are a rideshare service after all. Calling endangering other humans "legitimate" because you dislike the taxi company is not a good look.
I'm just getting started in iOS development as a hobby, but what does this mean? Can I now build my app in Xcode with an Android target and use that binary in the Play Store? It surely can't be that easy now is it?
I built https://invoicepad.app which is a free, completely in-browser tool for creating invoices, estimates, and quotes. Yes, similar apps have been posted here before, but none were built the way I envisioned, so I made my own. The key difference: all invoice data is stored in the URL hash, not the querystring. This is important because querystrings are sent to the server with every request, while hashes stay local to your browser. This means I can never see your invoice data, unlike other similar apps. The workflow is simple: use your browser's bookmark manager as your invoice filing system. Or if you want to keep it offline, just copy and paste invoice URLs into a text document for storage. I’ve also included helpful features like saved profiles to save on repeated data input. The next step is to finish working on a browser extension (v1 is being tested) to make bookmarking, editing, and saving changes even easier, that is if I ever stop being distracted by other side projects.
I recently moved two sites from GoDaddy's predatory WordPress offering (they were charging $1k a year just for some security add-on) to use Hugo + DecapCMS + AWS Amplify. Decap is a fantastic "good enough" CMS to do anything clients of this size need, the only downside is it takes about 1 minute to deploy any changes. Amplify let's you lock a version of Hugo to use, or bring your own, and it will build and deploy your site on any new commit if your repo is in Github or Gitlab. Both clients are currently billed $0.51 per month, and the only reason it is that high is because Route53 costs $0.50 per month per hosted zone. So both these clients went from paying nearly $3k each year for a WordPress site to paying just over $6 a year for a site with nearly the same functionality and none of the maintenance or security concerns. And once everything is all set up, which honestly is not that hard, the only "tech" they need to know is how to sign into Gitlab, which are the credentials they use to log into their Decap admin.
Supabase for registration and auth, frontend framework of your choice for views, Stripe payment links for subscriptions. You'll have to sprinkle in some Supabase Edge Functions for Stripe webhooks for your entitlements flow as well. AWS SES for transactional email. Something like Basedash for your admin panel and at this point you're running an MVP at least.
It's not a huge mystery why this is an issue. Most land that axis roam on is private and either does not allow hunting or charges very inflated prices to hunt. The other factor is the Hawaii DLNR is terrible at herd management. I've been hunting axis during the archery season on Lanai for years but am contemplating not going back because of how unorganized the program is and because they absolutely failed in managing the 2020 drought that killed almost 2/3 of the herd. I'd love to hunt Molokai or Maui but unless you personally know a landowner who will allow you to hunt, be prepared to pay upwards of $5K just for one animal. That's crazy.
Any light you want to independently control is a device. So yes, each bulb is a device. But that was with the TRADFRI, which it seems they don't sell anymore. It looks like the DIRIGERA supports up to 100 devices though, so probably nothing to worry about. Feels like I probably bought the first gen of their smart products.