Readit News> I’m sorry, but I can’t comply.
> Good luck.
The follow up around 2016: https://twitter.com/royvanrijn/status/788436253532426241
> Nothing happened, never heard from them again...
I couldn't find the code anywhere on his Github profile, so not sure if he actually took the step to publish the code.
If you want to DIY a container with unix tools, this should help: https://containers.gitbook.io/build-containers-the-hard-way/
On the server where I need to run that site, I just transfer the tar, load the image and run the docker image. It's so straightforward I much more prefer this way than being dependant on external registry sites for deployments.
So will SpamGourmet[2].
Of course the problem with all these services is that you're giving yet another third party access to your communication and giving up your privacy to them.
They are all, as far as I know, completely unaccountable regarding what they do with the information they get from your private communication.
No matter what they say in their privacy policies, press releases, or PR, there's no way (as far as I know) to reliably verify any of their claims.
That said, I'd still rather deal with a company which at least claims to respect privacy rather than one that (like Facebook or Google) either spit on it or make money off tracking me and datamining everything they can about me.
[1] - https://www.fastmail.help/hc/en-us/articles/4406536368911
Masked Email gives you more privacy (the identity behind the receiver is unknown) and with data breaches, there's is no login data leaked.
Duck's Email Protection does also remove trackers from the forwarded mails. So senders can't trace back whether you have opened the mail. I hope they also remove click trackers, but I am unsure how they would implement that technology with the referral codes in the URL.
Seems LE is pretty busy right now, got time outs flying around every where.
I have used both and stuck at Plausible. A few reasons (subjective):
1. Plausible is GDPR compliant by default, it has an effective way to measure analytics throughout the day without cookies
2. It is simple and that's key. I don't need to know much, Plausible just gives me that
3. It's fairly lightweight. Matomo is quite heavy and as my VPS'es are pretty much scaled down, less is just more
4. The Plausible self-hosting doc is centered around Docker, which is the architecture I use myself and is set up in literally a few minutes
Please consider bitwardenrs is a 3rd party implementation, indeed community led, so it lags several features which have been introduced by Bitwarden itself.
See the full list of feature requests in the Rust implementation here [1], but the two things I'll miss most are Emergency Access and now this feature called Bitwarden Send.
Autofill is relatively poor (it fails even on HN!). Also, Lastpass has a convenient timed expiry that doesn't work (well) on Bitwarden (BW will expire the login when the browser is closed).
All in all though, I do support the recommendation, in particular, because Lastpass works extremely poorly on Firefox (at least, that's what caused my switch some time ago).
Autofill is much more customizable than LastPass afaik. You can both define how (domain)name matching should occur as you can have multiple entries to match.
This means you can have instagram.com (as website) and androidapp://com.instagram.android (as app) which will use the same autofill entry.
If you configure name matching correctly, any site should be able to provide autofill. My HN entry does match with news.ycombinator.com with default matching settings. But matching settings include hostname / domain name / starts with and even regex!
> Also, Lastpass has a convenient timed expiry that doesn't work (well) on Bitwarden (BW will expire the login when the browser is closed).
You can specify BW timeout settings. Even further, you can define if BW should lock the session (only a password is required to unlock) or if a sign-out is required. With a sign-out, you also need to provide your MFA if applicable.
Time outs can happen directly (after autofill), after an amount of time (1/5/15/30 minutes or 1/4 hours) or upon closing the browser.
So tbh, there is plenty to configure Bitwarden to suit your needs.
The real reason most websites disappear is a much more human one.
So true.
I have had a blog running since 2006, all was php based back then with (html) posts inside a database. The tooling shouldn't be a problem, I switched systems several times (once every few years).
Currently on Hugo with markdown posts. As long as you treat your migration carefully and take some time to migrate, every tool should suffice. It's mostly about human effort and human error when things get lost.
I don't use comment forms, as they are a headache to maintain over the years. I used to have comments but removed them and discussions move to other media (HN, Twitter, Reddit). For analytics I use Plausible [1], self-hosted, and that's fully GDPR compliant.
I live in the EU (NL) and the server is located in AMS3 for DO. This setup runs perfectly fine for me for several years now.