HN user
https://twitter.com/aphelionz
Another similar artist that's still alive is Jon Sarkin [1] He has made over 10,000 pieces of outsider art usually drawn on the back of vinyl album covers. He has an archive of work online [2] and is active on instagram [3]
[1] https://jonsarkin.com [2] https://archive.jonsarkin.com [3] https://instagram.com/jonsarkin
AllSpice | https://allspice.io/ | Boston, MA | Full time | Remote/Onsite | Sr. - Principal| golang, Vuejs
At AllSpice, we're building the future of hardware development and collaboration, applying modern software design principles to the hardware industry with revision control, design review, and automated test (think GitHub/Bitbucket for hardware). AllSpice is unlocking the next generation of smart vehicles, IOT devices, rockets, medical devices, robotics, and much more.
https://techcrunch.com/2022/01/31/allspice-thinks-hardware-d...
We have a highly-capable, tight-knit, remote-first team with a flex office in Somerville, MA and competitive benefits. We strongly value continuous communication and personal development. See more on our careers page [https://allspice.notion.site/AllSpice-Careers-3173d0cd518b42...]
We're hiring primarily for:
Senior / Principle Infrastructure Engineer - Join our incredible engineering team by helping coordinate our infrastructure team and supporting enterprise clients. You'll work on automating our deployments, scaling infrastructure, and testing/planning architecture to support new feature development. More info here: https://allspice.notion.site/Sr-Principal-Infrastructure-Eng...
Tech Stack: Docker, Terraform, GoLang, Rust, Python, Vue
Apply by emailing us at jobs@allspice[dot]io with [HN] in the title and a link to your GitHub/GitLab profile and/or resume.
AllSpice | https://allspice.io/ | Boston, MA | Full time | Remote/Onsite | Sr. - Principal| golang, Vuejs
At AllSpice, we're building the future of hardware development and collaboration, applying modern software design principles to the hardware industry with revision control, design review, and automated test (think GitHub/Bitbucket for hardware). AllSpice is unlocking the next generation of smart vehicles, IOT devices, rockets, medical devices, robotics, and much more.
https://techcrunch.com/2022/01/31/allspice-thinks-hardware-d...
We have a highly-capable, tight-knit, remote-first team with a flex office in Somerville, MA and competitive benefits. We strongly value continuous communication and personal development. See more on our careers page [https://allspice.notion.site/AllSpice-Careers-3173d0cd518b42...]
We're hiring primarily for:
Senior / Principle Infrastructure Engineer - Join our incredible engineering team by helping coordinate our infrastructure team and supporting enterprise clients. You'll work on automating our deployments, scaling infrastructure, and testing/planning architecture to support new feature development. More info here: https://allspice.notion.site/Sr-Principal-Infrastructure-Eng...
Tech Stack: Docker, Terraform, GoLang, Rust, Python, Vue
Apply by emailing us at jobs@allspice[dot]io with [HN] in the title and a link to your GitHub/GitLab profile and/or resume.
Terry A. Davis vibes?
Equilibrium | Multiple roles, see below | Globally distributed, REMOTE | Full-time
https://equilibrium.co is a venture studio and services company that develops Web3 infrastructure for the likes of The Ethereum Foundation, Dapper Labs, Zcash, Forte, and Protocol Labs.
We are currently hiring for a whole bunch of positions:
- Backend systems engineer (web3)
- QA Specialist
- DevOps Practitioner
- Elixir/Erlang Developers (or Ruby devs who want to move to Elixir)
- Mid-level and Senior Go Developers
- TypeScript Developer
- C++ Developer
- Senior Rust Developer
- Smart Contract Developer (Solidity but also other SC languages)
See https://equilibrium.jobilla.com for information about all the positions listed above, and more
Equilibrium | Multiple roles, see below | Globally distributed, REMOTE | Full-time
https://equilibrium.co is a venture studio and services company that develops Web3 infrastructure for the likes of The Ethereum Foundation, Dapper Labs, Zcash, Forte, and Protocol Labs.
We are currently hiring for a whole bunch of positions:
- Backend systems engineer (web3)
- QA Specialist
- DevOps Practitioner
- Elixir/Erlang Developers (or Ruby devs who want to move to Elixir)
- Mid-level and Senior Go Developers
- TypeScript Developer
- C++ Developer
- Senior Rust Developer
- Smart Contract Developer (Solidity but also other SC languages)
See https://equilibrium.jobilla.com for information about all the positions listed above
There's definitely interest. Berty has a Go implementation and the idea of a Rust implementation gets tossed around every season.
Can Webassembly read IndexedDB yet?
Swarm persistence is hard, if not close to impossible. Better that multiple parties pin the data than just one though. It's a step in the right direction.
OrbitDB doesn't rely on a blockchain at all
It's not dead, just in a bit of a lull due to funding, which is hopefully coming soon. We have a very active Gitter and OpenCollective.
Source: I'm one of the core maintainers
https://equilibrium.co | Multiple Positions | REMOTE | Full/Part/Freelance
Equilibrium is a worldwide distributed team dedicated to building and maintaining the distributed web.
We're hiring for a number of roles:
+ Open Source Community Manager: https://www.notion.so/Hiring-OSS-Community-Manager-28be57e3d...
+ Smart Contract Developer: https://www.notion.so/Hiring-Smart-Contract-Developer-235f2e...
+ Technical Writer: https://www.notion.so/Hiring-Technical-Writer-bc6a543f6bea40...
+ Rust Engineer: https://www.notion.so/Hiring-Rust-Engineer-882281f5248e45579...
+ Senior Rust Engineer: https://www.notion.so/Hiring-Senior-Rust-Engineer-e6c94ccc26...
Please apply using the instructions on each posting! We look forward to hearing from you.
https://equilibrium.co is hiring REMOTE Rust programmers to help build the distributed web. Looking for one Senior and one "medium" level folks.
1. https://www.notion.so/Hiring-Rust-Engineer-882281f5248e45579... 2. https://www.notion.so/Hiring-Senior-Rust-Engineer-e6c94ccc26...
Also, speaking of Rust - we'd love more contributors over at https://github.com/ipfs-rust/rust-ipfs/.
Hey cryptoquick, I remember you from a while back. I'm https://twitter.com/aphelionz, one of the maintainers. Nice to see you :)
You're not wrong about the memory usage. We decided early on that the tradeoff would be more RAM than to take the performance hit with the I/O (either to and from IPFS or to and from the filesystem in the case of SnapDB).
That being said, I have been experimenting with removing indexes like the ones you pointed out in favor of generators that emit the values as they are traversed. There are two main efforts here, one is feasible and the other is more difficult.
1. The `entryIndex` inside of ipfs-log can probably go, and the ipfs-log#traverse function can be made into an async generator function that passes the oplog values up to the store 2. The indexes you linked to that hold the calculated STATE are harder to get rid of - they could be persisted to IPFS or the file system as well
Open to ideas on #2. SnapDB might work for all I know, as I haven't attempted it yet.
I can't speak to Electron, React, Redux, Iced, etc, but my guess is there are optimizations one can do there as well.
Can you elaborate?
Well, I imagine you'll be happy to know that some of us have begun IPFS implementation in Rust: https://github.com/ipfs-rust/rust-ipfs
Ah, sorry, yes I stepped on a rake and whacked myself in the face here.
What I meant, since LWW is nomenclature for an alternative to CRDTs, is that the last writer by _logical clock_ in a CRDT, not by _wall clock_ time, will "win" the key.
There ya go!
This is an open problem. It might be surprising to find out that it's quite difficult.
CRDTs usually work as last-write-wins, meaning that if you have a key-value store, the last update to update a key 'wins' the value via the way oplog reduction works.
If you reverse that to a FIRST-write-wins log, you can grant permissions and ownership on a first-come, first-serve basis. Revocation, then, becomes the issue. What do you do with the records they already have? Questions like that are plentiful.
The approach most people take is to find workarounds or "good enough" solutions here, either by using encryption and allowing the encrypted data to be public, or by using some sort of other OrbitDB store as their ACL and management, and only giving select keys access to write to said ACL store in the first place.
Adding encryption into the mix though, particularly multi-writer, becomes exponentially harder.
tl;dr: You use this any time you want to have mutable data shared across a peer-to-peer network.
I wasn't there at the beginning but I believe the project came out of trying to achieve said mutable state within IPFS (which, for other readers is content-addressed and therefore append-only)
http://orbitdb.org lists all of our current users, the biggest one is Metamask by way of https://3box.io. https://tallylab.com is building with it for remote encrypted backup and shared tallies. https://github.com/dappkit/aviondb is a MongoDB-like interface for it.
Yeah, sorry about that :( There's this though: https://github.com/haadcode/orbit-db-control-center
(which also seems to be putting https://ipfs.io under strain. Sorry, ipfs.io!
OrbitDB works with a CRDT stored in IPFS. In order to calculate the state of the database, it does need to reduce the CRDT oplog which requires fetching all the entries. This was indeed very time consuming, particularly for remote requests, since we used a "nexts" list of addresses to load.
HOWEVER! Our latest release, 0.23.0, mitigated this by using a power-of-2 skiplist to load things in parallel, which gave us a nice 4-5x boost there.
Hey thanks for taking a look at this. We support identity providers (the one you linked), and access controllers.[1]
Identity providers work by cross-signing an external keypair with the generated OrbitDB key-pairs, and access controllers generally work by exposing a `canAppend` function that facilitates any kind of auth you want to perform. There's support for Metamask for example. OrbitDB is also used _in_ Metamask under the hood by our good friends at 3box.[2]
TallyLab, my application project, uses these in its IAM system and you can see the repos here.[3]
1. https://github.com/orbitdb/orbit-db-access-controllers 2. https://3box.io/ 3. https://github.com/tallylab
Hey folks! I'm https://twitter.com/aphelionz. One of the maintainers of OrbitDB. Happy to answer any questions you might have. I'll also be in the thread answering folks as well.
It's still so interesting to me that this never caught on, particularly in the "distributed age." This feels like a hidden gem in the research that has been covered up by the sands of time.
It would be great if this achieved API parity with ES. Being able to swap out parts of the ELK stack would make tools like kibana even more powerful.
Right now a colleague of mine are working on a project called TallyLab. It's a "data diary" based on IPFS and OrbitDB. By utilizing those technologies we hope to create a distributed, decentralized, end-to-end encrypted, peer-to-peer system that gives people full control over their data. We believe it will be the first of many "GDPR-first" or "HIPAA-first" apps.
Sign up for our beta program at https://tallylab.com :)
The big mistake I made in trying to do this was to hire other people with my same skill sets. I am an engineer and I thought "Ok, I'll just hire more engineers," thinking I would transition to the business side of things. What I should have done was hire people with different skill sets like sales / marketing / etc.
IIRC it's the result of an FOIA request
Why did you create this account just to post these comments? Why is this so important for you to criticize?