
[{"content":"","date":"28 October 2026","externalUrl":null,"permalink":"/topics/android/","section":"Topics","summary":"","title":"Android","type":"topics"},{"content":"","date":"28 October 2026","externalUrl":null,"permalink":"/topics/nfc/","section":"Topics","summary":"","title":"Nfc","type":"topics"},{"content":" I hate carrying physical business cards. They get outdated, you forget to bring them, you find piles of cards from two jobs ago in an old jacket pocket\u0026hellip;\nI spend a lot of time at conferences - sometimes you need to give people your details, sometimes they just want to connect on LinkedIn, sometimes they can scan an NFC tag, sometimes they can scan a detailed QR code, sometimes they can only scan a simple one.\nSo I built a virtual business card app for Android.\nIt is now public: snrkl-labs/NFCBusinessCard under an Apache 2.0 license.\nWhat it does # This does 3 simple things really well:\nDefine a business card: Input the details or link to a web-hosted .vcf file, and optionally import a card image Show your details: Show the card on the screen, flip the card around depending on which way you need it shown Share your details: This can be via NFC or QR code. The QR code offers several levels of detail - the less detail, the easier the QR code is to scan. It is built for Android, needs no Google Play Services, no network permission, has no telemetry, and generally just minds its own business.\nOver NFC # Turn on send mode and the phone answers a tap exactly as a physical tag would. This uses Android\u0026rsquo;s Host Card Emulation, so there is no tag hardware involved.\nWhat works best is hosting a .vcf file somewhere and sharing a link to it. Any phone opens a link straight from a tap, iPhones included, and they get your full contact card.\nAs a QR code # Codes are generated on the phone from the active item and never stored. Swipe between four detail levels: Link only, Minimal, Standard and Full. Fewer fields means bigger squares, which matters in bad light or with a poor camera. Brightness goes to full while the code is up. Your contact card photo isn\u0026rsquo;t included in the QR encoding because it makes the QR code too dense and unscannable.\nAs a card # Use your own card artwork as a PNG, or let the app draw one from the contact details. Full card mode lets you flip the card to face the other person, and has buttons to share the card by NFC or QR.\nThere is also a widget that puts a mini card on your home screen, ready when you need it in a hurry.\nManaging items # Create a vCard field by field, copy one from Contacts, or import a .vcf. Items can be reordered, edited and deleted. Settings cover card shape (Australian 90 x 55, ISO/CR80 or US), default QR detail level, brightness and tap confirmation.\nNote: these screenshots use placeholder details and sample artwork.\nInstalling # Releases are signed APKs on the GitHub releases page. The easiest route is Obtainium: add the repo URL and it will pick up each new release. The signing certificate fingerprint is in the README and every release note, so a download can be checked with apksigner or AppVerifier before installing.\nIssues and pull requests welcome on GitHub.\n","date":"28 October 2026","externalUrl":null,"permalink":"/blog/nfcbusinesscard/","section":"Blog","summary":"I hate carrying physical business cards. They get outdated, you forget to bring them, you find piles of cards from two jobs ago in an old jacket pocket…\nSo I built a virtual business card app for Android.\n","title":"NFC Business Card","type":"blog"},{"content":"","date":"28 October 2026","externalUrl":null,"permalink":"/topics/open-source/","section":"Topics","summary":"","title":"Open-Source","type":"topics"},{"content":"","date":"28 October 2026","externalUrl":null,"permalink":"/topics/","section":"Topics","summary":"","title":"Topics","type":"topics"},{"content":"Things worth being able to find again, that someone else might find interesting too. Shorter and less finished than a post — a working note rather than a piece of writing.\n","date":"8 September 2026","externalUrl":null,"permalink":"/notes/","section":"Notes","summary":"","title":"Notes","type":"notes"},{"content":"","date":"7 September 2026","externalUrl":null,"permalink":"/topics/claudecode/","section":"Topics","summary":"","title":"ClaudeCode","type":"topics"},{"content":"","date":"7 September 2026","externalUrl":null,"permalink":"/topics/index01/","section":"Topics","summary":"","title":"Index01","type":"topics"},{"content":"I have been having fun playing with my new pebble index01 smart ring, and I have been coaxing it to do what I want\u0026hellip; The folks at pebble have done a FANTASTIC job of making it easy to have the voice notes from the ring parsed using a local (phone only) Speech-To-Text interface that I can then pass to a web hook somewhere for handling.\nWhy? I have a very strong preference for everything in my life living in Obsidian, so I naturally want my voice notes and anything that comes from them going straight to my Obsidian vault.\nSo I have claude-coded my way into an index01 router that runs as a local web hook on my phone, capable of routing different kinds of content to different places in my vault: Tasks, blog-post ideas etc, but also call intents to start timers, create calendar appointments etc\u0026hellip;\nIt keeps the recordings in the vault as well so that I can re-listen to the recording if I get back to my vault and find that something has been mis-transcribed (which incidentally, doesn\u0026rsquo;t happen very often!)\nThe notes arrive transcribed and the router files them by year/month/day in their appropriate folder based on the routing rules:\nInside the note you can playback the original recording if you want:\nIf it contains a task, the task is created for you:\nThe task is added to your tasks list for the day through a tasks search specific to the index tasks input location: It also handles timers and alarms via your regular clock app (these don\u0026rsquo;t end up in obsidian, obviously):\nAll up, it kinda looks like this from the ring to the Core Devices App:\nflowchart LR A[index01] --\u003e|voice recording| B[core app index feed] B --\u003e C{called via?} C --\u003e|single click| D[Do Nothing] C --\u003e|double click| G[play/pause] C --\u003e|triple click| H[skip track] C --\u003e|single click hold| E[index router webhook] C --\u003e|double click hold| F(reserved for future use) F --\u003e E G --\u003e|Spotify intent| I[Music Player] H --\u003e|Spotify intent| I[Music Player] And like this from my index router application\u0026rsquo;s webhook:\nflowchart TD O[index router webhook] O --\u003e Z{index router rules} Z --\u003e |Always Run: audio recording| K[Obsidian m4a file] Z --\u003e |keyword: task| Y[Obsidian task note] Z --\u003e |keyword: blog idea| X[Obsidian blog idea note] Z --\u003e |keyword: random| V[Obsidian random note] Z --\u003e |keyword: timer| W(Set Timer) Z --\u003e |keyword: new appointment| U(Create Appointment) W --\u003e |timer intent| J[Clock App] U --\u003e |calendar intent | T[Calendar App] Download: Available now on github at https://github.com/snrkl-labs/indexRouter\n","date":"7 September 2026","externalUrl":null,"permalink":"/blog/index01-router/","section":"Blog","summary":"A quick article describing how I am using the Pebble index01 smart ring using a custom Android application to provide web hooks that index can pass off to, allowing me to take control over what happens once I press the magic button on the index01 smart ring, and whisper my thoughts, my desires and even instructions to it.","title":"index01 routing with web hooks and Obsidian","type":"blog"},{"content":"","date":"7 September 2026","externalUrl":null,"permalink":"/topics/pebble/","section":"Topics","summary":"","title":"Pebble","type":"topics"},{"content":"","date":"5 September 2026","externalUrl":null,"permalink":"/blog/","section":"Blog","summary":"","title":"Blog","type":"blog"},{"content":"Notes, posts, and the occasional file\u0026hellip;\n","date":"5 September 2026","externalUrl":null,"permalink":"/","section":"wasteland","summary":"","title":"wasteland","type":"page"},{"content":"","date":"22 July 2026","externalUrl":null,"permalink":"/topics/product-management/","section":"Topics","summary":"","title":"Product Management","type":"topics"},{"content":"","date":"22 July 2026","externalUrl":null,"permalink":"/topics/prototyping/","section":"Topics","summary":"","title":"Prototyping","type":"topics"},{"content":"It\u0026rsquo;s funny\u0026hellip; A little while ago a colleague posted about how he is spending time sitting in the shed he\u0026rsquo;s having built, and ensuring he does everything he can to experience the \u0026ldquo;day to day\u0026rdquo; in there before design decisions are locked in, it got me thinking\u0026hellip;\nI was thinking about this again today, and it reminded me of the incredible lessons Tom Chi (of Google labs fame) shared with the Mind the Product community in the amazing talk he gave on rapid prototyping back in 2018. (Watch it here on YouTube)\nTom talks openly about using partial prototypes as quickly and as frequently as possible to get product teams out of the \u0026ldquo;guess-a-thons\u0026rdquo; up on the whiteboard or the chats that wander into the Highest Paid Person\u0026rsquo;s Opinion (HiPPO) zone.\nTom Chi on stage at Mind the Product in 2018 Instead, Tom advocates strongly on the value of incredibly rapid, real experiences that can drive data driven decisions.\nThis was a talk I was fortunate enough to find online when I was working for a hardware centric product deep in the modular rebirth of their platform. At the time, my days were often filled with design review sessions, sitting with engineers, commonly staring at a CAD model, or a software mock up of a function, trying to make design decisions:\n\u0026ldquo;Is Option A better than Option B?\u0026rdquo; \u0026ldquo;Feature X and Y are mutually exclusive. Which one should we keep?\u0026rdquo; \u0026ldquo;How should this feature work when the user does X?\u0026rdquo; etc\u0026hellip; Our approach to prototyping at that point was pretty \u0026ldquo;standard\u0026rdquo; by my measure: We were using 3D Printing and fast turn around suppliers to speed our time to market, but we still spent (what in hindsight was) a lot of time having discussions of how we imagined a thing would come to life, but very little time getting what we needed in terms of hard experience data to let us decide with confidence \u0026amp; move on.\nFast forward to the time after seeing Tom\u0026rsquo;s talk where I learned about the way his team did scrappy, super quick single experience level prototypes that let them go from guessing to an experience in hours, not days or weeks.\nIf I were to say that Tom\u0026rsquo;s story blew my mind, it would be a rather pronounced understatement\u0026hellip;\nLater that week, I was with our industrial designer \u0026amp; several engineers, staring at three different CAD models. We had to decide what shape the status lights on the top of the product should take: the problem was too big for 3D printed prototypes, and rapid manufacturing options would take weeks not days or hours\u0026hellip;\nThe \u0026ldquo;Tom Chi\u0026rdquo; vibe hit me and I asked:\n\u0026ldquo;What can we do today, right now, in the next few hours to allow us to make a data driven decision?\u0026rdquo; We scratched our heads for a little bit, then our industrial designer had a great idea: we could use the giant vinyl plotter we had (typically for putting a company\u0026rsquo;s branding on the product) to stick the three design options on some prototypes we had in testing. This could let us have an experience to help us decide, rather than more guesses and predictions.\nResult: 3 hours later, we had 2 terrible options excluded and one that worked really well, stuck on as stickers on test units. More importantly, we had rapidly coalesced on a solid decision everyone could see the reasons for and get behind:\nThe \u0026ldquo;STICKERS\u0026rdquo; style of prototyping was born.\nWhat\u0026rsquo;s more, these types of approaches helped us find creative ways to burn risk out of the project as early as possible, which any product leader in a company will tell you is the best way to operate!\nHow could this rapid path to experience help you on your product journey? What would a \u0026ldquo;STICKERS STYLE\u0026rdquo; prototype look like in your product?\n","date":"22 July 2026","externalUrl":null,"permalink":"/blog/prototyping-at-the-speed-of-stickers/","section":"Blog","summary":"A little while ago a colleague posted about how he is spending time sitting in the shed he’s having built, and ensuring he does everything he can to experience the “day to day” in there before design decisions are locked in, it got me thinking… I was reminded of the incredible lessons Tom Chi (of Google labs fame) shared with the Mind the Product community in the amazing talk he gave on rapid prototyping back in 2018….","title":"Prototyping at the Speed of Stickers","type":"blog"},{"content":"","date":"22 July 2026","externalUrl":null,"permalink":"/topics/tom-chi/","section":"Topics","summary":"","title":"Tom Chi","type":"topics"},{"content":"","date":"22 July 2026","externalUrl":null,"permalink":"/topics/youtube/","section":"Topics","summary":"","title":"YouTube","type":"topics"},{"content":" A Second Public IP on UniFi Without the Pain # If your ISP hands you an extra public IP as a framed route which is a single /32 routed to your existing WAN address rather than delivered on the WAN segment, the internet will tell you that you need to do something elaborate to use it on UniFi gear. Turns out you don\u0026rsquo;t: my UniFi gateway handled it natively.\nWhat \u0026ldquo;framed route\u0026rdquo; actually means # The extra IP arrives via the RADIUS Framed-Route attribute. In plain terms: the ISP just routes that /32 to you, with your current WAN IP as the next hop. The packets for your framed IP address simply turn up at your existing WAN interface. The address is not a second IP you configure on the WAN port, and it isn\u0026rsquo;t on the WAN\u0026rsquo;s local subnet.\nThis matters because most guides assume you can assign the static IP onto your WAN interface. With a framed /32 you can\u0026rsquo;t and for ISPs that only allow you to connect via DHCP (common on the NBN here in AU) even when your IP address is a \u0026lsquo;static\u0026rsquo; one, its really a fixed DHCP allocation, so you can\u0026rsquo;t mix a static WAN IP alongside the DHCP one anyway on the interface configuration.\nThe workarounds you can skip # Researching this turns up various suggested solutions:\nRun a PPPoE server on a separate EdgeRouter and put UniFi behind it. 1:1 NAT which technically double-NATs your traffic. Assign the IP to a VLAN interface which a /32 can\u0026rsquo;t do anyway, since there\u0026rsquo;s no spare address to burn on the interface itself setting up the routes. CLI / config.gateway.json hacks. I have tried this before, and they break constantly then one day might just disappear from your device config. None of these are necessary if your UniFi Network version exposes Source and Destination NAT in the GUI.\nThe simple solution: SNAT + DNAT # The /32 never touches an interface. It only ever lives inside two NAT rules.\nInbound — Destination NAT. Match traffic arriving on WAN destined for the /32 and rewrite the destination to your internal host (all ports, or per-port if you\u0026rsquo;re sharing the address across services). This is how you publish a service on the second IP.\nOutbound — Source NAT. Match traffic from your chosen internal host (or subnet) and rewrite the source to the /32, exiting via WAN. This makes that host egress as the second public IP instead of the primary — outbound overload / PAT, the way you\u0026rsquo;d expect.\nThat\u0026rsquo;s the whole configuration. No interface assignment, no PPPoE, no double-NAT, no CLI.\nTwo things to keep in mind # Nothing ARPs for the /32. Because the ISP routes it to your WAN IP as next hop there\u0026rsquo;s no \u0026ldquo;claim the address\u0026rdquo; step. If inbound traffic arrives and your DNAT rule matches, it works. If it doesn\u0026rsquo;t, suspect the upstream framed route (is it active? is the next hop your current WAN address?) before your own rules.\nMy ISP originally had some trouble with the concept, so I had to do some packet traces to show that the destination traffic for the new IP wasn\u0026rsquo;t getting to my interface to start with from an outside host, but traffic for my existing IP address was.\nI also did remote traceroute tests to the existing and new framed IP addresses, and could show that their routes were different in the last few hops, which indicated a config issue at their end. Once I did this, they went and found the problem and sorted it out pretty quickly.\nWatch the outbound return path. Make sure your chosen host actually leaves via the SNAT rule and isn\u0026rsquo;t using the default outbound NAT masquerade. Rule order and specificity matter here otherwise you can end up with traffic sourcing from places you don\u0026rsquo;t want it to. I use My External IP for this, mostly because the \u0026ldquo;raw\u0026rdquo; option just returns your IP address, which is super useful in scripts and automated tests.\nSummary # A framed /32 plus the GUI-based SNAT/DNAT on your UniFi router is all you need. If you are researching this like I did, you will find solutions for PPPoE servers, secondary routers, and config-file hacks that are actually un-necessary, so hopefully this helps someone save the time it took me to figure this out.\n","date":"23 June 2026","externalUrl":null,"permalink":"/blog/a-second-public-ip-on-unifi-without-the-pain/","section":"Blog","summary":"If your ISP hands you an extra public IP as a framed route — a single /32 routed to your existing WAN address rather than delivered on the WAN segment — the internet will tell you that you need to do something elaborate to use it on UniFi gear. You don’t. Modern UniFi Network does it natively with two NAT rules.","title":"A Second Public IP on UniFi Without the Pain","type":"blog"},{"content":"","date":"23 June 2026","externalUrl":null,"permalink":"/topics/networking/","section":"Topics","summary":"","title":"Networking","type":"topics"},{"content":"","date":"23 June 2026","externalUrl":null,"permalink":"/topics/unifi/","section":"Topics","summary":"","title":"Unifi","type":"topics"}]