Introducing – On This Day in Twistory

by @edent | # # # | 3 comments | Read ~291 times.
A list of columns with Tweets in them.

One of the things I loved about Facebook was its “On This Day” feature. There’s something delightful about seeing what nonsense you were talking about on this day a decade ago. Twitter doesn’t have anything like that. So I built it. Introducing – Twistory.ml Stick your @ name in, hit the big button, and you’ll…

Continue reading →

Moneyed – a personal OpenBanking API

by @edent | # # # # # | 1 comment | Read ~158 times.
API Token generation screen.

After writing about how to use MoneyDashboard’s unofficial API, the good folk at Moneyed told me about their officially supported API! So here’s a quick review & howto guide. Moneyed is a slightly strange service. I think it is designed for companies to give as a benefit to their employees. But you can sign up…

Continue reading →

Unofficial MoneyDashboard Neon API

by @edent | # # # # #
A tiny lego Storm Trooper eats a chocolate coin.

Yesterday, I wrote up how to use the MoneyDashboard Classic API. Read that blog post first before reading this one. MoneyDashboard have launched a new “Neon” service. The API is a bit more simple, but authentication is harder. Here’s a quick guide to the bits of the API that I found useful. I’ve lightly redacted…

Continue reading →

Unofficial MoneyDashboard API

by @edent | # # # # # | 4 comments | Read ~543 times.
A tiny lego Storm Trooper eats a chocolate coin.

The OpenBanking specification is brilliant. It allows you to aggregate all of your financial accounts in one place. You can give read or write access to apps and services. Magic! API access is restricted to registered financial institutions. That’s good, because it puts up a barrier to entry preventing dodgy companies slurping up your data…

Continue reading →

OMG! Twitter release an OFFICIAL conversations API!

by @edent | # # # | 2 comments | Read ~389 times.
An organic, branching tree view of a conversation.

One of the most requested Twitter API features is now available – the ability to get replies to a Tweet as a thread. Long time readers know that I’ve long been a fan of Visualising Twitter Conversations in 2D Space. But up until now you had to use horrible hacks to get the data. As…

Continue reading →

Relaunching @edent_solar. Part 5 – Getting data out of Fronius Solarweb

by @edent | # # # | 4 comments
A big grey box with lots of wires coming out of it.

Mostly notes to myself. My solar panels have an open API. But it’s only available if I’m on the same network as the Fronius inverter. I can connect my system to https://www.solarweb.com/ so I can access it anywhere in the world – if I have the right password. SolarWeb has an (optional) guest mode. You…

Continue reading →

Relaunching @edent_solar. Part 4 – Dual String MPPT APIs

by @edent | # # #
Graph showing the difference between east and west panels.

I’m hooking my solar panels up to the Internet! Installation Inverter API & Code My solar panels have an API! It tells me the total amount of power they’ve generated each day. But there’s a small problem… I have panels on the East and West sides of my roof. My solar inverter has two MPPT…

Continue reading →

Everything you know about Twitter character counting is wrong

by @edent | # # # | Read ~150 times.
Japanese text pasted into the Twitter compose window. It is showing that there are too many characters.

How many characters can a Tweet contain? It used to be 140, back in the good old days. Now it’s 280. Unless you’re Japanese. Let me explain… I run OpenBenches – a site which collects memorial benches. When a user adds a bench, the inscription is automatically Tweeted. If the inscription is longer than 280…

Continue reading →

Turn an old eReader into an Information Screen (Nook STR)

by @edent | # # # # # # | 14 comments | Read ~8,069 times.
Nook with a train display.

Here’s a quick tutorial for turning an old Nook into a passive display. This is an update to my 2013 post End Result An eInk screen which displays the trains I can catch from my local station. It shows the next few available trains, and whether they’re delayed. It also shows how long until the…

Continue reading →

Why API responses should be signed

by @edent | # # | 36 comments | Read ~4,400 times.
Doctor Who holding a glowing key

I’m going to start this discussion with the why and then move on to the how. Let’s begin with a couple of user stories. As the recipient of some data, I want to verify that it hasn’t been tampered with. and As the recipient of some data, I want to verify who originally published it.…

Continue reading →