jonathanvmv8f

The clones retain the same physical attributes and memory as the original 'you' just before the replacement. From the clone's perspective, it would be as if you swapped places with another person with no context of the situation that person was in, except it's with every living person on earth, everyone but you cease to exist and the original 'you' isn't affected in any way.

How would you imagine the world to become after this? How would the society act now that it has become entirely composed of 'you's? How would you and your clones live the rest of your lives in such a world?

I wish to understand what elements or aspects of the design of modern websites the end users are annoyed from. Though you are free to express your personal opinions, it would be even more insightful if you could provide objective criticism and suggestions for alternative implementations so that I may incorporate the same in my current and future projects to make them as user friendly as possible.

Some criticisms I have encountered a while back include:

• Switches being basically checkboxes with more ambiguous active state
• Scrolling animations that prohibit user from linearly scrolling through the page

Make sure that the opinion is not

• Related to business/legal matters e.g. Cookie consent notices, ad banners etc.
• Too vague e.g. Poor website layout
• Highlighting objectively bad practices e.g. Lack of accessibility features

I recognise I could have followed a design system for this question, but I want to understand the situation from the perspective of the end users to see if they have a differing view on what a convenient user experience should be like.

I saw a comment yesterday about how IT admins have to restrict the privileges of other developers on their machines and was surprised by knowing this. I simply thought that employees in the software industry were essentially at equal parity in terms of their departments, and that the admin department was there just to centralise all the work done by other departments and keep track of the status of their systems. I did not think there would be a need to apply childlocks on other employees' systems as I assumed that a person working at an industry like this would have basic computer literacy to know what is safe and permissible by company policy to execute and what is not.

This may come off as being too naive of me, but I genuinely want to understand how the hierarchy in such a company is actually like. I always thought of workspaces in the software industry to divide labour laterally and there would be no need for administrative powers apart from the management to exist, at least in regard to regulating other workers' actions beyond normal workspace policies. It would be extremely kind of anyone to shed light on this matter.

What does the launcher do with regard to the operation of the game that cannot be done within the actual game itself? Is it due to a technical limitation or simply there for the convenience of the players? Are there alternatives to such methods of starting the execution of games?

Imagine you wake up in the body of a famous and influential person in the bedroom where that person sleeps in. You know nothing about that individual prior to this incident apart from the fact that they are considered a high profile person.

Your only chance of survival here is to act like that person in front of their family, friends and the public for the rest of the unforeseeable future. How do you ensure you learn to imitate the personality of the individual by arousing the least amount of suspicion?

I haven't read any scientific journal or publication not because of the sheer volume or complexity of the content within but rather the extremely formal and scientific language of the content that makes them feel soulless and more like a punishment to the person reading them. I would really like it if someone could recommend a paper, preferably in the field in science and pertaining to an easy topic, where the author has some sense of humour and is able to retain my attention span all the way till the end.

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.

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:

1. I am using NextJS to build this application and Dexie to manage indexedDB
2. 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
3. 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.