No need for reverse engineering - it has already been done: https://github.com/RhetTbull/osxphotos

I figured this when IKEA started throwing out their current model for £5 a pop. Judging by how fast their stock was gone, they‘ll show up on ebay for a hefty markup any time now…

It’s the only CMS that runs on a classic AMP stack which is still the standard with cheap web hosters. And since everyone and their dog is using it, you can easily find support and ready-to-use plugins for almost anything.

In the car world, WordPress is your plain old petrol car that just runs, can easily be refuelled and you can get anything repaired at every other street corner. That’s why it is still so widespread.

Ghost runs on NodeJS which isn’t available at most cheap webhosters. Also it doesn’t do traditional blog things like pingbacks, trackbacks or webmentions.

BearBlog can’t be self-hosted at all - it says so right on their GitHub’s README.

WriteFreely is a Go binary that - again - isn’t supported on most cheap hosters. Also I can’t seem to find anything about it supporting pingbacks, trackbacks or webmentions. It seems to be more like a one-user Mastodon instance.

RCS dates back to 2007/2008 when it was still called lots of other names. (E.g. Joyn) And since then, not many cell providers adopted it. For all other providers (and those still sitting on an old version of RCS), communication will happen via Google-servers. It basically is a proprietary service under the disguise of a public standard. Especially because of this I’d rather use “proprietary” encrypted chats with it, so Google doesn’t get a copy of all my texts.

RCS at this point is just another Google messenger. And officially unencrypted as well. At least Google recently implemented encryption on top of it and it looks like Apple will adopt it as well.

Back when BlackBerry and their unified inbox (all messages from email, AOL, ICQ, MSN, Yahoo, etc. in one single list of messages) was still a thing - did people get bullied because of their choice of messenger?

It pops up on BundleHunt every once in a while.

MountainDuck supports this. They call it “cache on demand”. So you could setup an SFTP connection and use it via that. The next version of MountainDuck - v5 - should even support SMB.

I’ve had people tell me that the woman stays at 73 Yards because that’s the range of the TARDIS’ perception filter, but if that has ever been mentioned on the show, I’ve missed that little tidbit.

Kate mentions this at the café as the distance where a person with 20/20 vision can’t make out any facial details anymore. But there never was mentioned any relation to the TARDIS perception filter.

Let me add the “teleporting” stuff during the train ride. Also, what determines in which direction the blurry woman appears? And why didn’t Ruby - in all those years - not try to throw a stone or a bottle after her - just to see what happens? And if that scary lady really was “old Ruby”, how did she endure days/weeks/years outside in the rain?

Thinking about this, when Ruby was pacing around inside the pub while the other guy went outside… that blurry lady must’ve floated around - always keeping exactly 73 yards distance from Ruby, right?

And how did the “scary” stuff even work with the trained UNIT elite professionals that were explicitly briefed to “not make eye contact, don’t listen to anything”, etc.? And it even worked via radio with Kate, the snipers, etc… And suddenly, Kate wasn’t even interested in the location of the TARDIS anymore? Nor did this head(!) of UNIT say anything at all about WHY she was abandoning Ruby.

Oh, and why did the PM abandon all his plans for buying WMDs and stuff when all other people that had contact with the blurry lady just abandoned Ruby? Where’s the connection here? It clearly wasn’t the reason for the blurry lady as she was still there afterwards.

Also what is it with The Doctor stepping on things? Didn’t the fucking landmine teach him to watch his steps?

This episode was a mess IMHO. Like a fever dream - just that it was never suggested it was one.

On this Reddit thread they suggested SeaFile as their client explicitly supports selective sync. And also MountainDuck which can work with various protocols.

EDIT: Mountain Duck 5 even adds SMB support.

Similar here. As I don’t need multi-user support, I don’t bother with self-hosting some tool.

Bookmarks go to Safari where they’re synced between all my Apple devices and pop up automatically in the address bar.

And long-term bookmarks (news articles, references, etc.) go into Anybox which keeps an offline copy of the website so I can still read it in 10-20 years.

Yeah, the link is completely mangled. Looks like it was supposed to be this:

https://github.com/ish-app/ish

Heute morgen war “Ja” noch in Führung - und da gingen die Curl-Kommandozeilen schon durch die Radbubble…

I’m using OwnTracks to feed my Traccar setup at home.

You know you can basically implement Healthchecks.io completely in Zabbix using zabbix-sender or any compatible implementation of it? (Or find a better way, e.g. querying the timestamp of a logfile or even check the logfile for “OK” or “ERROR” lines… lots of ways possible.)

Google, Bing, and a plethora of others.

For me it’s the other way around. In Check_MK I was constantly writing new custom checks and it was all manual code and overall felt like Nagios on steroids (what it was back then) - just not in a good way.

In Zabbix you can do everything in the UI without messing around in the file system. And things like translating SNMP results to readable text works throughout the system without having to include a Python file and then call it from within your various other checks. All the alerting logic can be clicked together and easily amended in the UI. It’s so much more comfortable once you’ve figured it out.

But these 3 are all about metrics, right? While they’re great to monitor and analyse numbers (ping times, disk space, memory, etc.), they aren’t that great with e.g. plaintext error messages in log files. That’s how I remember it from a few years ago, at least.