It is not a problem if customers do not need it. I could also say that Storj not natively supporting SMB or NFS and relying on native uplink or S3 is a problem but it most likely is not a problem for the customers who either use S3 or use the native protocol. So, yeah, there is no demand for it, the customers do not care about it, why should Storj spend time implementing this (something that the customers do not care about) instead of fixing a bug or implementing a feature customers actually care about?
The cost of requiring ipv4 support today is still fairly low. Most customers and SNOs can make do as is with no change.
At some point, however, the cost will rise ever so slightly. This will probably impact SNOs first. It will not be very soon though, so Iām guessing the storj project will look very much different then than we think it will.
Iām an IPv6 advocate. Iād like to encourage storj to make design decisions that do not make the path to IPv6 longer, at least.
Until then, leave as is.
Every feature added has an up-front cost, and an ongoing support burden. Giving customers enhancements that theyāll pay for (especially if it gets new customer) is such a fundamental business idea that I donāt understand it being passed off as some sort of excuse.
Itās one of the core ideas that keeps a businessā¦ in business
If prioritizing IPv6 support isnāt going to result in more sales for Storjā¦ but adding other items from their dev backlog willā¦ shouldnāt they add those other features first?
Folks, itās even simpler than that.
Short version:
- Supporting ipv6 requires work but no reward: lack of ipv6 support does not preclude customers from using the services.
Case closed.
Longer version:
- Supporting both IP versions requires additional non-zero effort, with no reward, and Storj is not in the business of promoting ipv6. Itās not their job. Their job is to get storage to customers.
- There are no customers that are ipv6-only. Every customer has ipv4. ipv4 is not going anywhere anytime soon. Hence, every customer can access STOJ as is, if they wanted to, regardless of ipv6 support presence.
Hence, stop pestering storj to do useless busy work, and let them focus on improving the service.
Yes, before anyone is triggered ā I consider supporting ipv6 useless busy work.
I also consider ipv6 superior to ipv4 in every conceivable way.
And these two sentences can coexist just fine; understanding this fact is crucial in understanding this topic.
IPv6 support is not a ānice to have thingā, but a mandatory thing to any internet project who have people who really undertand the basics and necessary to do something properly and within minimal bounds.
The dificult for many to understand this difference explains a lot why they still disrregard IPv6 so much and why it keeps taking that long for people to learn something that is there for decades.
It would be really nice if you provided specifics.
Lack of what IPv6 feature that is missing from IPv4 threatens storj success?
Specifically, please.
(On the contrary, fwiw Iāve heard a lot of stories about broken routing and peering on IPv6. IPv4 benefits from working better simply by virtue of existing for longer, all other reasons aside. Letās not expand on this, this is just one counter example).
So far I hear a lot of fanboyism, no substance, and the whole junior developer vibe. IPv6 is more better and hence everyone shall use it right away and uproot everything that was done before.
World does not work this way.
I suppose this is possible. It seems unlikely all of Storjās current customers (and the ones theyāre trying to get) donāt understand the basics. After all: many are running successful businesses themselves that use the Internet. But there may be a Marvell Universe where this is true. Point taken!
You got me there. Iām not sure how many customers/potential-customers simply donāt understand the benefits of IPv6. I thought theyād have more pressing business concerns: but it could just be ignorance. It must be that they simply havenāt learned: it canāt be that they understand it completelyā¦ and have decided itās not important. I admit that until youāve brought up such nuanced arguments the thought simply hadnāt occurred to me.
I appreciate they youāre telling us whatās important to Storj and their customers, but leaving why itās important to our imaginations. Iāve spent far too much of my precious time reading about the reasoning behind positions: and itās refreshing and relaxing to just be able to trust whatever you type.
Please never explain how IPv6 support will improve Storjās business: youāll take all the fun out of it!
I have heard cows fly. Have heard.
My ISP doesnāt even have IPV6 support, so Iām rather happy with only IPV4.
Usually people that advocate for IPv6 immediate adoption are people that have just learned about it, maybe even set up a tunnel over at HE. They all seem to ignore the actual fact that IPv6 was proposed in 1995 in RFC1883.
We are close to 30 years later.
@Tetricz for saying such a thing it shows you undertands nothing, not even the basics to talk about having or not IPv6. It is pretty normal people who donāt know anything about something say they donāt need it.
@Mitsos usually people who fight against IPv6 or have a great anger about it is because they have learnet nothing about it after nearly 30 years but have a hard time in recognizing their innability to undertand and talk about that minimally, so in order to not look bad they find it better say that is not necessary.
@FREDY if someone is angry and fighting against IPv6, they should seek immediate medical assistance.
We are talking pure technical reasons and cows here. I havenāt seen your answer to the previous time I asked, so Iāll ask again: can you please cite one (just one) technical reason why IPv6 is a show stopper and every dev effort should be concentrated on adopting it first thing Monday morning?
Well thatās a baseless accusation. Iām all for IPV6 adoption, Iām even in talks with my ISP to work on helping them implement it for my other personal use cases.
Iāve seen this argument here before, but itās a low priority simply because there isnāt money to be made right now. If you got the budget, why not just pay storj to start work on IPV6 yourself? Better yet, they are open source, you could write it yourself.
Also, you are not making any strong arguments for why IPV6 should be used alongside IPV4 or even how to mitigate the problems that storj will face when implementing it. How do you get a customer who only has IPV4 to communicate directly with a node which only has IPV6? You canāt use a v4 to v6 proxy, that costs money one way or another.
Maybe in the future, but not today. Storj needs to focus on itās customers first.
Why is it mandatory? Did some country pass a law requiring it?
Otherwise everything seems to work just fine without IPv6. The again, maybe I ādo not understand the basicsā and having IPv6 would turn my 1gbps connection into 10gbps, but I kind-of doubt it.
Storj customers all have IPv4, so they donāt need IPv6. Maybe you are behind a CGNAT with IPv4 and also have a non-NAT IPv6, but even if Storj made the software compatible with IPv6 it would not help the customers, nobody would pay for it.
Honestly, most people, at this time, do not need IPv6. I work for a few small ISPs and none of them support IPv6 or care about it, because their subscribers do not care about it. My ISP is a bigger one and it does not give IPv6 to home subscribers (though maybe a business customer could ask for it, I donāt know, because none of the companies I know want or need IPv6).
So, if IPv6 is āmandatoryā then something must be broken with Storj because of lack of its support. What is that? What feature or capability of Storj, as it is now, is broken because of lack of IPv6 support?
It is even harder to start to explain such things to someone who firmly beleive āIPv6 is unnecessaryā. The problem is the person talking this with conviction. Sounds like Dunning Krueger or something like that. Thatās why is so hard to even start when argments are reduced to ācustomers donāt ask for itā (this is the worst ao far) or āsomeone doesnāt need itā.
Guess what is left is to feel sorry for those who still strongly believe they have any knowledge of what they are talking about.
Itās even better when you donāt even try and just try to go for personal attacks. Apparently IPv6 is so useful and wonderful, not to mention āmandatoryā, but I and the entire Storj company are too stupid to understand that.
āCustomers donāt ask for itā - Iām sure Storj knows if customers or potential customers have asked for it or not. I do not see why Storj would lie to us and lose (potential) customers by not supporting IPv6.
I know from my experience that my clients (and clients of my clients) do not ask for it. They get a IPv4 IP and are happy with it. Out of all those people, not one raised a question about IPv6 or said that he wanted to have it. I guess everyone is too stupid to understand IPv6 and how using it would be so great. By the way, the ISPs I work with do not use CGNAT. I worked with one that used CGNAT but would give a public IPv4 IP for free if the subscriber asked for it. Very few subscribers asked even for that.
Then again, Iām too stupid tu understand this and you refuse to enlighten me, so, I guess, I will remain stupid.
The node software supports IPv6. Just the node operators have to run dual stack.
Uplink supports IPv6.
The satellites are running on GCP I think and Google wasnāt offering IPv6 until end of 2022. So satellites could support it too, didnāt check if they already do.
Itās even harder trying to reason with someone that has their fingers stuck in their ears going āLALALALALALAā.
For the 3rd (third) time: can you please give me just a single technical reason why IPv6 is so badly needed?