server change?

[jeffp51]

I keep seeing messages that PA is going to switch to a new server, but it doesn't look like it ever happens--It is still showing as "not secure" when I open it.  Does anyone have an update on what is going on?

[willie]

 if this link works better, make a new bookmark

https://www.primitivearcher.com/smf/index.php

[Marc St Louis]

It's been moved and they are working on making it secure.  Hopefully within the month

[Digital Caveman]

The link doesn't help.  Good to know it is being secured.  Will this help with photos?

Sincerely,

[willie]

when the security update happens, we will be using https rather than http. the change should work with seamlessly with most browsers, but some folks may have to update their bookmark.

it does make sense to switch machines before updating the forum. hopefully there will be other features available with the update.

[Eric Krewson]

I have noticed the pictures download much easier, I haven't seen the " file to large" warning yet. I use to get it on about half the pictures I tried to download even after all of them had been resized to be message board compatible.

[Pat B]

It's all being worked on so please be patient.

[Marc St Louis]

I'm surprised it's taking so long to get this secure connection

[Deerhunter21]

I'm surprised it's taking so long to get this secure connection

me too...

[willie]

I have been seeing the https in use for a while, although http still works (or gives a warning for some folks).  try adding an "s" to the http and see if the warning stops

[Digital Caveman]

That didn't work. 

[Deerhunter21]

That didn't work. 

same...

[Marc St Louis]

I have been seeing the https in use for a while, although http still works (or gives a warning for some folks).  try adding an "s" to the http and see if the warning stops

Are you using Mozilla?

[jeffp51]

I am using chrome and it doesn't work for me either

[willie]

I have been seeing the https in use for a while, although http still works (or gives a warning for some folks).  try adding an "s" to the http and see if the warning stops

Are you using Mozilla?

up to date mozilla based seamonkey in linux