Helps me automate stuff around my life with a few small apps that connect to Telegram message threads. Summaries from other APIs, smart home functionality, family errands and shopping list reminders with my spouse and more.
Made Hacker News Alerts bot - https://github.com/lawxls/HackerNews-Alerts-Bot. Basically using it as a personal feed of stories and for keywords monitoring (Like "telegram" for example :) )
Using the Todoist API, I fetch all the open tasks with a certain tag and post to a group I share with my spouse when requested.
Another bot I have is everyday at 8:30am to summarize the completed goals from the previous day.
One of the fun things you can do is using the set of places API methods.
flickr.places.findByLatLon returns a placesId based on a supplied lat/long of somewhere you might be interested in.
You can then use that placeId to get photos around that location with a call to flickr.places.getChildrenWithPhotosPublic
Even more amusing is that you can get the actual shape co-ordinates for that place (for example the shape values or the polyline values of your local suburb or city).
I can tell you that I didn't expect to be able to access the shapefiles, bounding boxes and polylines for essentially every suburb I needed for a location based app I was building 10 years ago from a photo app API.
QT5.. It's so well documented, and just a pleasure to work in.
I'm almost never using it though.. I mostly work with the Node API, and some of the larger libraries in the infrastructure, it's fairly okay too.
It's interesting how many people say this. Much of it is great compared to an abysmal baseline of terrible APIs often in C++ ...
... but they have a magnificent 'context' problem: Qt is complicated and you never really know where you are in the architecture. There are 8 'Window' classes and you don't know if it's for Widgets, QML/Quick, QGraphics, or legacy or what.
I double-dare you to go and figure out what JS engine they currently use and for what. Because it's evolved so much over the years, and they keep legacy stuff around, StackExchange comments are poorly noted with versioning, it's a labrynth of disinformation.
There are neat articles you can find if you dig, but my god, you shouldn't have to dig.
I learn 'foundational' things about QT all the time, and to add salt they have an article where they dare to indicate it's 'our' problem for their incoherent documentation, they literally state 'Dunning-Kolberg' effect on one of their pages! Total gaslighting.
The desperately need 'overview' documentation that are accessible and put everything in context - and especially it needs to be just presented in an organized way - literally the Left Hand Menu of their docs jumps around and you have no context. You're looking at Qt5 classes, search for something and only Qt6 variations come up, you have to flip to Google etc..
Some Qt classes are well documented, but there are serious problems. I honestly think Qt would be 25% more popular if they just explained things more clearly.
Helps me automate stuff around my life with a few small apps that connect to Telegram message threads. Summaries from other APIs, smart home functionality, family errands and shopping list reminders with my spouse and more.