Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)L
Posts
12
Comments
1501
Joined
3 yr. ago

  • Unfortunately all the volume-based email providers I know (Purely, MXroute, Migadu) are one or two-person operations. Doesn't stop them from being excellent, of course.

    I wish the volume-based pricing model was more popular but unfortunately very few people know about it, and is course the large providers prefer to charge by account or add all kinds of artificial limitations because they make much more money that way. Having multiple mailboxes for the same domain costs the provider nothing and yet you get charged per mailbox.

  • Use a volume-based email provider like MXroute, where you pay strictly for the resources you consume (storage space and mails sent) not made-up limitations like number of accounts, aliases, domains etc. that cost the provider nothing.

  • Rechargeable AA batteries are a thing. I use them in everything: mouse, toothbrush, clock, controller, torch, electronic scale, milk froth wand etc.

    Whenever a device runs out of juice I pop fresh batteries in the device and pop the depleted batteries in the charger.

    It's great. Charge lasts much longer than chemical batteries and they work for many years. I wish everything used rechargeables.

  • The graduation from Linux from Scratch is to be able to make your own mini-distro. I reckon anybody who gets that far is above petty feuds about the install process or packaging in this or that distro.

  • Yeah I know. Derivate distros are cool only if they don't stray too far from Arch. How dare a distro do something different.

    Keep it up, it's a super cool look (and healthy) for a distro to hate on its own downstream.

  • Don't forget shitting on Arch-derived distros.

  • Then why do they offer a separate, distinct DDoS mitigation feature on the enterprise plans? And did you notice they call them "mitigation" and not "protection"? 🙂

    Look at the description of each one, the free one "stops illegitimate traffic at the edge". Meaning they'll serve from cache, it's not getting through to your actual site. You can get caching from any CDN service, it doesn't have to be CF. All CDN services are distributed and will try to serve for as long as possible because their whole purpose is to deal with traffic spikes.

    And if you want to know for how long CF (or any service) will serve from cache and how far they'll go for an account (especially a free account), you want to check the terms of service not the plans. The plans are made to sell to you, the fine print is in the terms.

    Anyway, I really don't understand people's obsession with DDoS, particularly self-hosting people. The chances of their little website ever being the target of a DDoS are astronomical. Many of them don't take proper backups, and don't worry about theft or fire or electric spikes, which are far more likely, but go frantic when they hear about features they'll never use.

  • Use your common sense. They're not going to expend any significant resources to keep up a free website.

    They have a small capacity available for mitigating DoS for free accounts together, while resources last. If you happen to fit in that capacity at any given time that's nice, if you don't, you go down.

  • If anything ever happens that involves [the lack of] DNSSEC or CAA you'll have to buy another domain because the old one will be on every block list.

  • As a workaround for Windows you can sync files to a Linux machine with SyncThing for example, and use Borg there.

  • Make your website all static files (if you can) and host on a CDN like Bunny.net. It's $1/month and your website might actually be able to get through some large traffic spikes. It won't work against a targeted sustained DDoS but like the other comments said that's not likely to happen.

  • You don't have to worry about DDoS:

    • DDoS is an advanced technique and the people who can do that spend a lot of time and effort putting malware on machines that can be ordered to perform DDoS on command. They usually sell that attack capability and it ends up getting used against worthy targets, we're talking attacks that disrupt entire industries, elections, warfare etc. Do you really think what you'll be hosting will attract that kind of attention and be impossible to take down with simpler methods?
    • To survive a DDoS attack you need a lot of resources, from a professional platform (like CloudFlare). The stuff they offer for free is not going to get you through a DDoS. If you'll read their terms you'll see it's worded just ambiguously enough to mean nothing. If you ever actually get targeted by an actual DDoS and you haven't paid a lot of money to a platform like that, everybody will simply drop you instantly (your ISP, your VPS provider, your tunnel provider, your VPN provider etc.) and possibly kick you off their service too.

    If the stuff you'll be hosting is static files you can use a CDN service. CDN's are designed to be distributed and redundant so they're somewhat resilient to DoS attacks by default. They'll still kick you off if it gets to be too much but maybe you can weather shorter/moderate attacks.

    If you're hosting a dynamic/interactive service forget about it.

  • Does Kore make the Netflix app stream to Kodi?

    Even if it does, I can't exactly make everybody who comes by install an app to be able to stream to my TV. Everybody (who's on Wifi) can stream to the Chromecast.

  • CAA and DNSSEC aren't obscure. I would not even consider managing any domain nowadays without them.

    Neither are ALIAS/DNAME/HTTPS, which you'll be running into more and more in the future if you haven't already. You could argue there are multiple competing standards at work there but Afraid doesn't implement any of them.

  • Try Claws Mail too while you're at it, if you're on Linux. Most powerful email client on Linux, with everything OP mentioned (some of it available as plugins, but your distro should install those too).

  • If you don't need CI/CD I'm not sure why you need a centralized frontend at all. Git itself is distributed and you can setup any code flow you can think of. It has hooks that can be used to set up code quality checks on select branches. There are local history browser apps for every platform and IDE plugins.

    A frontend is no substitute for developer communication — usually what the "PR" thing does is sugarcoat the fact the devs don't know how to use Git and/or don't talk to each other.

  • In polls the demographics of the participants are selected so they are statistically significant.

    When you poll visitors to a website there's no telling what biases might be at work. For example, Arch is a popular distribution so its prevalence in the results could simply be an indicator of that.

    Last but not least, correlation does not necessarily mean causation, and that goes especially for an uncontrolled sample. There's a famous example that says "100% of the people who drink water die after that".