This link to the wiki is incredibly helpful for me in order to gain context about the comic series. Thank you kind stranger!
It's incredibly awesome seeing a talent like yourself posting regularly on a platform like Lemmy. I fully respect and commend you and your efforts to actively engage with the community here, regardless of how I make sense of the comics personally.
OK, I am willing to break the ice here: What is this community actually about? I've been seeing these comics in my feed for the last 3 months and trying to connect the dots between the posts to get the idea behind the lore, but so far I'm drawing a blank apart from a hint that it could be related to Linux. Maybe I need to be a computer nerd to get the jokes or....I am not taking the community title seriously enough.
For further context, the website is virtually completely local and could be self-hosted. Aside from hosting the project itself, there is no central server to manage any aspect of the users' interaction with the site or allow communication with other users. There is no sensitive data stored barring the name of the user for which a pseudonym would be just as acceptable.
I think mentioning the ToS and privacy policy is pointless for creating an app like this. If it is possible, I would rather write them myself or omit them altogether.
How bored and fed up of your life would you have to be to be willing to read an entire Terms and Conditions page for entertainment?
What to write in the 'Terms of Service' and 'Privacy Policy' of my open source project?
I don't know what to write in both of these pages before I publish my project. I would greatly appreciate if someone would help me in this regard as I know nothing about the legal side of hosting open source apps nor do I want to spend too much time on this.
For context, my project is a web app that I specifically made sure to be as private as possible. All data generated by the user is made to be completely stored locally in the browser with no trackers or analytics installed. The data can be modified and deleted as per the user's will along with the ability to import and export the data as JSON files. A local account is required to save progress else the data will be wiped on exiting the site and the core functionalities of the site do not depend on whether an account has been created or not. The only privacy risk would be occasional loading of external resources like image links which I couldn't find a viable alternative to.
Frankly this is just a small side FOSS project which I do not intend to capitalise on. I still want to mention the TOS and the Privacy Policy just in case, but I couldn't be bothered to write all this legal matter by hand.
How to ensure my web app has backward compatibility with importing JSON based user data?
I am working on a small web app that stores user data locally using indexedDB which can be imported/exported by making use of JSON files. Since I plan on adding updates to the site, I want to know what best practices I should follow to make sure my app can allow importing of user data from older versions. It could be related to how I should define the properties of my user data object to make it future proof, or any library or tool I could implement that would make this migration process easier.
Do keep these points in mind:
- I am using NextJS to build this application and Dexie to manage indexedDB
- Without going into details, the user data file makes use of heavily nested objects and arrays and most likely won't fit in a cookie or even in the local storage API
- This web app acts as a proof of concept which must only make use of the aforementioned core technologies, regardless of whether more efficient alternatives exist or not.
I like to think that he forgets, keeps trying and then makes a new post about it
I would really like to get more about the 'business megaformal' option if I knew what it was called in real life
It was nice to have someone take this stand and I fully support this. People switching over to Linux already have their own stuff to deal with and need time to accustom to their new environment, and forcing them to embibe 'FOSS' philosophy and other strong opinions as held by others in Linux communities is only going to turn them off.
The Emptiness Machine by Linkin Park.
Listened to it for the first time two days ago and kept it going since
This is why [...] better
Sorry, what's the subject of that?
I was just referring to my original question i.e. how I should write comments in my code to explain its working if I have already done so in the code itself
Interesting to see your opinion on how commenting shouldn't be mandatory. I specifically go the extra mile to ensure my code is readable for everyone, by naming my variables and functions to be as self-explanatory as possible and breaking down long expressions to store chunks in variables. This is why I was feeling confused as to what more I could add to explain my code better, though I must admit there are still considerable complex portions in some of my projects that would appreciate similar simplification.
I believe you confused the 'how' of commenting the 'why' with 'why' of commenting the 'why', if that makes sense.
I am already aware of and totally agree with the need to document your code in this fashion for the convenience of others and self. What I am troubled about is its implementation in real life. How does one write comment that explains the 'why' of the code? How would I know if I haven't accidentally written something that explains the 'what' instead or anything that is simply redundant? It seems like this portion is left out 'as an exercise for the reader'.
Asking as a newbie programmer: how do you suggest we write comments that explain the 'why' part of the code? I understand writing comments explaining the 'what' part makes them redundant, but I feel like writing it the former way isn't adding much help either. I mean, if I created code for a clock, is writing "It helps tell what time it is" better than writing "It is a clock" ?
It would really help if someone could give a code snippet that clearly demonstrates how commenting the 'correct' way is clearly better than the way we are used to.
Need help introducing friends to Minecraft for the first time
I want to introduce some of my friends to Minecraft. They have never heard of it before and I am having trouble explaining them from the beginning since the scope of the game is very vast.
I want to give them a preview of the game before they start playing themselves, so I would prefer a video explaining the same. I tried to search for it on YouTube but I could personally find no video that could explain the premise and potential of the game from scratch. I tried to explain them via playing the game on my device too but that was of no meaningful help either since I have no personal worlds or builds to show.
Could someone please help me recommend some useful resource for this matter? I am sure they will come to love it once they get to properly understand it.
Though I appreciate the reply, I was looking for the difference between a remaster and a remake specifically. I think both of them should mean the same thing essentially.
What is the difference between the former two?
I got my gaming rig recently and played all the releases up to Rogue only this year. I assure you my specs are modest enough and it's just the game that is poorly optimised. Even Watchdogs 2 ran better than this.
Unity was the game I was most hyped for, especially because of its graphics and bigger maps. I even went to speedrun through the last three games to catch with the lore and begin playing it as soon as possible.
Alas, my PC couldn't meet up with the heightened hardware requirements and I had to give up after barely finishing the tutorial with the awful frame rates even with the settings set to minimal.
What interesting things can I do with my home WiFi network?
I recently learned about LocalSend and was intrigued by how it functioned by only using the WiFi network of the devices. I did not know my LAN had these capabilities.
Now that I've learned about it, I am excited to know if there is anything else I can do with it. Perhaps there could be a way to send prank notifications to all the connected devices, create a private chat room, or have custom LAN parties.
I genuinely do not know anything about how WiFi or LAN in general works in this matter. Is it possible for me to build my own applications that make use of these features? If so, I would love to get a direction on what resources or guides I should be looking for. If not, I would still be happy to use similar pre-built applications.
Thank you so much! I checked that he starred in the show 'Severance' which I just watched recently, which is why I could recognise his face.
Make this thread look like it's your first day on the internet
cross-posted from: https://lemm.ee/post/41811290
> I think the use of this meme format already counts as one
Make this thread look like it's your first day on the internet
I think the use of this meme format already counts as an example
How do you realistically build your own OS with Arch Linux?
cross-posted from: https://lemm.ee/post/40063668
> As a Linux newbie, all I know about Arch Linux is that it is a DIY distro where you assemble the entirely of the OS by scratch. Somehow it feels like it is too easy than it needs to be, even if it is primarily meant for experienced users. I imagine it to be less like building your PC from parts bought from the market and more like building each and every component of the PC by scratch along with building the PC, which I assume to be much harder for the average consumer. > It seems absurd how it is possible for a single person to incorporate the innumerable components required for functionality in a personal system that does not crash 100% of the time due to countless incompatibility errors that come with doing something like this. > > I would like someone to elaborate on how it feels to 'build' a system software by yourself with Arch and how it is reasonable to actually do so in a simple language. I do have some experience in programming, mainly in webdev, so it's not like I need a baby-like explanation in how this works but it would be nice to get to know about this from someone who could understand where this confusion/curiosity is coming from.
How do you realistically build your own OS with Arch Linux?
As a Linux newbie, all I know about Arch Linux is that it is a DIY distro where you assemble the entirely of the OS by scratch. Somehow it feels like it is too easy than it needs to be, even if it is primarily meant for experienced users. I imagine it to be less like building your PC from parts bought from the market and more like building each and every component of the PC by scratch along with building the PC, which I assume to be much harder for the average consumer. It seems absurd how it is possible for a single person to incorporate the innumerable components required for functionality in a personal system that does not crash 100% of the time due to countless incompatibility errors that come with doing something like this.
I would like someone to elaborate on how it feels to 'build' a system software by yourself with Arch and how it is reasonable to actually do so in a simple language. I do have some experience in programming, mainly in webdev, so it's not like I need a baby-like explanation in how this works but it would be nice to get to know about this from someone who could understand where this confusion/curiosity is coming from.
How do I know if tinnitus is some sort of a placebo effect?
What if I am just imagining the high pitch sound in my mind whenever I hear about or think of tinnitus just like how someone tells you to imagine a whale and you form a mental image of a whale? I don't pay attention to the noise while I'm busy doing stuff but once I think about it, it is as hard to stop noticing it similar to being told to breathe manually, and it gets very annoying after some time. Is it what tinnitus really is?
What video games would you rather watch someone else play than play it yourself?
For me, it is any city/building construction game like City Skylines, Two Point Hospital, Planet Zoo etc.