- DOES FLASHFXP NEED TO BE RUNNING FOR SCHEDULED TASK TO RUN SOFTWARE
- DOES FLASHFXP NEED TO BE RUNNING FOR SCHEDULED TASK TO RUN DOWNLOAD
This is actually a really ridiculous situation.
DOES FLASHFXP NEED TO BE RUNNING FOR SCHEDULED TASK TO RUN DOWNLOAD
Sourceforge download statistics tracking of releases (including graphing per country and with arbitrary timestamps) is far superior to Github, which doesn't offer even private tracking of download numbers without directly using their API.
DOES FLASHFXP NEED TO BE RUNNING FOR SCHEDULED TASK TO RUN SOFTWARE
The forum can be configured for users to be able to post without creating an account (though only as a specific user named "Anonymous", not arbitrary names) which is as important feature when creating software for users who aren't likely to have Github or Sourceforge accounts. Here is a review that might help some people.įor general project discussion, Sourceforge's traditional discussion forum is far superior to Github/GitLab issues (though I haven't tried Github Discussions beta yet). The new Sourceforge team has generally done a great job. You'd never actually make that stick in court. But like I said that's just fantasy academic theory. You'd never actually win in court, but in plain conversational argument, if say the crapware caused some damage, the vendor could't claim that the user voluntarily accepted the risk of damage by voluntarily installing the software. It also invalidates any arguments based on "the user accepted" something. It's that it exposes the true intent in a way that can't be denied. The norm is already bad, and this is just a little more of the same.
But that just doesn't quite add up to proof of anything.īut offering one extra, and then only trying again with another if the user declined the first, THAT exposes that the only intent of the extra was to get the user to take it any way they can manage to do it, and not a sincere "offer" of something the user might have actually voluntarily sought otherwise. You could try by pointing out things like how the outer packaging only said that the contents would be Product not Product+OtherProduct, and how the checkbox for the non-advertized and un-expected extra was pre-selected and visually tiny. We "just know" that's bs, but it's possible and it's hard to disprove purely on the face of it. If an installer always proposes an extra, or 2, or 13, then the vendor can claim "I'm just offering this extra that I honestly and sincerely believe the user might be interested in and might benefit from". The special difference is just that it exposes the intent which was theoretically deniable otherwise, even if everyone "just knows" what's really going on. That dynamic reactive 2nd attempt to trick you, which is only invoked if you caught and declined the first, is materially different from the first attempt, and different from if the installer always presented both extras.
I think it would be a very weak case and practically impossible to make that argument. It might possibly qualify as an attempt to deceive. In this example, we will schedule a closure to be called every day at midnight.I didn't say it was illegal, just dickish.įraud. To get started, let's take a look at an example. You may define all of your scheduled tasks in the schedule method of your application's App\Console\Kernel class. To help you get started, a simple example is defined within the method. Your task schedule is defined in the app/Console/Kernel.php file's schedule method.
When using the scheduler, only a single cron entry is needed on your server. The scheduler allows you to fluently and expressively define your command schedule within your Laravel application itself. Laravel's command scheduler offers a fresh approach to managing scheduled tasks on your server. However, this can quickly become a pain because your task schedule is no longer in source control and you must SSH into your server to view your existing cron entries or add additional entries. In the past, you may have written a cron configuration entry for each task you needed to schedule on your server.
0 kommentar(er)
