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.
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:
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.
Also: SpotNet (with e.g. SpotWeb as a client)
Because it probably was an ID10T problem?
This! Wipr on phone and Mac. Pi-Hole in my home network.
And for annoyances there’s also Consent-O-Matic and SponsorBlock installed.
Apart from the SMR vs. CMR, if your NAS will run 24/7 you need to make sure to use 24/7 capable drives or find a way to flash a 24/7-specific firmware/setting to a consumer drive. Normal consumer drives (e.g. WD Green) tend to have a lot of energy saving features, e.g. they park the drive heads after a few seconds of inactivity. This isn’t a problem with normal use as an external drive that only gets connected once in a while. But in a 24/7 NAS the drive will wake up lots of times and park again, wake up, park again … and these cycles kill the drive pretty fast.
https://www.truenas.com/community/threads/hacking-wd-greens-and-reds-with-wdidle3-exe.18171/
Money. It’s much better if you can sell the same thing over and over again.
deleted by creator
No need for reverse engineering - it has already been done: https://github.com/RhetTbull/osxphotos