... Which means that businesses are making 'too much' money on top to sink into such endeavors, no?
Thank you!
This is what I came up with.
- a script that does what you need, and reads a kinda 'config file' which Konsole instance/window/session to use
- another script that saves the current session into that config file
So you'd save the scripts somewhere you like, and run the useThisSession one in the session you'd like to be the target.
Then, you can run / bind to a shortcut / ... the runCommand script, and it will show, raise, set Session, and run the command on the target saved earlier.
useThisSession.sh:
#!/bin/bash
# useThisSession
echo MYCMD_SERVICE=$KONSOLE_DBUS_SERVICE > ~/.config/mycmdrc
echo MYCMD_SESSION=${KONSOLE_DBUS_SESSION#/Sessions/} >> ~/.config/mycmdrc
echo MYCMD_WINDOW=${KONSOLE_DBUS_WINDOW#/Windows/} >> ~/.config/mycmdrc
runCommand.sh:
#!/bin/bash
# runCommand
. ~/.config/mycmdrc
qdbus $MYCMD_SERVICE /konsole/MainWindow_$MYCMD_WINDOW showNormal
qdbus $MYCMD_SERVICE /konsole/MainWindow_$MYCMD_WINDOW raise
qdbus $MYCMD_SERVICE /Windows/$MYCMD_WINDOW setCurrentSession $MYCMD_SESSION
qdbus $KONSOLE_DBUS_SERVICE /Sessions/$MYCMD_SESSION runCommand "echo cmd"
For testing purposes, I'm using "echo cmd" instead of '!!' (note the different type of quotes) to not cause any... unintended... executions.
Running qdbus $MYCMD_SERVICE /konsole/MainWindow_$MYCMD_WINDOW will show you all methods available on the Window, eg, so you can pick&choose from those if you want different behaviour from show (& un-minimize) and raise.
EDIT: syntax adjusted to work in 'regular' bash
Soo... If we could figure out how to do the first one via DBus/from the command line, you could put both in a script and bind that to a (global or so) shortcut, and be set. (?)
What qdbus command line exactly are you using to post input to the shell within Konsole?
I'll have a look later when I'm at my desktop again (and hopefully will remember).
For the vendor (non-)consent thing - Consent-O-Matic provides an appropriate framework.
(Whether such a side would even care about the preference/consent is another matter entirely - I'd suggest a throwaway browser identity and cookie auto delete for a start, anyway.)
Creating rules has a bit of a learning curve the first three or seven times, but I find that more interesting to do than go through a hostile/dark pattern cookie dialog or such the third time.
Hm, maybe the appropriate functionality from CoM could be re-wrapped as a TamperMonkey module...
Web automation for the masses 😱
Great writeup, thank you so much for sharing!
Nothing more frustrating than googling an issue and (only) finding forum threads ending in "nvm it works now" 😬
What exactly does it do / which problem(s) does it solve? Its website reads kinda intentionally vague to me.
Regarding weather: I just love the no-frills at-a-glance presentation of the AF Weather Widget
12ft.io and/or archive.is/archive.today/... are worth trying in such cases (assuming you already have the latest version of the current ByPass addon, see the other comment).
Unless someone would stumble upon a combination of microwave magnetron that "just so happens" to fit a satellite dish LNC mount. I can neither confirm nor deny that such combinations might exist.
It certainly would seem a very good way to impart... "energy" into all and sundry besides the intended target, and as such horribly dangerous and irresponsible.
Regarding cookie pop-ups, there's a little known gem: https://consentomatic.au.dk/
Aus der "nur zufällig mitgekriegt" Blase:
bzw mit noch bisserl mehr drum rum:
Could also be the exact opposite (experienced this with consumer grade electronics based on microcontrollers often enough):
Because of the large capacitors, voltage from the power brick kinda "ramps up" when it is plugged into the wall. The device/its MCU/most specifically its clock circuit however prefers a hard edge of power being turned on, to reliably trigger its power on reset circuit/oscillator.
You can think of it similar to a pendulum/newton's cradle/metronome - they also prefer one decisive push to get going reliably.
Unplugging the brick for a longer time is still worth a try, but it could also be this.
The ruling has been updated to say that accepting cannot be more convenient/streamlined/less clicks than rejecting, though.
Getting that enforced is another matter altogether, however.
There's CookieAutoDelete (or anonymous tabs, containers, ...) for the other side of this issue.
As for the first points, yes, that may happen, but is it a problem for users who already are part of a 'better' experience here than on the for-profit platforms?
I, for one, find much better discourse here than anywhere on reddit, let alone Meta or Twitter.
Also exemplified by me engaging much more here than ever on the others. I do prefer quality over quantity - everyone is invited to join the table, but I don't see much benefit in luring people there who would ultimately only dilute or be disruptive - ie, not really into the thing that's happening here.
For the last point, well, legislators can certainly try. While telling people it's all for their benefit and upholding freedom and democracy and equal opportunity and whatnot. And even keep a straight face.
But they happily give it to Threads, no...?
Yes, I know, I'm being somewhat more provocative here than necessary.
More down to reality, thousands of accounts being registered within seconds, possibly all from the same IP, aren't ordinary user activity. And quite feasible to filter for.
Heck, you could even ask for the eMail and offer some "or, if you rather wouldn't, you could..." thing that basically serves as a CAPTCHA.
(Disclaimer: I haven't read into that referenced article by ninja at all, maybe it already says something related)
For one, it may be possible to filter accounts that were created but actually never used to log on, within a week or two of creation - those could go without much harm done IMO.
And/or, you could message such accounts and ask them for email verification, which would need to be completed before they can interact in any way (posting, commenting, voting). That latter one is quite probably currently not directly supported by the Lemmy software, but could be patched in when the need arises.
How would they ensure this latter thing?
In my current understanding, it's readily possible today (on Lemmy and related software), what could Meta do to keep this from continuing to work?
From my (admittedly, deliberately naive and provocative) perspective, what is the (possible) "added value" of Threads' ad-infested feed over the community experience straight on Lemmy?
