The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Had to read through the entire thread before I realized that your use of the word 'dead' was meant in a literal sense and not metaphorical.
With the increase in inexpensive storage space, I only remove contacts which I can't remember any details about. If a person has passed away, they are still in there. If I look through the list and see their name, it is a reminder of the good times we shared.
Otherwise any contact I made over the course of my life or career might be useful down the line, even if I need to make an effort to track them down. On the other hand if it is a person that I don't wish to associate with any more, I move them to the blocked contact section instead.
It would work better if you did not capture and encode a video. Instead, you could try to process each frame with the help of the graphics processor on the fly. And you could lower the frame rate to give it more time. Shirley you don't need so many almost identical frames.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
The link is rated NSFW at work but I grabbed the idea from the Google cache. I was not aware of that reputation of people from imgur, was merely refering to the fact that you had dropped your picture on it.
I have been working on a little dotnet core project that will allow users to create their own site and then post to it. It's really an interesting experiment so I can learn the underlying technologies -- and I've learned a ton so far.
Anyways, I just got my SSL Cert applied to my site so now it is secure for users : https://NewLibre.com[^]
HTTPS & HTTP Still Work
The additionally interesting thing is that I updated the dotnet core site with the existing (and very limited prototype code) and everything is now working perfectly under HTTPS and still works under HTTP if the user selects that.
Cool VStudio Deployment
Mostly, I'm shocked that it still works. I'm also amazed at how easy VStudio 2017 and dotnet core make it to publish your web site. Serious CI and very cool. Also cool that you can test so easily on localhost:<port> then deploy to your prod site and it just works.
You can read about it here: Web server implementations in ASP.NET Core | Microsoft Docs[^]
I found it interesting for our company as there are multiple SignalR projects in the pipeline and that way the developers don't have to implement HTTPS security themselves in their applications (we always struggle with certificates and stuff like that )
Interesting. Thanks. I will take a look at that article. EDIT
Oh, yes, interesting. On my main site I am not employing that at this time.
However, I have also deployed a test dotnet core web site to my DigitalOcean.com droplet (running Linux Debian). I want to soon try deploying this prototype to that environment but I had a heck of a time getting the sample running due to getting nginx (proxy) setup properly to expose it to the outside world.
Firefox is displaying a "mixed content" warning, but I can't see what's causing it. Chrome, Edge and IE11 don't seem to have that problem. (Edit: Now Firefox has stopped complaining about it as well. Weird.)
Did you have to pay for your certificate? Let's Encrypt[^] might have been a better option, especially if you could combine it with PKISharp/win-acme[^] to automate the renewals.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Thanks for all that info.
I will check out those items.
I did pay for SSL cert but only $29 and then additional $24 for static IP which is required.
All hosted on smarterasp.net which is cheap and quite nice and allows direct deploy from VSTudio 2017.
congrats and a quick question ... :
did you encounter any problems with SignalR over https ?
I am asking because I could not make it (SignalR 2.2.3) work using (various types of)
self-signed certificates, no matter how hard I tried ...
Last Visit: 13-Jul-20 12:26 Last Update: 13-Jul-20 12:26