HNHacker News
TopNewBestAskShowJobs

airocker

278 karma · joined August 24, 2018

submissionscomments
airocker··on The "AI 2027" Scenario: How realistic is it?
I want to bet 10 million that this won’t happen if anyone wants to go against my position. Best bet ever. If i lose, i don’t have to pay anyways.
airocker··on How Discord stores trillions of messages (2023)
They could use vitess, citus or alloydb. They could use read replicas for read operations and single master in a shard for write. They would get many SQL features (upgrades, referential integrity etc) for free. It would allow them to extend their business logic considerably.
airocker··on How Discord stores trillions of messages (2023)
Just wondering if anyone considered using Postgres or another relational db. I understand it won’t do multi master replication as well but it is much more stable and predictable if you give it right amount of traffic. I guess the team had to do that part anyways for ScyllaDB
airocker··on Serverless-registry: A Docker registry backed by Workers and R2
Is there a registry that would work on extremely cheap disk storage if the use case if only push and very infrequent pulls?
airocker··on Helen Fisher, who researched the brain’s love circuitry, has died
RIP. She should be credited when someone at OpenAI introduces the concept of hormones to neural networks.
airocker··on Show HN: PgQueuer – Transform PostgreSQL into a Job Queue
We use a garbage collector to error restart if a job is not served within a specified amount of time.
airocker··on Show HN: PgQueuer – Transform PostgreSQL into a Job Queue
We use a garbage collector to error restart if a job is not served within a specified amount of time.
airocker··on Show HN: PgQueuer – Transform PostgreSQL into a Job Queue
Great observation, I wrote a little wrongly. What we want ideally is guaranteed delivery to one random free worker. Uuid strategy is better than locking but this could mean that if one worker gets a longer job, all the others on this worker are delayed even if another worker is free.
airocker··on Show HN: PgQueuer – Transform PostgreSQL into a Job Queue
Thats exactly what we do but taking a lock takes 1 RTT to the database which means about 100ms. it limits the number of events receivers can handle. IF you have too many events, receivers will be just trying to take a lock most of the time.
airocker··on Show HN: PgQueuer – Transform PostgreSQL into a Job Queue
We use listen notify extensively and it is great. The things it lacks most for us is guaranteed single recipient. All subscribers get all notifications which leads to problems in determining who should act on the message n our case.
airocker··on Panic at the Job Market
A different take: All companies are built on relationships. Large companies are a form of nepo companies where you get paid for a relationship to the management chain.
airocker··on Microsoft insiders worry the company has become just 'IT for OpenAI'
This is so true! Going after the pie in the sky only works for a short while, then you have to work for your pie. the worst is that employees in windows used to get slower promotions than these new tech groups (live,mobile etc ) which means more of them are in powerful positions to continue this trend. They tasted success with this strategy in their early days when they built sq L, xbox and word. Azure was the last successful play like this but at least they wrote own software.
airocker··on Ask HN: Why do message queue-based architectures seem less popular now?
I think dbs like etcd mongo Postgres all have some notion of events and notifications. The only drawback is that you have to still poll from the ui if you use these. This is sufficient for most use cases. If you want real time updates, Kafka provides long running queries which keep Kafka still relevant.
airocker··on Run0, a systemd based alternative to sudo, announced
If we forget how the current system is architected, we are looking at two problems: First problem is that Linux capabilities are also dealing with isolating processes so they have limited capabilities because the user based isolation is not enough. Second problem is that local identity has no relation to the cloud identity which is undesirable. If we remove user based authentication and rely on capabilities only with identity served by cloud or kubernetes, it could be a simpler way to do authenticating and authorization
airocker··on Show HN: An SQS Alternative on Postgres
I think it will be better if you create events automatically based on commit events in wal.
airocker··on Run0, a systemd based alternative to sudo, announced
Good software hides complexity. User does not have to understand user group permissions suid etc etc
airocker··on Run0, a systemd based alternative to sudo, announced
I think a admin would better understand the system if there was only one subsystem doing a particular type of security and not two. Two subsystems doing security would lead to more problems down the road.
airocker··on Run0, a systemd based alternative to sudo, announced
no it is not
airocker··on Run0, a systemd based alternative to sudo, announced
It could all be simplified and map one to one to your identity provider credentials at a higher level. Having a complicated user system on the servers makes it a problem.
airocker··on Run0, a systemd based alternative to sudo, announced
One user with sudo for sysadmins on baremetal and a sudo access without CAP_SYSADMIN on container should be good.
airocker··on Run0, a systemd based alternative to sudo, announced
Exist does not mean it should keep existing if it is unnecessary complexity from the past.
airocker··on Run0, a systemd based alternative to sudo, announced
You dont need to use docker. Containerd or just just direct cgroup manipulation: https://access.redhat.com/documentation/en-us/red_hat_enterp...
airocker··on Run0, a systemd based alternative to sudo, announced
but then even traditional multi-user would be compromised in this case.
airocker··on Run0, a systemd based alternative to sudo, announced
In an on-prem cluster, yes one guy or a few sysadmins who either share passwords or can somehow put their keys in the authorized keys file and ssh.

In the cloud, AWS/GCP let or not let an IAM user reach a server.

airocker··on Run0, a systemd based alternative to sudo, announced
Only one human per machine. If you need to share the machine, make multiple containers and give everyone a separate container.
airocker··on Run0, a systemd based alternative to sudo, announced
How about only in servers where you only have CPU/Memory/disk/GPU with open source trusted drivers?
airocker··on Run0, a systemd based alternative to sudo, announced
you could potentially create multiple containers in that machine which are single user and give to every user who needs access. CPU/Memory/GPU can be assigned in any way you want(shared/not shared). Now no user can mess up another user.
airocker··on Run0, a systemd based alternative to sudo, announced
There have been no big cves of container escapes for a while now. I guess it can be considered secure enough.
airocker··on Run0, a systemd based alternative to sudo, announced
Maybe containers are a better way of isolating processes as mentioned in other comments.
airocker··on Run0, a systemd based alternative to sudo, announced
Its just maybe easier way to not have to go to the root shell.
← PreviousPage 2 of 10Next →