The risk of access to the router is more that they can access your network and touch unprotected and vulnerable things rather than active monitoring.
9,034 karma · joined January 12, 2017
The risk of access to the router is more that they can access your network and touch unprotected and vulnerable things rather than active monitoring.
The purpose of dating work is so that if your copyright is contested, you will have evidence that you created the work first. This is done by obtaining an officially recognized dating, which is usually done through registration with the copyright office (the registration has no other legal purpose after the Berne convention was adopted). External evidence or dating can also be used, e.g. having mailed the work to yourself and thereby having the work dated by the post office, having music be on hitlists, etc.
Writing the date on the work yourself has no value whatsoever. Dynamically injecting the current year has negative value as you are undermining the age of your work and thereby harming your ability to defend it as being the work first created.
In the case of a website, the only valuable evidence in proving the age of the content would be external content references and archive.org scapings.
That repos haven't been pushed in a number of years is slightly supsicious, although they could just have taken things internal.
(Open source licenses do not require pushing to public github, only that someone obtaining the application can also obtain a copy of the source used to make it - can be an inquiry leading to a flashdrive by snailmail.)
Nowadays your webapp is often a persistent, multi-threaded web server where you can cache whatever temporary state you want far more efficiently than reaching out to a KV store.
Using postgres and caching common results becomes a non-issue even at scale. The main area where a super fast KV store shines is when you need to share a very large number of keys, where many servers only need to access a random subset and isn't interested in maintaining the full set and getting updates on a bus, where the values often change and needs to be revalidated so caching is ineffective, and where persistence is not needed so a database doesn't matter and a lighter KV store is acceptable.
The message is that the app developer in question's argument that they have nothing to update is most likely false, not that special industries is a driver for the policy.
But if that random game should, say, fetch user avatars from the web, then untrusted input to a way out of date image decoding library would be a nice path to a remote code execution vulnerability.
Or if the app registers any intent handlers that other apps and websites can trigger, or establishes TLS connections to any third party site, or...
When using web apps, the browser you bring is no different than, say, having to install Qt. It's a static entity shared by all apps, with each app "just" being anywhere between kilobytes and tens of megabytes.
Electron brings a browser, but even then what makes the app bloated is still design Theres a baseline amount of bulk included, but it's mostly inconsequential to the actual app behavior - similar to how a standard system has god knows how many libraries and functions available but mostly unusued.
You could easily have an app written with PyQt that's way more sluggish, bloated and complicated despite using a fraction of the disk space. Shitty apps, that's the issue.
When "going elsewhere" means "getting stuff cheaper", people are likely going to go elsewhere to pay for any subscription even if setup is notably less convenient.
Making good apps is hard.
A CLA often tries to mitigate this by making contributors give the project owners special rights at the time of contribution.
(Note that even if relicensed, this itself can never revoke licenses granted for prior versions unless that license specifically had revocation written into it.)
No, where I live all education is provided as a free service. The US education system, putting people into a life of debt just acquire the minimum of marketable skills, is broken beyond repair and not a valid point of comparison.
On the other hand, people with qualifications also demand reasonable salaries and need to pay taxes. "Private tutoring" is not a 10 minute zoom call.
The alternative to being s business in s transaction is being a consumer (as in B2C), and you're obviously not a consumer when publishing an app.
Doing business is orthogonal to being a company, and depending on your country, some "company" forms are just VAT filing registrations for an individual itself with no independent legal status. What you normally call a company is something that behaves as an independent legal person.
However, it may be legally required to register a proper company if your yearly business volume exceed a certain value - check local rules - but it may also be perfectly fine to do business as an individual below that volume, in which case the legal entity is just you.
(The alternative to being a business in a transaction is being a consumer)
Your license text is only capable of adding supplementary rights, and you're responsible for ensuring that your source license is fully compatible with the contract at time of publishing.
If you just want to dump stuff, leave it on GitHub.
Having to go through between zero (it you have needed the number before) and one free forms from a standard entity to get a widely recognized identifier used for many things is objectively not an excessive effort.
Sharing apps on app stores is a continuous commitment with various responsibilities like, such as ensuring safety of users through regular maintenance. If the idea if submitting one number is too much of a burden given the joy/finances you get out of it, then the rest of the maintenance responsibilities likely are too and maybe it's better to skip the publishing part.
Not sure what you're on about with corporate colonization. Colonizing implies forcefully taking what was rightfully someone elses. Also, in many places, making a company is just a form and standard practice even if you're just going to sell a single bogus app for 0.99 USD or whatever, so even individuals will be "corporations".
A bit silly to require for private individuals, and a bit annoying to have to go back and do, but not itself a big deal.
Try to force some more exchanges with your wife. Make a day of the week the day you only speak her language (for at least a few hours, but don't give up from the frustration when vocabulary runs short - keep it going even if you need to point and sign).
Doubles as a silly/fun couples activity.
Language should not be reserved for people that can throw that kind of money monthly at their random hobbies, and suggesting that this is "the solution" is grotesque at best.
You also end in a false dichotomy.
Specifically, I consider the fundamental missing piece to allow achieving language intermediacy or fluency to be confidence and sporadic language use, and you have to be lucky for a language class to give you this. Hearing about grammar and having Q&As is nice, but that teaches language theory, not fluency. Trying to converse about a specific topic with other non-fluent and disinterested individuals does not teach fluency, and not every conversation will be with the teacher - the only (hopefully) fluent person in the room - and even if the option is present, some might be uncomfortable with it.
On the other hand, if you have achieved some confidence and means to exercise the language - which you don't acquire from a language class - then I'd consider Duolingo to be a decent vocab and sentence exercise tool. Some cultures rely on flashcard approaches to teach their written language to locals, so it's not that silly. Duolingo does also have reading and listening comprehension tests.
Furthermore, I'd argue that newer LLM-based exercises might end up being superior to both traditional "pool of random non-fluent people" language classes and duolingo's current model, and arguably the task that large language models are most suited for.
(Note that Duolingo classes differ a lot between languages - my experience is from Mandarin.)