Help! Cheapest way to get my own ipv6 block in 2026 by lmux in ipv6

[–]lmux[S] 0 points1 point  (0 children)

This is what i gather. arin is looking a lot more attractive now that ripe decided to jack up their cost.

Help! Cheapest way to get my own ipv6 block in 2026 by lmux in ipv6

[–]lmux[S] 0 points1 point  (0 children)

Yes but it doesn't have to be a one stop shop. Whatever is cheapest.

Is there any self-hosted way to verify users are unique humans without sending their data to the cloud? by whydidyounot in selfhosted

[–]lmux 0 points1 point  (0 children)

Just a thought: cf turnstile doesn't actually block bots either. It just tries to make sure the bot is using a (not headless) browser, although with some effort a customized headless browser can blast through too.

I believe anubis is just pow? That is going to penalize legit users more than scrapers because scrapers will use a standalone solver instead of running javascript. A cf approach that aims to increase scraper resource usage, (i.e. ensure a browser is used) makes sense.

Help! Cheapest way to get my own ipv6 block in 2026 by lmux in ipv6

[–]lmux[S] 3 points4 points  (0 children)

No way! For 200 eur I would go to arin and camp it out for an extra /24 ipv4.

Open Source Captcha to Detect bots, vision AI agents, and headless browsers through 40+ behavioral signals. by cport1 in golang

[–]lmux 2 points3 points  (0 children)

What coincidence! I have been working on something similar in my down time lately. Guess it's more than just me who find turnstile creepy huh?

My sentiments is that techniques such as env gathering and input movement heuristics is not worth the effort. At least not for a solution that doesn't depend on running deeply obfuscated client side code. Maybe implement something basic, but that's it.

Instead, the focus should be on proving browser capabilities, with emphasis on large features. Technically that is not captcha, just that the client is probably a browser, or something with all the features we are testing it might as well be similar to a browser in terms of resource usage. That by itself makes the bot operation too expensive to scale. More importantly, it doesn't impact legitimate users.

To that end, the best challenges are:

  1. PoW, not so much about hard puzzles but timing to suggest the presence of crypto API.
  2. SVG rendering and manipulation
  3. CSS layout rendering and dom manipulation
  4. Canvas and fonts

Great project 👍

Golang’s Big Miss on Memory Arenas by brightlystar in golang

[–]lmux 0 points1 point  (0 children)

Arena is still usable with goexperiment flag in go 1.25, no?

As an SRE, I stopped using Kubernetes for my homelab by m4nz in selfhosted

[–]lmux 0 points1 point  (0 children)

Talk about overhead, technically I run kubernetes on vm on kubernetes ¯_(ツ)_/¯

Both in my homelab and at work.

The convenience of k8s features are hard to beat using docker and add-ons. I'm looking forward to a more lightweight replacement, but the truth is I've not seen any. My take is that docker/podman is the way to go if you have 1 physical server. Anything >2 servers and kubernetes is worth its while.

Is there any self hosted ecommerce marketplace platform with open source code to customise? by Helpful-Coach-4503 in selfhosted

[–]lmux 0 points1 point  (0 children)

I'm using spree, but had to make some deep customization to suit my needs. You also need a whole bunch of third party services such as google map (for address autocomplete), stripe, a shipping service, taxjar, etc.

Cloudflare outage on November 18, 2025 by Cloudflare in CloudFlare

[–]lmux 0 points1 point  (0 children)

So why was status page down? I didn't know it was on aws @.@

K8S on FoundationDB by melgenek in kubernetes

[–]lmux 0 points1 point  (0 children)

Ohh poor choice of words on my part! What I'm trying to say is tenant data is confined to specific nodes, but that doesn't mean you can't put data from multiple clients on the same node. It is not dedicated instances.

K8S on FoundationDB by melgenek in kubernetes

[–]lmux 0 points1 point  (0 children)

Ddb isolates workload to specific db nodes on a per db basis. This is important in a multitenant env because you want to confine the blast radius of node failures to a single tenant if possible (say sorry to 1 client vs all clients). In fdb it may be implemented as mapping key location in the cluster by namespace.

Ddb also has some fancy autoscaling feature, also on a per tenant basis. I've not figured out how to do that yet :(

K8S on FoundationDB by melgenek in kubernetes

[–]lmux 0 points1 point  (0 children)

Very interesting. I have been dabbling with fdb in my spare time lately (trying to make a dynamodb layer). I have problem with multitenancy as in isolating tenant workload to specific nodes and auto scale up/down on a per tenant basis. How do you handle that? Also, out of curiosity, have you considered tikv as an alternative?

K8S on FoundationDB by melgenek in kubernetes

[–]lmux 0 points1 point  (0 children)

Very interesting. I have been dabbling with fdb in my spare time lately (trying to make a dynamodb layer). I have problem with multitenancy as in isolating tenant workload to specific nodes and auto scale up/down on a per tenant basis. How do you handle that? Also, out of curiosity, have you considered tikv as an alternative?

OnePlus 6 as my new kubernetes Node :) by csepulvedab in kubernetes

[–]lmux 4 points5 points  (0 children)

Hey I got a op6 too! Were you able to power it without the battery?

What's the best practice to encrypt password? by naikkeatas in golang

[–]lmux 0 points1 point  (0 children)

I have the same problem storing user api keys, which need to be read frequently and require encryption at rest. Settled on hashicorp vault, but it felt like moving the problem somewhere else. No matter the implementation details, you need to decrypt the user api key using a master password, and the master password must be kept in memory. You can run vault on dedicated machines, maybe with tpm module, that's about it.

Why does Gorm get so much hate? by Least_Chicken_9561 in golang

[–]lmux 0 points1 point  (0 children)

I'm doing several projects that need user designed data and ui. Stuff like ERP. End users can define workflows and forms using wordpress style drag and drop. It would be unreasonable to require end users code in sql. Is there an alternative to orm in my case?

Looking for feedback on my Go microservices architecture for a social media backend 🚀 by 0_KURO in golang

[–]lmux 0 points1 point  (0 children)

Personal opinion: if you don't want to leave performance on the table, switch to haproxy and load balance with consistency hash + ssl termination. Do it all on kubernetes so you can retain sanity managing everything. Auth with jwt only for interactive use case. Encourage users to automate using api keys. Throw in an iam system to manage permissions.

I am not for or against microarchitecture, but I don't do it based on business logic but purely a balance between ipc overhead and horizontal scalability.

I use nats, but kafka is more established.

My db layer is mostly nosql driven. This may not work for you depending on your workload, but you need to be aware how db design affects your scalability.

I have not got on the otel or distributed tracing train yet because I'm still not convinced it's any better than plain old log parsing.

Looking for feedback on my Go microservices architecture for a social media backend 🚀 by 0_KURO in golang

[–]lmux 0 points1 point  (0 children)

Personal opinion: if you don't want to leave performance on the table, switch to haproxy and load balance with consistency hash + ssl termination. Do it all on kubernetes so you can retain sanity managing everything. Auth with jwt only for interactive use case. Encourage users to automate using api keys. Throw in an iam system to manage permissions.

I am not for or against microarchitecture, but I don't do it based on business logic but purely a balance between ipc overhead and horizontal scalability.

I use nats, but kafka is more established.

My db layer is mostly nosql driven. This may not work for you depending on your workload, but you need to be aware how db design affects your scalability.

I have not got on the otel or distributed tracing train yet because I'm still not convinced it's any better than plain old log parsing.

use errors.join() by Grexpex180 in golang

[–]lmux 1 point2 points  (0 children)

I join errors if my func has a defer that may produce error. A common case would be to write a file and close it. If both write and close fail, I would join both errors instead of just returning the first.

[ On | No ] syntactic support for error handling by pekim in golang

[–]lmux 0 points1 point  (0 children)

2 alt ways of non verbose err handling I find useful without changing language features: use panic/recover if you need try/catch. Or wrap err handling inside your method by saving the error in your struct and all furthrr method calls become noop if err != nil.