onionjake

Not open source. What would be your use case?

No BSD support unfortunately. Just Linux, Mac, windows.

We developed Object Mount (formerly cunoFS) (https://www.storj.io/object-mount?hn=1) specifically to not rely on any metadata storage other than S3 AND preserve 1:1 mapping of objects to files AND support for POSIX. We have a direct mode that uses LD_PRELOAD to keep everything in userspace so no FUSE overhead.

This approach isn't right for every use case and juice might be a better fit for this sort of 'direct block store', but wanted to include it here for folks that might want something like Juice but without having to maintain a metadata store.

(Disclosure: I work at Storj that develops Object Mount)

Storj supports arbitrary configured backends each with different erasure coding, node placement, etc.

When the cameras become a revenue stream for a city it is not a good thing.

Cameras have been installed to fine cars running red lights. The city then reduces the length of the yellow to catch more people and offset the high cost of the cameras. The shortened yellows cause increased crashes and fatalities.

Net-net the track record in the states is not great.

One example https://www.koaa.com/news/news5-investigates/news-5-investig...

I switched banks until one worked. Others I access on the web.

* I work in my unfinished basement, but often roam to recliners in the house because the basement is cold in the winter * standing desk from IKEA * 5K ultra wide LG monitor * Thinkpad P1 * Microsoft ergonomic keyboard * Regular run of the mill mouse * Blue yeti microphone * Currently using the laptop webcam for video

I get a lot of comments about being in an unfinished basement so I recently bought a green screen and some ring lights to try and improve my picture. The webcam on my laptop is too grainy for OBS to use the green screen, so looking to buy a new webcam.

Database indexes are definitely one of the most approachable concepts of databases for computer science majors. If you have studied data structures and Big O notation you have all the concepts needed.

While I agree that how a query planner works is one of the most ‘magic’ aspects, I think the output from the query planner in most databases is very approachable as well to regular common programmers and will get you quite far in solving performance issues. We know what full scans are (searching through every element of an array), etc.

The challenge is usually discovering that the jargon used in your database really maps to something you do already have a concept about and then reading the database documentation…

Matt Might was one of my favorite professors when I was in school. I hadn't learned about his son's passing until seeing this. Both Matt and his son are an inspiration to what can be done even in the face of the unknown.

I can't imagine the pain and anguish over the years that must have been felt as parents, so it was comforting to read about what kind of person Bertrand became.

I hope that if my son ever needs my skills, I would be up to the task so perfectly understated here: "Extending an artificial intelligence tool on the fly to analyze the data, Bertrand’s father found an unusual strain of pseudomonas as the likely culprit in Bertrand’s body."

Best of luck with the Bertrand Might Endowment for Hope!

S3 has been around for a long time and they had a lot of objects to transition when they upgraded, so I imagine that is why it took awhile.

There are other object storage systems that have strong consistency guarantees that came out after S3.

It greatly simplifies things that an object written to S3 it is immutable.

On a high level, all writes to your storage use some UUID. All reads use a consistent metadata storage (pick a modern database). After your write is complete and you are sure it is persisted, do the metadata update and return success. Everyone gets a consistent view of the operation.

Discussed in another thread: https://news.ycombinator.com/item?id=26581399

There is a 'Contact Us' button at the bottom of the page you can always reach out.

Another thread I posted a little bit about how we are compared to glacier: https://news.ycombinator.com/item?id=26582429

Glacier can get pricey when you store/retrieve your data because of ops, retrieval fees, and egress (if going to the internet). We feel like immediate availability is a compelling advantage of our product.

How do you arrive at twice as expensive as AWS glacier?

AWS S3 Glacier is the same $0.004/GB/month and requires the same minimum of 90 days, but retrieval takes "from 1 minute to 12 hours". They also have large retrieval costs (on top of the regular egress to the internet) and API call charges.

AWS S3 Deep glacier is only $0.00099/GB/month, but requires it to be stored 180 days and also have operation/retrieval fees. "For long-term data archiving that is accessed once or twice in a year and can be restored within 12 hours"

https://aws.amazon.com/s3/pricing/

We feel like the immediate availability of our offering is compelling and a competitive advantage over glacier.

Is there a forum/discord where the community can discuss/learn?

Not yet, we will have one created soon.

This is great feedback, we'll take this into consideration. You can always reach out to talk about specifics about your use case and how we can better meet it (there is a Contact Us button near the bottom of the page).

Precisely. Although we also believe you shouldn't have to worry about going bankrupt if you ever need to restore all your data or want to migrate somewhere else, which is where the 100% egress of what you have stored comes from.

Answered in another thread https://news.ycombinator.com/item?id=26581857

Interesting thought thread on our pricing structure... It saves money if you intend to send the backup to 10x places every month. If you only intend to do it once though you don't come out ahead $10 * 3=$30 versus $1 * 3+$22.50 = $25.50.

I answered the sibling comment: https://news.ycombinator.com/item?id=26581857

It is a service you can sign up for https://crowdstorage.com/products/device-backup-my-cloud-hom.... Stay tuned for support on more devices in the future (i.e. synology, qnap, etc.).

We also purchase storage in datacenters.

Not trying to obscure anything, just busy this morning :)

I answered the parent.

We are not built on top of Sia or Storj. Our technology has been developed for the past decade and is independent.

Storage comes from services that we offer to end consumers. In exchange for our services they agree to let us use the unused storage on device, i.e. (https://crowdstorage.com/products/device-backup/). We plan on expanding to many more devices.

Storage also comes from being able to transparently leverage more traditional storage that we purchase from various providers.

How do you handle the problem of low interest?

We can seamlessly leverage more traditional storage as well as distributed endpoints. So in a way yes we can 'seed' it. We will likely wait until we have enough storage in a region before launching there.

the egress pricing seems a little disingenuous

I have made small edits to the website to make it clearer it is 100% of data stored is free egress. This is definitely something we will focus on in the redesign.

so is this really a US only service

We plan on launching regions outside of the U.S. that only store data outside of the U.S. soon.

Also, how is the data encrypted? "State of the art encryption" is just marketing fluff :)

AES256 and/or xsalsa20poly1305.

You can also use SSE-C to provide our servers with a key to encrypt the data (which our servers then promptly forget). https://docs.aws.amazon.com/AmazonS3/latest/userguide/Server...

Yes. We are strongly consistent.

Yes! Our storage footprint globally is growing so we will definitely add more regions.

What region in particular interests you?

I'm adding some quick edits to the page to make it clearer that it is free egress up to 100% of stored content.

We are currently redesigning our website and this will definitely be something we focus on making more upfront and clearer.

We are working on it! We plan to have support for ACL, object locking, versioned buckets, etc.

Hi, CTO of CrowdStorage here. Happy to answer any questions. I'm doing my best to respond to comments.

Our website is right now being redesigned and your comments here are helpful to help us know where we need to improve!

We have plenty of capacity to handle 50 PB :) We also leverage our own more traditional cloud storage transparently if/when needed.

We've been storing data like this for several years and have kept hundreds of PB and 10's of billions of objects without data loss despite having many nodes in areas affected by large regional outages. One recent example is when Texas was affected by blackouts.

We are working on getting as much content up on the website as we can and telling more about us!