Closed sunlightspectre closed 6 months ago
Thank you for your kind words!
That is kind of unusual you are getting that. OldGlory opens a connection to 1.1.1.1
before it checks for any updates, which theoretically should work for any internet.
That is kind of unusual you are getting that. OldGlory opens a connection to
1.1.1.1
before it checks for any updates, which theoretically should work for any internet.
Wild, that's super simple and I cannot think of any reason it should fail to work for my connection.
I'm going to close this one because I've got no clue what to test or try, but I'll add a comment and @ you if I figure anything out.
And, of course, you're very welcome..!
Wild, that's super simple and I cannot think of any reason it should fail to work for my connection.
Can you ping 1.1.1.1?
Can you ping 1.1.1.1?
Oh yeah, just as reliably as ever! It's pretty wild, honestly. Since it's a comparatively minor issue, I actually find weird edge cases like this hilarious. Later, I'll try moving oldglory to a different box with a similar setup and see if I get the problem there.
Mostly, this is just a sincere and heartfelt thanks for maintaining this.
It is such an incredible relief to have at least one program rolled back to usability by your work.
Thank you, very much..!
As for the bug(?) report, it's as above.
Here's an image example.
Emphatically, I am online. c;
SteamOldGlory shouldn't have a block on Windows Defender.
I've no idea what else could be causing the problem.
But given I'd imagine future updates probably won't be small ones and updating from the git is easy -
What with all the options I'd done myself now handily natively supported...
This is very much low priority. See paragraph one, and one last time with feeling - thank you.