That sounds like a lot of fun to have
Technology
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
throw wireless charger in there, perfect place for a work phone over the weekend
Hell yeah now we're talking
With how this routes push notifications to an invalid IP, will they be resent or are they lost? When you put your phone is the box will you get all your missed notifications or just ones coming in while it's in the box?
Also your guests will think their phone is broken or your Wi-Fi is down.
In the article it mentions that it downloads the notifications while it's in the box
So basically it must cache the notifications to so that
To pull this off, the Raspberry Pi is programmed to act as a router. Any lookups that are associated with Google’s push service are redirected to a nonexistent IP and blocked from reaching your phone. When the mailbox door is opened and you place a phone inside, an ESP-32 is activated which sends a notification to the Pi that it’s okay to allow push notifications through.
I'm not well versed in networking, but this reads to me as it blocks and sends all notifications to the void and then while in the box the Pi allows new ones through.
The question then is do push notifications need an ACK and if they fail to receive one do they try again? I know cell carriers can tell when you're out of connection and can delay notifications and packets until you reconnect but this is slightly different.