Not quite the same, but EMT conduit is very popular for shade structures at Burning Man and similar events. You can get fittings that will hold up very well in windy conditions (if properly secured) https://formandreform.com/blackrock-hardware/
I know I don't. It's a dystopian nightmare for an advertising company to be building "the metaverse".
I hope all the other players in this space band together and form an open, federated metaverse.
It's one use-case I can kind of see benefiting from blockchain protocols: enforcing digital scarcity in a federated metaverse, by recording transfers of avatars and assets between the "metaworlds" making up the metaverse ("digital identity scarcity" is still an unsolved problem though, I think)
Stats like "2%: The percentage of Patreon creators who earn more than the federal minimum wage through the site" are pretty meaningless when there's zero barrier to signing up and asking people to fund your hobby.
People shouldn't be misled into have unreasonable expectations of how easy it is to make a living this way, but I'm not sure how much of that is Patreon's fault. It's a platform, you still have to create the value and attract customers.
In both my comments I explicitly said that vulnerabilities in browsers can and should be called RCEs. I was only arguing about what to call vulnerabilities in the underlying libraries (like SQLite) which aren't inherently exposed to "remote" data/manipulation.
Say for some reason someone used an exploitable version of SQLite in a program that had the setuid bit set. You wouldn't say SQLite had a privilege escalation vulnerability, would you?
I don't know. I'd say PDF or JPEG parsers (and SQLite) can have arbitrary code execution vulnerabilities, which can in turn be responsible for remote code execution vulnerabilities when used in network-connected software.
e.g. SQLite has an ACE. Chrome has a RCE (which is SQLite's fault).
I think the key to eliminating most of this behavior is to not show the picture right off the bat since it allows people to be subtly racist. If they have to ask for a picture before denying a guest then it's a lot more obvious they're being racist.
The more overt racists can be dealt with by doing simple analysis of denied/cancelled bookings and banning them.
I'm guessing AirBnB will eventually have to implement one or both of these approaches to avoid discrimination lawsuits.
For many purposes it would be cost prohibitive to run detailed background checks on individuals to discover every relevant fact like that, so they rely on aggregates, which works well enough.
I'd take it even further and implement the various web standards on this VM. That way when HTML6 or CSS4 comes out you don't need to wait 4 years for everyone to upgrade their browser, you just download it automatically the first time it's used.
This is sort of taking Cappuccino/Objective-J's principle of "shipping the runtime" to the extreme.
The Haight isn't that bad, I certainly wouldn't call it a red light district. I lived a block from Haight and Ashbury for a year, and while the fauxbos can be annoying they're mostly harmless.
Tenderloin is much scarier. My friend got punched in the face by a random guy walking down the street.
If you live and work near Caltrain or BART stations it's very easy to live in the city and work in the valley or east bay, or vice versa (though if you live outside the city you'll want a car).
Or if you're fortunate enough to work somewhere that has a shuttle that's another option. Many of the big tech companies do now, thanks to Google's lead. Off the top of my head: Google, Facebook, Apple, Genentech (I actually knew someone who would take the Genentech bus to work even though they didn't work there. Guess they don't check)
Of the people I know who live in SF and work in the valley, I'd say roughly half drive, and half take the train or a shuttle.