handmade.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
handmade.social is for all handmade artisans to create accounts for their Etsy and other handmade business shops.

Server stats:

36
active users

#tasker

0 posts0 participants0 posts today
Mac Berg<p>As <a href="https://mastodon.online/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Android</span></a> is becoming more and more locked down, trying to become <a href="https://mastodon.online/tags/iOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>iOS</span></a>, I see fewer and fewer reasons to use it. <a href="https://mastodon.online/tags/Tasker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Tasker</span></a> (the best ever case for Android) getting nerfed over the years, <a href="https://mastodon.online/tags/SyncThing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SyncThing</span></a> canceling their official Android app due to Google's shenanigans regarding Play rules etc. Why use "spying af iOS" when I can use the original "a bit less spying iOS"? Please for the sake of humanity, can proper <a href="https://mastodon.online/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> mobile become a viable thing already?</p>
Jan ☕🎼🎹☁️🏋️‍♂️<p>How do people deal with ad blocking on dns level when out of the home, on Android? </p><p>I don't want to have a vpn running 24/7, nor do I constantly want to be using some external dns service.</p><p>Right now I have a Tasker automation that switches my dns to nextdns when not on my trusted WiFi, but often the switcheroo gives problems.</p><p><a href="https://fedi.kcore.org/tags/adblocking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>adblocking</span></a> <a href="https://fedi.kcore.org/tags/dns" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dns</span></a> <a href="https://fedi.kcore.org/tags/android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>android</span></a> <a href="https://fedi.kcore.org/tags/tasker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>tasker</span></a> <a href="https://fedi.kcore.org/tags/automation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>automation</span></a></p>
Fabio Manganiello<p>📦 <a class="hashtag" href="https://manganiello.social/tag/platypush" rel="nofollow noopener noreferrer" target="_blank">#Platypush</a> <a href="https://pypi.org/project/platypush/" rel="nofollow noopener noreferrer" target="_blank">1.3.0 is out</a>!</p><p><a href="https://git.platypush.tech/platypush/platypush/src/branch/master/CHANGELOG.md#1-3-0" rel="nofollow noopener noreferrer" target="_blank">This release</a> turns <a href="https://git.platypush.tech/platypush/platypush/issues/341" rel="nofollow noopener noreferrer" target="_blank"><em>procedures</em> into first-class citizens</a>.</p><p>Procedures are the bread-and-butter of Platypush customizations. They allow you to specify some custom logic that can run within the application, either from structured requests or code snippets - both <a class="hashtag" href="https://manganiello.social/tag/python" rel="nofollow noopener noreferrer" target="_blank">#Python</a> and <a class="hashtag" href="https://manganiello.social/tag/yaml" rel="nofollow noopener noreferrer" target="_blank">#YAML</a> scripts are supported. They are akin to recipes in <a class="hashtag" href="https://manganiello.social/tag/ifttt" rel="nofollow noopener noreferrer" target="_blank">#IFTTT</a> and tasks in <a class="hashtag" href="https://manganiello.social/tag/tasker" rel="nofollow noopener noreferrer" target="_blank">#Tasker</a>.</p><p>You can call them from an event hook when a certain condition is met, from a cronjob or an alarm, from stand-alone scripts, from other procedures, and so on.</p><p>This release improves the integration of procedures into the UI, turning them into entities that can be controlled from the <a href="https://docs.platypush.tech/wiki/Entities.html" rel="nofollow noopener noreferrer" target="_blank">entities panel</a> - and, <a href="https://git.platypush.tech/platypush/platypush/issues/228" rel="nofollow noopener noreferrer" target="_blank">soon</a>, embedded into custom dashboards.</p><p>It also introduces a new powerful procedure editor, which allows you to visually create your automation routines through an intuitive UI with drag-and-drop support (a big part of this release has been about getting drag-and-drop to work nicely on mobile too). The new UI supports nested if/for/while blocks, break/continue/return, setting context variables, variable name autocompletion, export to YAML (if you prefer to have your procedures stored in the configuration rather than the db), and more.</p><p>This UI has been inspired by the job done by Joao Dias on Tasker (I’ve always wanted to have a similarly powerful block-based UI to create custom routines also on desktop/server), and in part by IFTTT’s recipe editor.</p><p>This release also includes a new file browser component. You can now browse your files on the Platypush instance, create/edit/delete/upload/download them directly from the Platypush UI, even if you don’t have SSH access to the machine.</p><p>Happy hacking!</p><p>Python procedures can also be easily managed through a new file editor component that allows you to precisely navigate to their definition.</p>