I'll note that when using multiple windows, I recall that switching the user in one window would switch the user for all other windows as well, so support for simultaneous user sessions would probably have to be added as well.
ruffsl
joined 1 year ago
Call it WebOS or something.
Kind of off topic, but webOS was in fact a thing, but more of mobile OS alternative to android and iOS, first developed by palm, the bought by HP, then sold to LG.
https://en.wikipedia.org/wiki/WebOS
It had a small but active homebrew community, with the HP touchpad being one of the early tablets on the market with an unlocked bootloader and Linux support.
Guess the author's click bait'y title was too much. I'll withdraw their video then.
I've recently been looking into using Backblaze with their S3 object storage for hosting Lemmy, but it looks like they also have personal PC backup cloud offerings. Perhaps you could use them to do both?
That looks neet. Although I suspect this would succumb to the same cross post discoverability issues where URLs pointing to the same video would not match string for string. A better approach might be to facilitate inline embedding of HTML video players into Lemmy using browser extensions, where user scripts could be used to preview youtube links or re-write them to nocookie, allowing the Lemmy web UI to still avoid the use of cross-origin scripts by default.
Found the full transcription for the video from OP author:
Note to self: use
youtube.cominstead ofyoutu.be
for better cross post detection and lemmy integration
For programming tutorials, yep, I also prefer reading documentation instead. Although, it looks like this tutorial these folks put out doesn't have much of anything you could copy from, like terminal commands, given its a recorded walkthrough in using the graphical web UI. YouTube also now allows for searching the auto or manual transcription text, which is handy when creators always forget to include timestamped chapters.
Thanks for the link! Could you explain the difference between Managed Hosting vs Available Packages? The former is for admining your own entire Lemmy instance, while the later is for having an account without having to admin an instance? Perhaps the service marketing page could use a little more context to clarify if those are complementary or mutually exclusive service plans.
Checking the issues tracker for RES, there's not yet any mention of lemmy or kbin:
Perhaps you could ask there. I'd also recommend checking out the Lemmy Plugins & Userscripts community:
Like a file tree view with respect to the context directory? Could be nice if it color coded the file by matching with the respective .dockerignore file as well. I'm always second guessing if I edited the ignore file correctly just after running docker build. Not like I can use git CLI to check if the .dockerignore change was interpreted as intended.