DATACOMMANDER

I recently created a web application that wasn't quite good enough to turn into a product, but was interesting enough to garner attention from the CEO of a major site in the space. I was close to being offered a contract position with that site, but the offer was ultimately rescinded. The CEO and the dev who spoke with me about my project seemed apologetic, but from the start of the interaction the vibe was that they hire people who are experienced and can jump right into their frameworks and go. Although I learned a lot from the project, I'm not an experienced dev and I'm not an expert in any frameworks.

Should I put the backend code for the project on GitHub? Should I link to the app in my LinkedIn profile? I'm partly just depressed that the contract position didn't work out, and I'm even a bit reluctant to create a portfolio website because I can only show off this and one other project (which I did earlier and is much less impressive). I know that I could apply to open junior dev positions and link to my projects, but to be honest I just don't believe that I'll get a response.

I suppose that I'll do all of those things, and I'm not sure what sort of response I'm expecting here; maybe I just needed to vent. Thanks for listening.

I just want to make sure I'm not missing something. By "[download] a stream" I obviously mean "save video that you're streaming to permanent storage". I'm doing an interview project that involves working with a "streaming as a service" (terminology?) provider, so I thought I'd go to PBS's website and download some video to use in the project. I found that all of the video there is only available to "stream", and in fact uses a video player and "streaming as a service" provider that's in the same space as the company I'm interviewing for. Five seconds on google revealed a "PBS video downloader", which I assume just locates the video segments in the browser's temp folder, stitches them back together, and saves them to a location that won't be cleared on reboot.

My question is basically, "That basic procedure can always be performed and there's nothing that can be done to prevent it, right?" Isn't the distinction between "streaming" and "downloading" ultimately just about how the video data is delivered? The server is incapable of ensuring that the client doesn't save it to permanent storage, and a "cooperative" client can always be modified by the person who controls it to save the data, assuming it's physically connected to a storage medium.

Am I missing something fundamental that allows there to be a hard distinction between streaming and downloading?

NB: I don't have any moral qualms with providing streaming video, I just think that the business folks wish that there were a technical distinction that, AFAICT, does not exist.

I have a bit of frontend experience and a general understanding of how backends work, but I guess the "glue" layer between them must be more difficult than I think. Why is it that when I need to reset a password, or log in or out, the site that I'm interacting with is unable to handle even basic state? I'm not blocking cookies, so it can't be that.

Can't the page/endpoint that I left in order to reset my password be encoded into the password-reset URL, so that after my password has been reset I'm brought back to where I was?

Password resets aren't the only manifestation of this, but they're the most obvious.