chiisana

Have you seen OwnTracks?

Not necessarily just yaml — there are things yaml cannot do well, but even ignoring that, traefik can also use toml, or container labels — but rather, the entire concept of infrastructure as code is way better than GUIs. Infrastructure as code allows for much better linting, testing, and version controls thereby providing better stability and reproducibility.

Most providers offer some kind of OS reload and you may be able to use custom ISOs for the process. However, that doesn’t change the fact that if you don’t want to change OS (especially if you’re already using something more commonly seen in production environments like Debian), then you shouldn’t change the OS.

It’s not the protocol, it’s the users. There’s a vocal group that would rather stay small, niche, and remain in obscurity away from the rest of the world. They fear that they’re going to lose their pedestal and megaphone because their quirky skewed view of the world will be drowned out by mainstream worldviews. They’ll then mask it with claims of “privacy”, “EEE”, or “anti-blahblahblah_that_I_dont_like”.

Big companies did wonders for Mastadon’s adoption, and will likely do the same here. The lack of users and content will be resolved when it happens, and I just hope I can hold out long enough until that happens.

Phones learn from what you’re typing. The more you type (typo) something, the more they will recommend it to you. Vicious cycle if it auto corrupts it for you, and you miss it/ignore it thinking the other party will understand you fine. Eventually it learns the ironic typos as actual words and then you’re stuck with them when you type. I kind of wish there’s a way to review / manage the autocomplete dictionaries, but I haven’t tried hard enough to find out yet.

Tin foil hat: Spy phone/app/browser looking at what you’re reading and adding it to your keyboard hints. That particular company was mentioned in a recently linked article about the company triggering an earthquake from fracking in northern BC, as well as being sued by the state of California.

Went shopping recently… literally first time in years. Hopefully this is just a ransomware attack with no exfiltration of data.

I received DMCA from Nintendo in 2015 from dmca@millernash.com which was also confirmed to be legitimate as authorized agents.

Big companies like Nintendo doesn’t have to use their own in house corporate counsel for this kind of enforcement. They can and often do task it out to firms that’ll take on both discovery and take down based on given directive on an agreed rate that’d be cheaper than them doing it in house, so they don’t need to train up an entire department on the skill set required.

The name servers themselves is not part of the equation. The commonality in all those linked are sending emails from Namecheap’s shared hosted email/website, not name servers. Sending email from shared hosted email/website is asking for trouble, doesn’t matter who you’re hosting with, because those IP range are always abused, especially with the larger providers, simply due to a larger exposure. The detection mechanism here is really simple and observable via raw mail headers by checking the Received: line. Filtering emails from this information here is a typical part of the anti-spam model. A typical implementation would be via DNSBL providers such as Spamhaus, Sorbs and alike. The solution is always to use trusted transaction email services to deliver email from the website instead.

That, however, is a very different problem than the dedicated email services like Google Workspace Gmail, because you’d not be sending from your web server’s IP address, but rather via Google’s dedicated range. As such, the Recevied: line is much less likely to yield a match in DNSBLs. Validation for these are then done via the SPF/DKIM/DMARC records on your domain, checking if your configuration permits delivery from server at the Recevied: line (look for Received-SPF) and whether or not you have the appropriate signing (look for Authentication-Results: and bits about the various stages of DKIM and DMARC).

No it does not make any sense. There are literally thousands of domain registrars out there; almost every single last one of them will offer free DNS service with registration. Also, more specifically speaking, DNS provider host provider look up is not even part of email delivery flow.

The most well known spam registrar is GoDaddy as they spam ads everywhere, and everyone and their third cousin’s dogs know about them. NameCheap is a large registrar but isn’t that big of a fish comparatively speaking. But, regardless, blocking any registrars that size the way you’re describing would break way more businesses and hurt the recipient provider’s own reputation. This honestly starting to sound more and more like a smear campaign as opposed to anything grounded in actual technology.

I don’t understand how this could be the issue.

If you’re using Google Workspace, Google will give you the appropriate DMARC, DKIM and SPF records to add to your DNS. The NS themselves should resolve the records and provide the recipient server with the values you’ve entered, thereby ensuring delivery.

Does the free DNS on NameCheap no longer allow certain types of records? Aren’t those mail specific DNS records all just TXT/CNAME records now (no more weird legacy SPF record type), which are fairly basic and typical?