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…
mbirth
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.
Da meine Synology einfach nicht stirbt, brüte ich auch schon länger die Idee für den Nachfolger aus. Im Moment ist der Plan, ein TerraMaster F4-423 zu nehmen. Das Ding ist quasi ein Intel NUC + SATA Controller in einem kompakten Gehäuse. Kleiner bekommt man das nicht im Selbstbau. Auf der Hauptplatine ist ein USB-Stick angestöpselt, den man austauschen und dann ein eigenes OS installieren kann.
Und sollte das Ding sterben, kann man die Platten auch an jedem anderen Linux wieder lesen.
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.
No need for reverse engineering - it has already been done: https://github.com/RhetTbull/osxphotos