Is a lack of HTTPS a turn off?

[Dreamwings]

So, I've had my site for a long time. Most of the time, there has been no HTTPS. I never really saw a need to have it since there weren't any forms or sensitive information to be encrypted. I know how to and how to do it for free and that it's just a few commands but I just didn't want to. Plus the site was mostly just for myself. But now that I am hanging around here and planning to join webrings and such I was wondering.... should I get HTTPS anyways? I know a lot of browsers will warn you if you try to connect to a site using HTTP (even if, as long as there are no forms or logins or anything there isn't much of a reason to warn, which my site doesn't have. Like, all an interceptor would get is a HQ download of chart's The Forest and a bunch of pngs). Sometimes I've had to tell my parents and friends when they try to look at it that no, it's just being silly and it is completely safe. But ofc people online don't know that when their browser is looking all threatening and telling them how dangerous it is, nor do I know everyone on the entire internet to explain to them that it's actually perfectly fine. I've seen notes from webring creators saying they removed sites because their browser was saying they were insecure, and ofc I don't want my site getting removed unless I'm asking for it. Plus I don't want people in general thinking im "trying to hack them" through the browser (You would be surprised how tech illiterate some people can be. Hell, I've had to argue that with my own parents).
But anyways, wanted to ask the forums, is a lack of HTTPS something that makes you go "Oh no" and leave or do you know what that means and would push through regardless? Also any other fun facts/addendums on the topic.

[Zombiethederg]

dude, im not even gonna lie to you I never check if a website has HTTPS. I have no idea what it even means. I just kinda surf the web, and as long as a site dosent ask me for any info like my credit card, I dont really pay much mind to the HTTPS status of the site :P

[Melooon]

If you look at your sites listing in the surf club, you'll notice its very broken! This is because its super hard to embed HTTP stuff in HTTPS sites; they just don't get along well 

I definitely have feelings about non HTTPS sites! I wouldn't say "no" and leave, but I do notice it. Seeing a site with HTTP tends to make me think its older and potentially not well maintained - or at risk of going offline. Its kinda like seeing a house that just hasn't been kept as neatly as its neighboring houses and you think that maybe the owner is not so interested or is having hard times.

I could actually see that being a vibe that someones going for! In the past I would have said paying for HTTPS was not worth it on a personal site; but HTTPS is widely available for free now and its generally accepted as standard ~ it is a little more secure for your visitors and it makes collaborating with things like the surf club work better, but it also makes the site harder to access from retro computers that don't support modern HTTPS ~ so it really depends what your aiming for! 

[larvapuppy]

I use Firefox, so I get a warning when trying to open a non-HTTPS site. If I know what the site is I'll still click through, but if it's an unknown link I usually decide not to visit.

[Semper]

I think it depends on what kind of audience you're trying to cultivate with your website. More tech literate users will have a better idea of what's going on with your website not having HTTPS and give it a chance, while those who are less knowledgeable will heed their browser's (kinda overblown tbh) warning. That could be a positive if you want to talk more with people who are on the same page as you are. Also, if you're looking to make money off of your personal website in some way then you should absolutely have HTTPS, even if the money making is done through promoting something on your site like through a blog post or newsletter and the links go to a HTTPS site like Patreon or Ko-fi. Also like Melon pointed out, having a site without HTTPS means it runs the risk of breaking a webring's link circle and driving off anyone browsing who might not know what is going on. This could look bad for the webring your site is a part of, especially if anyone who visited the ring starts emailing the webring mods with complaints and concerns. If you want to join webrings in the future then you should get HTTPS.

But here I am rambling and forgetting the pointed question haha. Anyways! A lack of HTTPS does not scare me off because I have an idea of what's going on. I'll only leave if your site starts demanding personal information from me.

Side thought; I wonder if there are any HTTPS free webrings/communities that are built around eschewing this new security requirement to keep their sites accessible to people who use older machines and browsers?

[Dreamwings]

Nyes, after much reading, I have decided I might as well get HTTPS then lol.

dude, im not even gonna lie to you I never check if a website has HTTPS. I have no idea what it even means. I just kinda surf the web, and as long as a site dosent ask me for any info like my credit card, I dont really pay much mind to the HTTPS status of the site :P

Basically, it just means your connection between the server and your computer is encrypted so that no one else on the same network can see what you are doing. Thats why a lot of stuff still says to not do banking on public wifi (although you probaboly still shouldn't because you don't know if someone is peaking over your shoulder) because back in the day when it was more uncommon that was a major security concern as you wuld be sending your raw social security info and passwords over the wifi for all on the network to see.

If you look at your sites listing in the surf club, you'll notice its very broken! This is because its super hard to embed HTTP stuff in HTTPS sites; they just don't get along well 

OOOOOOF! Man, that doesn't look hot lol. Also, I was curiuous why my site's view counter was going up so fast ahah. It has like, 150 views or something in the 6 days or so it's been up which doesn't sound like a lot but it's a lot for me. Which reminds me, I should probably also put the webring code on there.

Side thought; I wonder if there are any HTTPS free webrings/communities that are built around eschewing this new security requirement to keep their sites accessible to people who use older machines and browsers?

I found this one on my internet ring collection-for-later travels (Its under "HTTP / HTTPS"). Kinda like that. Tbh I feel the people on the Commodore 64 aren't going to be able to see it at it's full glory anyways but okie. Even then it's a bit more of an encouragement than a requirement (though one of the reasons why I was considering not, even though I personally don't see the use)

Also, unrelated but @larvapuppy FELLOW SEAL PFP!

[starbreaker]

If your site is strictly read-only, with no forms or other interactive elements, then I won't insist on HTTPS. But if you want me to log in, then it's HTTPS or GTFO.