nixos-search
nixos-search copied to clipboard
NixOS
IPv6 support of search backend
Hate to bring it up again but the backend we are using for the search doesn't seem to support IPv6. While Elasticsearch is perfectly capable of IPv6 the host (despite being on AWS) failed to enable it. This is a discrimination against people with poor (or none) IPv4 connectivity on this planet.
Like explained in my NixOS.org Netlify post we should try to have this as a baseline requirement for new services that will - to some degree - be mandatory/required to interacting with our services/websites.
I will ask if our ES provider can support IPv6.
I know your :heart: is in the right place, but I would like to avoid such strong wording as "This is a discrimination ...". It might be understood wrong depending on the context you are coming from. I was also guilty of such mistakes in the past and I just hope I will not make them in the future.
Just so other people can find this using the GitHub search. I just got bitten by that.
Network Error! A network request bonsaisearch.net domain failed. This is either due to a content blocker or a networking issue.
This is an accessibility issue. Accessibility is not only about "handicaps".
The search cannot ship if it's not IPv6 enabled, plain and simple. Some environments won't go through IPv4, as can be seen here by @mweinelt (I suppose), which means that some technically inclined people, you know, the kind of people a Linux distro, or a package manager caters for, will have an issue that is mostly out of their control for the site.
This is, I believe, not something that we can just program our way out of, so I think this'll need to be validated with the upstream provider.
Perhaps it is something we could fix with a ipv6 capable proxy if upstream isn't able to support ipv6 directly.
On Thu, Jul 30, 2020, at 11:11 AM, Samuel Dionne-Riel wrote:
This is an accessibility issue. Accessibility is not only about "handicaps".
The search cannot ship if it's not IPv6 enabled, plain and simple. Some environments won't go through IPv4, as can be seen here by @mweinelt https://github.com/mweinelt (I suppose), which means that some technically inclined people, you know, the kind of people a Linux distro, or a package manager caters for, will have an issue that is mostly out of their control for the site.
This is, I believe, not something that we can just program our way out of, so I think this'll need to be validated with the upstream provider.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/NixOS/nixos-search/issues/52#issuecomment-666440822, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAASXLCMYWPJFKJKZJEDRITR6GETTANCNFSM4NINNBNQ.
Ipv6 is a blocker, as it wasn't for nixos.org. It is important thing definitely, but not a blocker.
I can see many ways how this can get resolved:
- bonsai.io adds support for ipv6
- we fix the issue with ipv6 capable proxy as suggested by @grahamc
- we find another provider for elasticsearch that supports ipv6 and is as generous as bonsai
- we manage our own instance of elasticsearch
I also reminded bonsai.io to answer the questions regarding ipv6 support, since they didn't answer. I hope they just forgot to come back to me and support for ipv6 is not a problem.
Regardless of their decision we should move forward and not punish all of the users. Punish is probably to strong of a word, but can not think of a better one.
Regardless of their decision we should move forward and not punish all of the users. Punish is probably to strong of a word, but can not think of a better one.
Punish? What do you mean? We've been living with this solution for years now and it just works. It has different problems but none that make it unusable.
Still the same problem… When will this be fixed?
Also This is either due to a content blocker or a networking issue. is not true: It's not a content blocker or a fault in the network, it's a problem at bonsaisearch.
