02-01-2020
Update:
I am finding it hard to build a decent app (beyond a very basic app) with Blynk. With four labeled data displays, that "cost" met 400 x 4 = 1600 credits. That means I cannot add more of value (like another country or two's datasets for the Wuhan virus and a data chart), without getting into the “feed Blynk money”¯ business model. Blynk is starting to feel "disappointing". I was advised to “just give Blynk another 1000 free credits to share”¯; but I don't have any “free credits to share”¯ because this “very tiny app”¯ leaves me with only 400 "Blynk energy credits".
As many people know, I have a very low threshold for corporate greed, and surveillance capitalism in general, and I have promoted Blynk in the public service cause; but I think I was premature in doing so due to Blink's business model.
So, after this experiment with Blynk, I'll probably stop developing public service apps with Blynk. I have already "learned" the impression that Blynk is quite a bit more “feed me money”¯ than I care for; based on my experience with this public service app today. Unfortunately, as some know, I have a very low threshold for the "Blynk-like" business model, as I have come to understand it. Maybe I simply do not understand it?
People keep saying Blynk is "free"; but Blynk is not free for any real useful app. Everything in the app has a “cost”¯ and after we use the very tiny “2000 Blynk energy credits”¯ we have to pay real money. What am I missing? Any user created app of more than a few small data parameters exceeds the "free credits" provided by Blynk. I find today, I cannot add a chart of the Wuhan coronavirus without digging into my bank account to feed Blynk's requirement for "real coin" on a public service app. I don't have the “Blynk credits”¯ to add more countries, charts, or whatever. It's seriously - pay to play.
This Blynk business model is not designed for public service, as I have experienced over the past day.
Also, on the tech side, I do not like / appreciate it when we create a Blynk app on our phone, Blynk just “deletes it”¯ without warning. I was running a test server monitoring app one phone, and the Wuhan stats app on another phone, and Blynk just deleted the server monitoring app and replaced it with the Wuhun stats app without warning me. I'm not happy about this at all. My work on that "server monitoring app" is gone from Blynk; there appears to be no mechanism to save the Blynk app we created in the phone, so after Blynk deletes it, all that work is GONE!
Anyway, I have a low threshold for the things I am seeing with Blynk, especially after building a public service app, meant only to help others who are in crisis, and learning more about Blynk today, in the process.
This User Gave Thanks to Neo For This Post:
6 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
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
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?
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
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
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
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
LEARN ABOUT SUSE
vfs_scannedonly
VFS_SCANNEDONLY(8) System Administration tools VFS_SCANNEDONLY(8)
NAME
vfs_scannedonly - Ensures that only files that have been scanned for viruses are visible and accessible to the end user.
SYNOPSIS
vfs objects = scannedonly
DESCRIPTION
This VFS module is part of the samba(8) suite.
The vfs_scannedonly VFS module ensures that only files that have been scanned for viruses are visible and accessible to the end user. If
non-scanned files are found an anti-virus scanning daemon is notified. The anti-virus scanning daemon is not part of the Samba suite.
Scannedonly comes in two parts: a samba vfs module and (one or more) daemons. The daemon scans files. If a certain file is clean, a second
file is created with prefix .scanned:. The Samba module simply looks if such a .scanned: file exists, and is newer than the pertinent file.
If this is the case, the file is shown to the user. If this is not the case, the file is not returned in a directory listing
(configurable), and cannot be opened (configurable). The Samba vfs module will notify the daemon to scan this file.
So what happens for the user in the default configuration. The first time a directory is listed, it shows files as 'file is being scanned
for viruses, but after the first time all files are shown. There is a utility scannedonly_prescan that can help you to prescan all
directories. When new files are written the daemon is notified immediately after the file is complete.
If a virus is found by the daemon, a file with a warning message is created in the directory of the user, a warning is sent to the logs,
and the file is renamed to have prefix .virus:. Files with the .virus: prefix are never shown to the user and all access is denied.
This module is stackable.
CONFIGURATION
vfs_scannedonly relies on a anti-virus scanning daemon that listens on the scannedonly socket (unix domain socket or UDP socket).
OPTIONS
scannedonly:domain_socket = True
Whether to use a unix domain socket or not (false reverts to use udp)
scannedonly:socketname = /var/lib/scannedonly/scan
The location of the unix domain socket to connect to
scannedonly:portnum = 2020
The udp port number to connect to
scannedonly:scanhost = localhost
When using UDP the host that runs the scanning daemon (this host needs access to the files!)
scannedonly:show_special_files = True
Whether sockets, devices and fifo's (all not scanned for viruses) should be visible to the user
scannedonly:rm_hidden_files_on_rmdir = True
Whether files that are not visible (.scanned: files, .failed: files and .virus: files) should be deleted if the user tries to remove
the directory. If false, the user will get the "directory is not empty" error.
scannedonly:hide_nonscanned_files = True
If false, all non-scanned files are visible in directory listings. If such files are found in a directory listing the scanning daemon
is notified that scanning is required. Access to non-scanned files is still denied (see scannedonly:allow_nonscanned_files).
scannedonly:scanning_message = is being scanned for viruses
If non-scanned files are hidden (if scannedonly:hide_nonscanned_files = True), a fake 0 byte file is shown. The filename is the
original filename with the message as suffix.
scannedonly:recheck_time_open = 50
If a non-scanned file is opened, the vfs module will wait recheck_tries_open times for recheck_time_open milliseconds for the scanning
daemon to create a .scanned: file. For small files that are scanned by the daemon within the time (tries * time) the behavior will be
just like on-access scanning.
scannedonly:recheck_tries_open = 100
See recheck_time_open.
scannedonly:recheck_time_readdir = 50
If a non-scanned file is in a directory listing the vfs module notifies the daemon (once for all files that need scanning in that
directory), and waits recheck_tries_readdir times for recheck_time_readdir milliseconds. Only used when hide_nonscanned_files is false.
scannedonly:recheck_tries_readdir = 20
See recheck_time_readdir.
scannedonly:allow_nonscanned_files = False
Allow access to non-scanned files. The daemon is notified, however, and special files such as .scanned: files. .virus: files and
.failed: files are not listed.
EXAMPLES
Enable anti-virus scanning:
[homes]
vfs objects = scannedonly
scannedonly:hide_nonscanned_files = False
CAVEATS
This is not true on-access scanning. However, it is very fast for files that have been scanned already.
VERSION
This man page is correct for version 3.5.0 of the Samba suite.
AUTHOR
The original Samba software and related utilities were created by Andrew Tridgell. Scannedonly was developed for Samba by Olivier Sessink.
Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed.
Samba 3.5 06/18/2010 VFS_SCANNEDONLY(8)