1,162 karma · joined September 15, 2020
My profile https://keyoxide.org/hkp/4AF679D0ABA0ED4B07BF7B6932CA3267C8D187D7
This is an OpenPGP proof that connects my OpenPGP key to this Hackernews account. For details, check out https://keyoxide.org/guides/openpgp-proofs
[Verifying my OpenPGP key: openpgp4fpr:4AF679D0ABA0ED4B07BF7B6932CA3267C8D187D7]
No, the alternative is that anyone with a password the app generates can send notifications to any app, which is (effectively) how WebPush and UnifiedPush work. The server that knows the secret URL can send a notification to that website or app.
For personal projects, I also prefer using fancier chips like the ESP32 series or the new generation of ATtinys.
Latency? You can hand deliver a password ahead of time, but not messages.
/s I hate how they're scaremongering with the vague term "Forever Chemicals" instead of just using the more specific terms PFAS or Microplastics.
My goal with this intro is to make something hand-solderable though, which is why I'm using QFP32, 0805, etc. In addition, this is Arduino Nano compatible to ease the transition. I'm using a CH340N for USB. An unfortunate consequence of this is that you need another MCU board to flash the bootloader first.
TBH ATmega328Ps are surprisingly expensive ($2.x) for their functionality.
Especially with the smartwatch, we are considering using an ESP32 WROOM/MINI module and will write about that too, eventually.
Some people are making NFC business cards, USB Hubs, and even smartwatches!
I'm looking forward to more JMAP adoption, especially on FOSS Android platforms.
> Please understand that this is in no way a judgment of you as a student or as a person, since our decision has more to do with the applicant pool than anything else—many of our applicants are not offered admission simply because we don’t have enough space in our entering class.
> none of the GPIO pins are exposed, the only IO is buttons, usbc or a QT/Stemma connector.
Sorry for losing context.
n=1, but I'm using a single CR2032 with a Badger 2040 (same as OP) and a DS3231 in parallel and it works just fine down to ~2.8 volts.
And XMPP is just $lightProtocolB, there is nothing stopping an XMPP-based UnifiedPush distributor w/o messaging from existing. If you don't use XMPP for messaging, there are many simpler distributors available.
> until now, the only option for push notifications was Google’s proprietary service, Firebase Cloud Messaging (FCM). UnifiedPush is a new alternative that allows you to get push notifications without being tied to a single company.
> Applications that support UnifiedPush can receive notifications via a dedicated UnifiedPush application that maintains a single server connection to receive all notifications. We call this “UnifiedPush application” a distributor;
Conversations is now a distributor, and UnifiedPush-supporting apps like Element or Tusy can receive notifications through it.
My PR fixing that in Caddy: https://github.com/caddyserver/caddy/pull/4865
For now, UnifiedPush is targeted towards De-Googlers, self-hosters and FOSS enthusiasts, not average users.