Sponsored Content
Top Forums Programming Wuhan Coronavirus Status for China - Rapid Prototype Blynk App with ESP8266 Post 303043591 by Neo on Saturday 1st of February 2020 11:14:06 AM
Old 02-01-2020
Update:

According to the network, Blynk has apparently responded to my honest opinion and review of their product and business model by blocking our two apps we are running, but that is OK, I expected as much from the Blynk team.

I woke up this morning and built an app using Blynk to help the good people of China in a national crisis.

Now, at the end of the day, I am very unhappy, 100% of that unhappiness is because of Blynk.

Both my apps are now blocked from the Blynk network because I provided an honest assessment of their business model.

Blocked Wuhan Virus in China App (Blocked By Blynk):


Wuhan Coronavirus Status for China - Rapid Prototype Blynk App with ESP8266-blocked_blynkjpeg


My mistake in this task was in choosing Blynk for this app. I will not make that mistake again.
 

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Function prototype declaration

Hi All, I have the script as below #!bin/bash let k=9 if then echo "Start" Hello echo "End" else echo "failed" fi function Hello() { echo "hello !!!!" } I got the below error : (4 Replies)
Discussion started by: Balasankar
4 Replies

2. Programming

Embarcadero Rapid SQL query for dependency

Team I am using Embarcadero Rapid SQL V8 . When we right click on any procedure/table/view and open the contents. It has dependencies tab, which tell what all are the dependents used . My question is how does this information captured in backend to retrieve the dependency objects in... (0 Replies)
Discussion started by: Perlbaby
0 Replies

3. What is on Your Mind?

Major Changes in New UserCP (v0.63) Prototype

Regarding the latest version of the UserCP prototype (version 0.63) I have made a lot of major changes, including Added a "Posts Timeline" table for the recent posts, complimenting the non-table version earlier, which has been moved off the main menu (link at the bottom of the table). Added a... (4 Replies)
Discussion started by: Neo
4 Replies

4. Programming

NodeMCU ESP8266 Blynk SSL Application for Linux Server Load Averages

Here is a useful SSL (HTTPS) application for anyone with a remote Linux server they want to keep an eye on using Blynk and the NodeMCU ESP8266. This little app also works (have tested as well) on the WeMos D1 ESP8266 Arduino board. The NodeMCU setup could not be easier, just find a... (8 Replies)
Discussion started by: Neo
8 Replies

5. Programming

Wuhan Coronavirus Status App for China - Rapid Prototype using MQTT and the IoT OnOff IOS App

With a little bit of work, was able to build a nice "Wuhan Coronavirus Status" app using MQTT and the IoT-OnOff app. More on this technique here: ESP32 (ESP-WROOM-32) as an MQTT Client Subscribed to Linux Server Load Average Messages The result turned out nice, I think. I like the look and... (10 Replies)
Discussion started by: Neo
10 Replies

6. Programming

A Slightly Better NTP Client for the ESP8266

Was not really happy with the NTP clients for the ESP8266 because, after a few years of game engine programming, I am not a fan of a lot of code and delays in the main loop, so here is a "slightly better NTP client" for the ESP8266. In a nutshell, instead of having a delay in the main loop as a... (1 Reply)
Discussion started by: Neo
1 Replies
SafeEjectGPU(8) 					    BSD System Manager's Manual 					   SafeEjectGPU(8)

NAME
SafeEjectGPU -- Facilitate safe eject/disconnect of eGPU(s) from system SYNOPSIS
SafeEjectGPU [gpuid <gpuid>] [gpus] [apps] [status] [Eject] [Initiate] [Relaunch] [Finalize] [Cancel] [RelaunchPID <PID>] ... DESCRIPTION
The SafeEjectGPU command is used to prepare for safe eject/disconnect of eGPUs from the system. This involves interacting with apps to migrate off of ejecting eGPU(s), and triggering the eject itself. This tool can also be used to view what GPUs are attached to the system, their eject status, and what apps hold references to each. A list of commands and their descriptions - note that commands affecting state are capitalized, and that multiple (including repeated) com- mands can occupy the same command line: gpus Lists attributes of GPUs currently attached to system (gpuid, vendor/model, flags) gpuid <gpuid> Specifies which GPU(s) subsequent commands apply to. The default (0x0000) means all eGPUs. See output of gpus command for valid <gpuid> values (of the form 0x7005) to use. apps Lists apps holding references to specified GPU - and app attributes/properties like PID, RPID, USER, PROCESS, APIS (Metal, GL/CL, GVA), BUNDLE_IDENTIFIER, PATH, GPUEjectPolicy and GPUSelectionPolicy where specified. status Shows eject state of specified eGPU(s) (Present, Initiated, Finalized). Eject Performs the full Eject sequence ( Initiate + Relaunch + Finalize ) of specified GPU(s). Initiate Initiates eject of specified eGPU(s). These eGPUs are temporarily hidden from API instantiations. Relaunch Interacts with apps that hold references to specified eGPU(s) - to facilitate migration to remaining GPUs. Finalize Finalizes eject of specified eGPU(s) - must be physically unplugged before they can be used again. Cancel Cancels initiated eject of specified GPU(s) - instead of Finalized. RelaunchPID <PID> Apply relaunch stimulus to one particular PID - for app relaunch stimulus testing. EXAMPLES
$ SafeEjectGPU gpus List eGPUs. Output is useful for cut-n-paste of example specified gpuid values used below $ SafeEjectGPU gpus apps status List all eGPUs and Apps on all eGPUs along with eject status of all eGPUs $ SafeEjectGPU Eject Perform full Eject sequence on all eGPUs $ SafeEjectGPU gpuid 0x7005 Eject Perform full Eject sequence on specified eGPU $ SafeEjectGPU gpus apps gpuid 0x7153 apps Lists all eGPUs and apps on all eGPUs and on integrated GPU as well $ SafeEjectGPU Initiate RelaunchPID 12345 Cancel Hide eGPUs and send relaunch stimulus to PID without doing full eject PLIST PROPERTIES
The following properties are generally inferred. Some values can be specified in the app's Info.plist. They affect eGPU eject and API selection behaviors. Generally, these properties won't need to be specified: GPUEjectPolicy Inferred/Settable GPUEjectPolicy values for dealing with apps that needs to drop references to ejecting eGPU. Establisehd in app bundle's Info.plist. Possible values: relaunch Send AppKit quit-with-save event followed by open-with-restore (relaunch app using alternate GPU(s)). wait Just wait for GPU references to drop (without sending events or signals). kill Use sigKill to force app exit (for apps that will relaunch via launchd - using alternate GPU(s)). ignore Ignore - necessary for some internal GPU/display components - working to eliminate its use. Inferred-Only GPUEjectPolicy values (you can't specify these values, but you'll see them as defaulted/inferred policies in apps out- put): wrelaunch Wait momentarily for processing of Metal GPU change notifications before resorting to relaunch (as necessary). jrelaunch Just relaunch without waiting (since OpenGL/OpenCL are in use). rwait When a process is subordinate to another, "responsible", process (see RPID column), Eject actions apply to the responsible process, who in turn deals with subordinates to eliminate their ejecting eGPU references. GPUSelectionPolicy Settable values that affect instantiation of Metal and OpenGL/CL contexts (wrt eGPU use). Established in app bundle's Info.plist. Possible values: avoidRemovable Avoid creation of MTLCommandQueues, and OpenGL/CL contexts on eGPUs. preferRemovable Prefer creation of MTLCommandQueues, and OpenGL/CL contexts on eGPUs. SEE ALSO
plist(5) sudo(8) launchd(8) HISTORY
The command line SafeEjectGPU tool first appeared in the 10.13.4 release of Mac OS X. Mac OS X January 22, 2018 Mac OS X
All times are GMT -4. The time now is 03:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy