The comment is referring to finding something to replace the Haber-Bosch Process, which is mostly fossil fuel driven, which makes most of our food itself dependent on fossil fuels.
Unrelated to the above, except in the mix of sustainability and agriculture - there are a bunch of companies working on bacteria to fix nitrogen for crops without requiring separate fertilizer similar to how legumes do it. I think Pivot Bio is the furthest along in the space - they’ve got a commercially available product - but it’s an active area of development in the industry right now.
> Unrelated to the above, except in the mix of sustainability and agriculture - there are a bunch of companies working on bacteria to fix nitrogen for crops without requiring separate fertilizer similar to how legumes do it.
Nitrogen fixation is energy-intensive, so something has to provide energy. Additionally, nitrogen fixation has to happen in anaerobic conditions, oxygen kills the enzymes responsible for nitrogen fixation. In legumes, the oxygen is carried away by hemoglobin (the same one used in "artificial meat"), but engineering these conditions for free-living bacteria is likely going to be problematic.
I'm personally hoping for a catalyst that can work in mild conditions.
There’s been some success here already - as mentioned, there’s some commercial products on the market already that do some amount of nitrogen fixation for at least corn and I believe wheat as well, so it’s not unsolvable.
Where is the security problem? All code commits and builds can still be signed. All of this is just a more efficient way of deploying changes without dropping existing connections.
Are you suggesting that hot code replacement is somehow a attack vector?
Ericsson has been using this method for decades on critical infrastructure to patch switches without dropping live calls/connections it works.
My interpretation of the GP was that a code change in one node can be automagically propagated out to a cluster of participating Erlang nodes.
As a security person, this seems inherently dangerous. I asked why it is safe, because I presumed I’m missing something due to the lack of ever hearing about exploitation in the wild.
An Erlang dist cluster has no barriers between connected nodes. But a multithreaded application has no barriers between its threads either.
If someone can exploit one Erlang node, they can easily take over the cluster. But in a more typical horizontally scaled system, usually if they can get into one node, they can get into all the other nodes running the same software the same way.
Security wise, I think of the whole cluster as one unit. There's no meaningful way to separate it, so it's just one thing. Best not to let anyone in who can't be trusted, because either they have access or they don't; there's no limited access.
But given that, may as well push code updates over dist in a straight forward way, because it's possible, so it may as well be straight forward.
If someone were to exploit a running Erlang process, the description of this feature sounds to me like they would have access to code paths that allow pushing new code to other Erlang processes on cooperating nodes.
Yeah -- and a some constraints. We don't want to spend any more than $10 per user per month and must support SSO for our Google workspace accounts. Other than that it's pretty much standard project management stuff for managing Sprints and hosting some docs.
@junaru have you worked in the service industry?
Are you suggesting that people who work in areas where tips are common should just be paid more by their employers?
100% Agree that people should just be paid more.
But it's not that simple ...
Raising wages has an inflationary effect on the prices in the restaurants/bars.
And the people who suffer from inflation are the minimum wage earners who spend proportionally more of their disposable income on essentials like groceries.
I worked as a waiter/bartender for 3 years in college and the wages were terrible!
But I always made an effort and customers gave me tips.
Saved those tips to buy my first iMac which I used to learn higher-paying skills.
Having been a service industry worker and now in a different income bracket I always tip for good service. Without tips many people in the service sector could not get by.
> Without tips many people in the service sector could not get by.
I don't think that's necessarily true. In Japan tipping is a faux pas, and in fact restaurants will often return or refuse to accept them, yet the service sector is massive and the quality of service tends to be extraordinary. Much of Europe is similar, especially in eastern and southern parts. In China tipping is just not done...
How is it that they all get by, but the US service sector can't?
Indeed, people working in services in Japan people are paid significantly better than in the US/UK so tips aren't required. Also the culture is totally different and I prefer it that way too.
At worst, it's comparable. You could make a complicated argument that costs of living in Japan are lower so on pseudo-PPP terms they're paid better, but this is by no means clear.
> Japan as an example for this is like a red herring. The US/UK is not Japan. Just lookup "Cheating culture in Japan"
The red herring is raising totally unrelated behavior from a Reddit post.
In truth, most of Asia's tipping culture is much like Japan's. China's 1.4B denizens don't tip. I'm in Croatia and nobody tips here, either. It's only expected of tourists.
How is it going to have an inflationary effect when workers are already making that money? I don't really see how increasing menu prices or adding an automatic 12%-15% on the bill to avoid playing games afterwards with the receipt is a bad thing.
If costs rise, prices have to rise to maintain margins. Textbook definition of Inflation.
If there's 15-20% (discretionary) added to the bill, it's not perceived as the price but rather as a "thank you" for taking care of us during our experience.
Again, I don't like this system; and would welcome a viable alternative!
> Raising wages has an inflationary effect on the prices in the restaurants/bars. And the people who suffer from inflation are the minimum wage earners who spend proportionally more of their disposable income on essentials like groceries.
I don't understand why you are conflating inflation of sit-down restaurant and bar prices (which doesn't affect poor people) and inflation of grocery prices (which does). You don't tip at checkout at a grocery store or a liquor store.
>Raising wages has an inflationary effect on the prices in the restaurants/bars
That implies consumers spend differently if they know the actual cost ahead of time, otherwise service inclusive pricing would make no difference. ie the whole industry is exploiting anchoring effects.
Removing anchoring effects would make restaurant businesses less profitable, and consequently the properties that host them less valuable, so lower rents.
There are clear incentives for pushing an inflation narrative.
How are tips immune from the inflationary effect you’re describing?
If a government mandates a higher wage or if 90% of a society voluntarily contributes tips, the effect is the same.
At the end of the day, the customer is likely paying an increased amount for a service being rendered. Except a mandatory wage increase may have the business reduce their margins while a tip puts the pressure directly on patrons.
I did tipped service work. It’s time to discourage general adoption.
"I spent around ~$5750 for all my devices and accessories.
This includes 7 APs, 6 PoE cameras, and several switches.
I rebuilt it from scratch, and my house is big."
I wonder how many people this is applicable to...
We have a similar setup but for a co-living house with 24 people.
It can read like an Ad for Unifi but, in our experience no other brand comes close in terms of hardware+software quality, reliability and no leaking data.
Mhh, I'm not so sure I would count that breach against them. It was an inside job from an employee who wanted to export money. I would guess most companies fail at that threat vector.
Thought that link made me curious, why did UI have peoples social security numbers? (I'm not American)
IMO this should have been included in their threat model. The only way to exclude yourself from insider threats is if insiders cannot possibly become threats.
Excellent point. Agreed. Do you have any practical tips on how to achieve this? e.g. a) don't collect data unless it's absolutely necessary to the functioning of your product/service. b) encrypt and limit access to only essential people.
But then what if one of those essential people goes rogue or falls victim to a spear-phishing attack or family ransom etc. How do you mitigate that?
Perhaps have a "two keys" to unlock protocol such that two separate team members are always required to unlock sensitive data and i.e. always supervised.
I don't know the solution, genuinely curious how this is solved in practice.
The gist is that as long as your business model is collecting certain data that can be used to identify individuals you must cater for the insider threat and for instance implement segregation of duties. When you do not manage the risk of the data you’re collecting that’s when you end up together with ubiquity.
The engineer that stole the data should have needed to collaborate with at least one peer to exfiltrate it. There should be no way for any individual to take this data and clear himself from the audit logs. Segregation of duties in this instance should have made it possible to detect the event quicker and attribute it to this particular employee.
I like it. I use Ubiquiti gear for most of my homelab and home networking stuff with the exception of the 40g and 100g stuff. It is both easy to use and provision as well as easy to upgrade… and of course it works.
OP. Bummer that the article gave that impression. I'm just a passionate person, if you read my blog and the other articles, people would see every single of my blog post is like that. I just like to shoot nice photos and write about my experience, nicely.
Don't worry. People are naturally skeptical when they see high quality content it feels like "advertorial".
It's clear you are just sharing your experience of using the Unifi products/ecosystem and setting up an impressive home-lab.
I was taken aback that an individual would spend almost $6k on their private home network. But you're clearly not short of a penny so why not spend it on having a kickass network? ;-)
I'm sure other successful software engineers have similar setups / investments; they just don't share them in public.
I’d argue that returning to something after a period of absence is a good test for how intuitive it is. If you forgot something and it’s not obvious to you then it definitely won’t be to the beginner. Having a beginner’s mind is essential to avoiding unnecessary complexity in a system.
(Awesome tech! Or at least CGI ...)