Some of the original developers of H3 gave a presentation about it that goes over the tradeoffs between those different systems, would recommend watching it.
We're hiring experienced software engineers to build the future of self-storage and vehicle storage.
Neighbor is a marketplace connecting people with spare space to those needing storage, disrupting the $40B self-storage industry.
Backed by A16Z, real estate venture firm Fifth Wall, leaders of Airbnb/Doordash/Uber, among others.
We're looking for strong generalist software engineers who enjoy ownership and impact in an early-stage, growing company. Our stack includes Typescript, React, Ruby on Rails, Golang, and Python, primarily deployed on AWS. You'll be involved in feature development, system architecture, and producing a high-quality product.
What we're looking for:
* 4+ years full-time software development experience.
* Solid understanding of software engineering principles.
* Experience with our tech stack (or a strong desire to learn).
* Ability to take ownership and drive projects.
* Must be willing to work on-site in our Lehi, UT office.
Bonus points for:
* Experience with React, Ruby/Rails, AWS, TypeScript, PostgreSQL.
* DevOps experience.
* Interest in AI/machine learning/data science and their applications.
* Technical leadership experience.
Went down this route and haven't had any issues with heat or having to replace heatsinks, add fans, etc. that others mentioned, but your mileage may vary.
Runs opnsense on proxmox, along with some other containers. It's been a great little box.
On a podcast series covering some of the history of the intersection of business and technology in Utah (The 4th Node), the hosts had an episode with Bruce Bastian. Covers his background and the history of WordPerfect, for those curious to learn more and/or hear from Bruce himself:
Postmortem report from withpersona.com resulting in ~12 minutes of complete service unavailability and several hours of varying degrees of degraded service.
It's not entirely clear to me after reading, but the author addresses it somewhat in the article. Seems like it depends on the persistence of the crawler, if the host instance permits that info to be shared:
> In the example above, if Ringo were to reshare John's reshare of my status - John doesn't know about it. Only the original poster (me) gets notified. If John doesn't share his social graph, it might be possible to work out where Ringo saw the status - but that's rather unlikely.
> Mastodon has an API rate limit which only allows 80 results per request and 1 request per second. That makes it long and tedious to crawl thousands of results.
> Similarly, some instances do not share their social data or expose anything of significance. Some servers may no longer exist, or might have changed names. It's impossible to get a comprehensive view of the entire Fediverse network.
reply