It's with ample RAM and the latest Intel CPU. Assuming the whole thing draws 100W, that's also including 72kWh of electricity.
3,618 karma · joined March 16, 2017
If the .com prices were to be increased, there will be a huge backlash. As for .bananas, not so much.
.bananas might get blocked at TLD level, .com unlikely so.
My tips would be:
- Use Markdown. It makes writing so much more faster and takes away the focus from markup.
- Do not focus too much in the technical details. Content is still the king.
- That said, make yourself familiar and follow great typography patterns in your blog. Use legible fonts faces and sizes, clear separation, hierarchy, etc has the best impact.
- Have your email address visible. I find it be more effective than contact forms. You will get all sorts of feedback, but you can still decide if you want to respond to them. In my experience, people who take the time to compose an email tend to provide constructive and generally positive feedback.
- Decide a "tone" that you want to follow. For example, I have my technical content separate from personal, and travel content separate from the rest. It's sometimes refreshing to be able to speak in different tones.
- Be open about what you expect from the blog as well. If you hope to land in a better job, saying it openly won't hurt.
Well that's the thing... You don't. It's a very passive approach if you are actively looking for a job.
Posting solutions to interesting challenges you come across has a lot of potential getting asked to interview for jobs that solve similar problems. A generic article about "top 5 Gen AI projects" will be fruitless, but a post about how you practically "abused ramfs to make database tests 5x faster" might be.
But in RAW/JPG world, the metadata and edits is already a solved problem with Sidecar files + EXIF data. Sure, EXIF fields are kinda messy but I'm sure it's better than Apple has rolled by their own.
- https://github.com/openssl/openssl/issues/7482
From query statistics, I see that around 15% of the queries are for HTTPS records, 30-35% for A and AAAA records, and the rest for RR types like NS, TXT, etc. Browsers make HTTPS requests in addition to the A/AAAA, so this makes sense.
In an ideal world, the ipv4/ipv6hints do the job if A and AAAA records, so a browser will only need to make an HTTPS request.
PHP added JIT in 8.0, and these math-heavy tasks can take advantage of it. It's not trivial to fine tine JIT configuration though.
In PHP 8.4 (scheduled Nov 2024), there is a major upgrade to JIT as well.
Rebase/reset are major and first class features of Git. It's only wrong if you work with a team that expect the centralized server to be consistent.
GitHub owned by MSFT aside, and also putting their AI push _also_ aside, GitHub has things like Sponsors, Dependabot, and code scanning that you won't find anywhere else. They sure are luring you into ecosystems that require a huge escape velocity, but GitHub serves as less-friction entry point to open source software.
GitLab self hosting is also nice and flexible, but it has a more "enterprise open source" feeling to it. Debian and Drupal can take advantage of it, but I don't see myself hosting mini projects like my mini CSS library that is also used by three other strangers.
Source Hut is really nice too. Admittedly I don't like email based workflows, so I haven't really thought about moving anything there. But Source Hut has "unlisted" repos, which I thought was really clever and missing from other forges.
I don't see any advantage of layering HTTP/3 here. It adds more friction, and the only advantage it brings is being able to "hide" the SSH server over a URL path. I guess x.509 certificates would be fine, but SSH hostkeys, SSHFP or TOFU is enough and far more secure (because it implicitly pins the server public key).
It's a relatively new project from the looks of it, so I'd definitely not use it anywhere half important having to create something interesting with QUIC and HTTP/3.
For browsers, there are extensions that can create SVG screenshots. They work by either copying or inlining CSS into the SVG. They don't work all the time, but worth giving a try first.
For Firefox, see https://addons.mozilla.org/en-US/firefox/addon/svg-screensho..., it worked relatively well for me.
- OCSP servers to query TLS certificate validity. This is necessary because I have configured my web server to staple OCSP responses. (`e1.o.lencr.org`)
- Software repos (apt, dnf, etc). `livepatch.canonical.com` being the top contender.
- GitHub
The only place that TXT records are used in the very popular use cases would be an email server. SPF, DMARC, and DKIM all piggy back in TXT records. I would also imagine a lot of Microsoft stuff like AD use DNS .
// insert some clever "you are the product" here.
It downloads a text file maintained by someone at a repository that lists all uBO YouTube Fixes, and compare it to the latest YouTube JS files. Not all JS updates contain anti-adblock codes, so what this website shows is pretty misleading.
Addon sideloading is only possible on Firefox Developer edition (which I use, so it didn't bother me much).
I'm very aware that I'm in a bubble with my peers, so these are certainly opinionated.
I would pick Postfix because it's more maintained, and what most of my peers use it too. It's a PitA to configure, but there seems to be many resources online. Most of the configuration are quite common, so that one-time configuration is manageable.
Exim is pretty robust too. I don't have a strong reason to not use it, except that I don't have many close peers who use it. Really nice configuration. If you have a multi-tenant setup, Exim would serve better.
Qmail, despite being unmaintained, is praised for being quite secure. I suppose it's the low number of CVEs.
There is also msmtp that provides sendmail compatibility, but uses an external smtp server (like AWS SES) to send the actual email. This is what I use when the server I'm sending from has low IP reputation but I don't want to change my app to use a REST API to send email.
I send a couple newsletters (one tech related, other for marketing for a coffee shop/bakery I own), and it was fairly easy to land on inboxes. Now, I don't know with a 100% certainty that they were delivered, but if DMARC records and bounces are anything to go by, self hosted emails aren't all that hard.
When you buy a VPS, it helps to check if the IP you receive is already blacklisted. After that, it's easy to use some outside service to monitor DMARC responses and blacklist. There are about 40 black list databases. My domains and the IP address are on none of them.
Npm already does it at the package registry with ignore/npmignore files, and that's the package authors choice. How much storage can you really save? 50MB? 200MB? is it really worth the risk of running rm on some glob pattern and cross your fingers the packages don't require any of the deleted files?