• 0 Posts
  • 347 Comments
Joined 2 years ago
cake
Cake day: June 30th, 2023

help-circle
  • So uplink is 500/500.
    LAN speed tests at 1000/1000.
    WAN is 100/400.
    VPN is 8/8.

    I’m guessing the VPN is part of your homelab? Or do you mean a generic commercial VPN (like pia or proton)?

    How does the domain resolve on the LAN? Is it split horizon (so local ip on the lan, public IP on public DNS)?
    Is the homelab on a separate subnet/vlan from the computer you ran the speed test from? Or the same subnet?






  • Servers: one. No need to make the log a distributed system, CT itself is a distributed system.

    The uptime target is 99%3 over three months, which allows for nearly 22h of downtime. That’s more than three motherboard failures per month.

    CPU and memory: whatever, as long as it’s ECC memory. Four cores and 2 GB will do.

    Bandwidth: 2 – 3 Gbps outbound.
    Storage:
    3 – 5 TB of usable redundant filesystem space on SSD or.
    3 – 5 TB of S3-compatible object storage, and 200 GB of cache on SSD.
    People: at least two. The Google policy requires two contacts, and generally who wants to carry a pager alone.

    Seems beyond you typical homelab self hoster, except for the countries that have 5gbps symmetric home broadband.
    If anyone can sneak 2-3gbps outbound pass their employer, I imagine the rest is trivial.
    Altho… “At least 2 [people]” isn’t the typical self hosting

    Edit:
    Tried to fix the copy/paste.

    Also will add:

    https://crt.sh/
    Has a list of all certificates issued.
    If you are using LE for every subdomain of your homelab (including internal), maybe think about a wildcard cert?
    One of those “obscurity isn’t security”, but why advertise your endpoints? Also increases privacy (IE not advertising porn(dot)example(dot)com)


  • This… Except for contactless payment.
    I used graphene for a month. It was lovely. Even things like banking apps worked.
    I don’t care about absolute privacy, but I do care about controlling my privacy. Grapheme gave me that.

    I had only 1 issue.
    Contactless payment.
    It’s extremely convenient to me, from public transport to groceries. I just bop my phone.

    The fact that Google has that locked down surely violates some EU laws. But I’m sure they wave away the laws because of “financial security” or some other bullshit.
    As if bank card NFC/contactless doesn’t suffer exactly the same issues.
    I looked into some “graphene contactless payment” type systems or workarounds, and I couldn’t find anything that would fill the gap.


  • Smaller file size, lower data rate, less computational overhead, no conversion loss.

    A 64 bit float requires 64 bits to store.
    ASCII representation of a 64 bit float (in the example above) is 21 characters or 168 bits.
    Also, if every record is the same then there is a huge overhead for storing the name of each value. Plus the extra spaces, commas and braces.
    So, you are at least doubling the file size and data throughput. And there is precision loss when converting float-string-float. Plus the computational overhead of doing those conversions.

    Something like sqlite is lightweight, fast and will store the native data types.
    It is widely supported, and allows for easy querying of the data.
    Also makes it easy for 3rd party programs to interact with the data.

    If you are ever thinking of implementing some sort of data storage in files, consider sqlite first.










  • Years ago, I played with AWS then contacted their support to make sure any AWS billing to my account was disabled.
    I thought I’d try it again recently, and couldn’t log in.
    I still don’t think I’m missing anything.

    I’d rather have VPS or server providers where I know exactly what I’m getting per month no matter what, tho I’ve ran near data transfer surcharges.


  • Oh, it’s expected costs.
    Like, figure out the compute requirements of your code, multiply by the cost per compute unit (or whatever): boom, your cost.
    Totally predictable.
    Compared to suddenly having to replace a $20k server that dies in your data center.
    So much easier.

    Except when your code (let’s be honest, the most likely thing to have an error in it… At least compared to some 4+ year old production hardware that everyone runs) has a bug in it that requires 20x compute.
    But maybe that is a popularity spike (the hug-of-death)! That’s why you migrated to the #cloud anyway, right? To handle these spikes! And you’ve always paid your bills so… Yeh, here’s a 20x bill.


  • The amount of software that is limited free self-hosted but the next tier of “self hosted” is enterprise and thousands per year is ridiculous.
    Absolutely ridiculous.

    Like, you have self hosted. I like your software, I use it personally and that’s why I’m using it for (and recommending it to) small businesses. They could afford your 10-100 per month for whatever extra features, but they don’t want to rely on 3rd party hosting. They want to host it themselves.
    But the only way to get those features is to go for some “cloud” bullshit they don’t control, or to pay “enterprise” prices.

    It’s why I make part of what I make/charge a contribution to the products and projects I use and recommend.
    I’ll set all that up and tailor it to your company, but anything and everything I recommend/implement is standing on the shoulders of giants. So pay those giants.
    Although I think I’m lucky with the people I work for, in that that are interested in the tech, but not the detail.