So Storj worked with the VP of Global Technology Alliances and Partnerships to put that marketing together… and didn’t provide a single link to Signiant?
The Storj author got linked. The year-old post about the University got linked. Same for an old Storj performance post. But neither the business contact that provided the quotes+data… nor the partner company… nor their product were worth a URL?
Aaron Zitzer is going to find keeping up a steady stream of good marketing like that a challenge… when you link-the-heck out of your own stuff and provided absolutely nothing to the partners you work with.
Why would any potential partner want to help work on content? Links are the cheapest thing you could give them back…
It seems to look they are on Tsunami UDP Protocol but I might be wrong. EDIT: Yeah I did some additional reading, they claim they have patented technology which is a conjunction of UDP and TCP [Signiant’s core UDP-acceleration protocol offers distinct advantages. Signiant isolates different sources of congestion by looking at latency and packet loss, and also by constantly examining the rate of change in these observations.]. On the first glance it looked like Tsunami.
Thank you for pointing out the missing url links! It was an unfortunate oversight, so these links have been added now.
Is it a customer? Or a potential customer? Or partner/reseller? Or just a potential partnership?
Storj isn’t even listed on their partners page (Wasabi is listed): Partners | Signiant for Faster File Transfer
So maybe it is something that is upcoming. But it sounds like partnership which means Storj needs to convince Signiant customers to sign up for Storj as storage solution. So still miles to go.
I dont think they were using S3 - take is with a grin of salt because I was really not paying attention to optimize it and dont quite fully remember all rclone-browser settings - on rclone I was able to get sth like 20MB /30 MB down / up and I am usually on 5 to 100 Gbs with high performance filesystems below it. In general, I’d say your question is a bit naive. If one wants to get some speed with storj, one has to go native. Its like a rhetoric question. Nevertheless, the problem is that as far as I remember, so called uplink cli user interface is not very user friendly, you have to remember all the settings and adjust every time to the particular machine you are operating from. The same complain applies when you are just starting with storj, you have to spend abour 1 to 3 hours just to understand it all in order to make some basic decisions (but thats a different topic). Anyway, I think you are making a mistake not paying attention to UDP and TCP and to such protocols as Tsunami and/or BBR. :- )
Tried my best, however, to be very frank, I dont see a point in further communicating with you. Good luck with you further endeavors in the world of TCP and UDP pockets. :- )
Im afraid its too late, but, keep trying. :- )
I like it but why you are still writing to me? Cant comprehend the reason. :- )
Get a room you two.Řś
Maybe some more news soon:
Storj and Signiant Partner so customers save on cloud storage without compromising on performance. Companies to demo solutions at NAB Show, Las Vegas April 13-17, 2024
today the Signiant Platform technology is trusted by over 50,000 companies for mission-critical workflow processes. With customers including Disney, NBC, and Apple, Signiant is a trusted partner to leading media companies, delivering critical enterprise-wide elements of global technology infrastructures.
Let’s hope. 
Do you have a feedback?
I’m sure - not. You just trying to took it down. Why?
Just explain, why do you are attacking Storj? Do you have some imagine problems with Storj? Or just some affiliation doesn’t allow you to agree with the how is it actually working?
Because other clients in Switzerland are happy with a performance.
And hopefully that was not only the commercial network that they tested on.
And hopefully potential future customers out of that partnership will not choose the commercial network to store their data on. At least not exclusively.
why. is. it. matter?
We want as much customers as we can attract. S3/native doesn’t make a difference. The Customer will decide, what is better for them.
See a difference?
Not convinced, sorry!
Would you like to share your location and other personal information publicly? No… why?
I know that, but you didn’t add anything to that, only generates a virtual problems out of blue (because we do not have customers with such requests in the support).
of course not. The commercial network has a limited application and right now the public network is much better because it has a distribution across the world, not a limited location to the one continent and maybe even to some locations of the continent - (asking for troubles), (yes, I still do not like the idea of geofence, because your data is encrypted, and doesn’t matter where is it stored. Nobody can get an access to it, include Storj!). So, even if it’s stored in Russia - it’s still safe.
I dont think this is accurate. We aren’t running an S3 front end to lose money.
The S3 is a current standard in the objects storages likes you that or not. In the end these objects are stored on nodes and retrieved from nodes anyway. Our S3 gateway is a distributed service too, not so much instances like nodes (yet), but it is covering most of locations.
Yes, if you have a wide channel (more than 1Gbit), the native can be faster for your location, for all others (Up to 3Gbit) using S3 can saturate the whole channel too.
The main point in any cases - parallelism, this is where the distributed nature of Storj is shining. And it’s encrypted by default, even for S3.
they have to have S3 integration, because as John the COO said, otherwise no one even wanted to start talking about the change, ppl just don’t want to do changes!
ppl say: “If it works, don’t change it” - well then You miss the progress, You need to keep progressing for the better! thus STORJ is waiting to be discovered.
See the problem is that we answer your questions but you disagree with our answers.
You assume that we run S3 at a loss and it is low performant. We have said these statements are not true, but you go on saying it is.
Here is another one:
Greg Holick from CloudSoda presenting at the Storj booth
Specifically @3:30.
Obviously this customer has no issue being named and having its use case presented. So it would make up a great case study on the Storj website as well.