escalt

Spam filtering on your own mail server is easy. 99% of spam are generic automated E-Mails that are sent in bulk with lots of spoofed metadata (domain, sending address, date, etc.). I have an address on a domain that used to be hosted by a third party and it got tons of spam. At some point I moved the domain to my own server with mailcow, and it blocked the vast majority of spam out of the box with no false positives. It uses rspamd, not sure if they have a tweaked config for it or something

Generally I really like mailcow. It makes dealing with all the ugly parts of hosting E-Mail fairly simple

Also worth noting that good bitcoin wallets automatically use a new address for every transaction, so you never end up reusing an address.

To me, (home) automation is not (only) about saving a total amount of time. It's about saving time at the right moment. When I have lots of free time, I will happily spend it refining my home automations. It's a fun hobby and simple programming with things that you can actually see and touch. But when I just got home from a stressful day at work and have to hurry to some other appointment, saving a few seconds here and there can actually be very valuable. As long as all your "smart" stuff can't access the internet it's great.

Sorry for the late reply, I use https://github.com/tulir/mautrix-whatsapp as bridge for my Matrix server. You need your own server to install this bridge. The easiest way to do all this is with https://github.com/spantaleev/matrix-docker-ansible-deploy, which takes care of many things

The cool thing about Syncthing is their public network of community provided relay servers https://relays.syncthing.net/

When two devices can't find each other on the local network they look for each other on public discovery servers and then pick a community provided relay to connect. The data is end-to-end encrypted between both devices, so the relay doesn't see the file contents. This works out of the box on almost all networks. Unfortunately IPv6 doesn't seem to work with their public relay network though...

I am bridging WhatsApp to my Matrix server. On Matrix it shows the username when the number is not in your contact list, and only then did I notice how unnecessary access to the contact list actually is (as long as you don't start new chats with people)

Snowden didn't tell much about war crimes. He was the guy that unveiled just how large the NSAs operations are and what they are capable of. And it was very effective, because since then there was a big move towards encrypting all communications. Nowadays it's almost standard to have end to end encryption in messengers, and the majority of websites support https or are even https-only

As far as I know Chinese (Mandarin) is actually very easy to talk/understand since it has very simple grammar. The reading/writing on the other hand takes a lot of dedication. At least that's what someone learning Mandarin told me

I'm absolutely no expert on this, but I think your provider would usually filter this spoofing attempt out, just like with IP spoofing. But if you're in the right spot in the network (e.g. your provider doesn't check for spoofing or you're your own "provider") you can do whatever you want.

Another problem with Android could be that the operating system might not have enough control over the SIM-Card/Modem to spoof phone numbers.

I have heard about people using some services to send/call from spoofed numbers though

Kind of weird that a page about cryptography has broken https

It would be great if offering public IPv6 only services was viable, but according to Google statistics (https://www.google.com/intl/en/ipv6/statistics.html) you're still cutting off about two thirds of potential users.

Using SLAAC is the way to go in most cases. DHCPv6 should only really be used when you have a network that is for some reason smaller than a /64.

In my opinion you shouldn't really bother with compatibility. Just do dual stack and maybe NAT IPv4 if necessary.

For my personal use cases IPv6 just proved to be much more versatile than IPv4. It did take some getting used to since it's approached differently, but learning it is very worth it and also helps using IPv4 better

I guess I don't have as much low level experience as you do, but in my eyes IPv6 is literally just IPv4 with more bits. Due to the increased number of possible addresses, IPv6 is used with some different (better) concepts than IPv4. For example having (very likely) unique local networks (ULAs) is amazing when you happen to merge previously independent networks together or do some VPN stuff. You pretty much never have to calculate subnets because you'll likely never run out of addresses. And even if you somehow manage to do the impossible and fill up a /48 ULA (at which point you would have died from NATing billions of entire IPv4 address spaces with multiple layers to somehow make it all one network on IPv4), it takes just two seconds to generate a new one.

Also getting an entire public prefix assigned instead of just a single address is amazing too. On my public servers I let my ssh service listen on a randomly generated static IPv6 address from my prefix, which is not used for anything else. On that same machine I can have dozens of other public services on their own IP each (they can even all run on the same port because they're using different addresses), and when someone then decides to scan the IP of my website for interesting ports, they won't find anything.

To be honest, if someone doesn't understand IPv6, I doubt they really understand IPv4 either. Many issues with IPv6 today come from the fact that everyone and everything is so used to V4 concepts, that most products focus on IPv4 first and then half-ass IPv6 support (if they implement it at all).

Telegram keeps talking about how private and secure it is, but all group and private chats are not encrypted by default. Its end to end encrypted chats are very limited (only direct messages and only on one device) and rely on self-baked crypto. Their voice chat is also almost definitely not end to end encrypted, as I'm not aware of a way to do e2ee voice chat with many participants without linearly increasing bandwidth requirements for users

I think that's mostly because only one short message was encoded with it (and it contained errors!). Would he send unique messages daily or write an entire book with it, I'm sure it would have been cracked much faster.

With Jellyfin (more geared towards movies than music) you can use your clients as a remote for another currently playing client

macOS has barely functional OpenGL support and no Vulkan support at all. Most of the value of Proton comes from the DXVK project (aside from Wine itself), which is a D3D->Vulkan wrapper. In theory it could be combined with MoltenVK, which wraps Vulkan to Apples Metal API. Chaining two graphics wrappers like that is probably fairly error prone and the losses in performance are likely too high to make it applicable for video games. Additionally ever since Apple ditched 32 bit support, Wine became kind of useless on Macs since a lot of Windows software (especially older games) is x86 only. The announced move to ARM further decreases chances of Proton ever officially supporting macOS, as emulating x64 would be way to costly to play modern video games.