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.
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.
Google, Bing, and a plethora of others.
Also: SpotNet (with e.g. SpotWeb as a client)
I believe it’s often because nobody does their own website anymore but instead uses managed services, e.g. Medium. Or bits of information, that would’ve been worth a blog post some while ago, end up on sites like StackOverflow, Reddit, etc… And once these services want to monetise these contents, they usually start with limiting public access.
And OTOH TikTok, Instagram Reels and YouTube Shorts are doing everything they can to further limit people’s attention spans and get them addicted to those services. So the people capable of and/or interested in producing proper “content” are dwindling, too.
Especially gas-powered as they can then rev them all the time, raising the annoyance to completely new levels.
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/
I think that already happened and was called “The Fappening”. You can still find it with Google.
Money. It’s much better if you can sell the same thing over and over again.
Maybe they delete enough code to be able to give us a third “theme”.
For reverse image search, Google is also becoming more and more useless. I usually also look on Yandex to identify fake profiles using photos of other people.
Part of the experience to me is reading all the comments and leaving my 2¢. So I’m using the Share → Embed workaround so far.
What’s next? Do they maybe also want landlords to cancel renting agreements over this? Supermarkets to not sell to these people?
Instead of the full-blown Mastodon, you should also look at #GoToSocial which is compatible and pretty light-weight. (Doesn’t come with a web UI, so you need to use client apps.)
Pretty much, I think. I have it running on a Raspberry Pi 4 with docker-compose:
version: '3'
services:
gotosocial:
image: superseriousbusiness/gotosocial:latest
restart: unless-stopped
networks:
- traefik-public
environment:
TZ: Europe/London
GTS_HOST: xyz.example.com
GTS_CONFIG_PATH: /gotosocial/storage/config.yaml
GTS_DB_TYPE: sqlite
GTS_DB_ADDRESS: /gotosocial/storage/sqlite.db
GTS_LETSENCRYPT_ENABLED: "false"
GTS_LETSENCRYPT_EMAIL_ADDRESS: ""
volumes:
- smb-gotosocial-data:/gotosocial/storage
labels:
traefik.enable: "true"
traefik.http.routers.gotosocial.rule: Host(`xyz.example.com`)
traefik.http.routers.gotosocial.entrypoints: websecure
traefik.http.routers.gotosocial.tls: "true"
traefik.http.routers.gotosocial.tls.certresolver: le
traefik.http.services.gotosocial.loadbalancer.server.port: "8080"
volumes:
smb-gotosocial-data:
driver_opts:
type: "smb3"
device: "//mynas/docker/gotosocial/data"
# Use nobrl to mitigate SQLite3 byte range locking issue on CIFS/SMB mounts
o: "rw,nobrl,vers=3.1.1,addr=172.16.254.1,username=xxx,password=xxx,cache=loose,iocharset=utf8,noperm,hard"
networks:
traefik-public:
external: true
At least in Germany, many of these copyright claims have no real legal grounds and wouldn’t hold up in an actual trial. All cases I’ve read into so far ended with a settlement - as the private person was too afraid of even more legal fees. Or were dropped completely after a while (full of empty threats) if the people never engaged with the other party.
DMCA is only valid in the US. Those other countries obeying it are usually just doing it to avoid trouble, but there’s no real legal obligation. (But if ignored, it is pretty safe to assume that any bigger company would look into local laws and try to find a different way.) But from what I’ve heard, hosters don’t just close your account because of some DMCA. They will actually look into it and work with you to solve it.
And in the end, you could simply host it on a Raspberry Pi at your home. The ISP can’t be held responsible for the data you transfer, so they won’t just shut down your Internet connection. And if you get a strongly worded letter from some company, you can send it directly to the recycling bin.
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.