[I see the irony as I ask strangers for reviews lol]
188 karma · joined March 15, 2012
[I see the irony as I ask strangers for reviews lol]
What do you think?
Above is the very first version (super simple right now). Would love to know the top challenges you face while ideating and dreaming of new thoughts.. What would you like to see, what would you like to add?
Probably will do something like a $2 day pass and a $20/mo subscription. The monthly subscription would definitely have a lot of features in it. If you have any suggestions, would love to add them in!
We built a tool to summarize and chat with with some of the most popular books [1], like The Book Thief [2]
The key features we felt that were necessary were:
- Quickly search your books
- Select the book and start chatting
- One click book summary
- Add link to buy on Amazon
--
Caveats:
The books library is currently very small, if we have enough interest we would be happy to source and grow the library.
--
What would you like us to add to this next?
[1] Search all books: https://www.sliksafe.com/books
[2] The Book Thief Summary: https://www.sliksafe.com/book/the-book-thief
Key features include:
- Context-aware email drafting based on your input
- Multiple tone options (formal, friendly, etc.)
- Adapts the email to your voice
- Ability to directly send the email to the recipients
- FREE to get started
Try it out for FREE: https://www.sliksafe.com/tools/ai-email-generatorI'd love to hear your thoughts and feedback. What features would you like to see in an AI email assistant?
The full end-to-end encrypted backup and sharing experience is provided by Slik. We use Storj only for storing the encrypted blobs, or simply as a replacement of S3.
> The website tells me I can pay by solana (or even by credit card!), but there seems to be no indication of how much I actually would have to pay.
Our detailed pricing page is currently available within our web/desktop apps. You can pay - 0.1 SOL for 10 GB lifetime storage (10 years), or
- $4.99/mo for 500GB storage, and so on..
> That does not follow from the provided info. Simply leaking the keys in some form would already be enough as a backdoor, as the data is obviously not only stored locally.This is similar to the problem of leaving your device accidentally open, which unfortunately is a much harder problem to solve. However, we do provide a way for you to remotely wipe a device in case of unauthorized access.
> There seems to be a lot of metadata on sliks side, or is it using some form of encrypted search?
All your metadata is encrypted on your device before it is backed up to Slik. We provide client side search experience so that Slik is unaware of even the keywords that the user is searching for.
We're constantly improving our WhitePaper to provide as much clarity as possible about our systems and algorithms.
We had set lifetime storage for 10 years, and have clarified it on our website to prevent it from being misleading. Thanks a lot for your inputs! :)
If you have any questions, feel free to reach out at arpit@sliksafe.com. Happy to support your use case.
Reliability, performance, and a scalable infrastructure were strong selling points of Storj for us, and hence, we decided to go with them to provide a more seamless experience in terms of data upload and fetch. We also use Filecoin for immutability of user data, and as another layer of global redundancy.
Currently, we pay for storage/egress to Storj. Users can pay using dollars/crypto on our platform and we convert it to relevant Storj tokens to pay for storage. It is not automated yet, but yes we plan to automate it soon. Also, Storj does accept Storj tokens as payments.
About interchangeability, we plan to provide the migration functionality on our end to users.
We started with Firebase/Google because it was easy to setup. However, our team has been experimenting with different blockchains to sync the different file-ids and file-hashes. This would provide even more dApp developers to develop apps on top of Slik. We have a potential fit, and expect that to be integrated in H1'2022.
There are parts of the system like the multi-device sync, encryption, cross-platform support, etc. that would need to be factored in. However, reducing $/TB is an area that we plan to explore when all other systems are stable and our unit-economics is net positive.
Do you know anyone in their team? and if so, could you connect me with them? Thank you!
Here were our goals when we started this out -
- Prove and implement the encryption technology [completed],
- Switch over from centralized storage to decentralized storage [completed],
The above two goals help us achieve a working solution that users can start adopting.Next few near-term goals are -
- Switch over from centralized compute to decentralized compute,
- Make the code open-source so that the technology can be extended, forked, etc as the community needs.
Hope that gives you a reason to be stoked! :)We currently have a macOS app available and are targeting January for a Windows launch and a Linux launch soon after. We also have an iOS and Android app with a few beta users, and will release it around Jan/Feb'22.
Slik’s desktop apps have the ability to automatically detect changes in your local connected folder and sync those changes.
About On-demand syncing - we built Slik in a way that, once backed up, no files are required on your local machine. This doesn't prevent you from searching through all your files, and you can selectively download files based on your need.
However, I have added an item on our roadmap that would selectively download folders for offline syncing and faster access. Thanks again!
We're using Storj and IPFS as the only storage layer behind user data, not as a CDN.
However, we also have an email sharing solution already integrated into the app which uses public-key cryptography. This is protected from accidental leaks as you correctly pointed out.
Thanks for the feedback, we would update our WhitePaper with the details from above, and also indicate that to users in the UI - so that it scares people less! ;)
The encrypted file metadata (and the search indices) are downloaded at once. It is then decrypted using the user's key on device. The user then performs a client side search to get the relevant file-ids. The file-ids are then used to retrieve retrieve the file from the decentralized storage.
The keywords (along with other file metadata) are also encrypted using the user's key, so analyzing access patterns of the chunks, would not be possible for us.
Feel free to read more implementation details in our WhitePaper - https://sliksafe.com/whitepaper.pdf