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]
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.
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...
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.
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...
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)
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)
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.
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.
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.
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)
[1] https://jonsarkin.com [2] https://archive.jonsarkin.com [3] https://instagram.com/jonsarkin