Ah sorry, I misunderstood completely, I didn’t read it right. For some reason I thought you were talking about the router / wifi service being SOWPL.

IANAL, but I feel that coffee shop case would not be different if the software were under AGPL… if you are providing a service to other people, even if “the other people” are the customers to your shop, it could be argued that under the terms of the AGPL (not to be confused with GPL) they should have the right to see the source of the service that they are making use of.

But if the SOWPL requirement really does apply to private code that isn’t providing service to others, the implication would be that even if you are the only user (no coffee shop customer), and even if you are the only one who knows about it, you would still need to make the source code public in some way… which I feel this is very impractical and probably unenforceable anyway.

Even if you did block it, the fact that you blocked it is also trackable… so it might actually single you out even more, and it’ll still allow them to fingerprint your browser (you can test your fingerprint here).

It might make more sense to randomize / spoof the data so that it becomes inconsistent and useless so that you aren’t identifiable.

alias lt='ls -t | less'

Good idea! I’ll steal that but I would rather be able to give a directory path as parameter (and show in colors, and don’t pause if less than 1 page of content, and support the scrolwheel), also piping ls forces it to be 1 single column so might as well show more details, personally I’m gonna use this instead:

lt() { ls -t --color=always -Fgoh "$@" | less -RF --mouse; }

Consider for a moment that browsers still support multiple protocols besides hypertext transfer.

When the protocol is not https, then it will show it. In fact, it will show if the page is http and not https.

The lock icon (the one showing certificate information when clicked) only shows when the page is https, so essentially that icon replaces the https://

I mean… it would be simpler if it didn’t run any commands.

I think the point is that the UI of the bar wasn’t really more complicated before. So it’s not like the bar itself has really gotten any simpler. Specially if they aren’t removing the previous ways to access those functions.

That said, I do like the idea.

The approach to taxing isn’t determined by this tool, but by the government. What this tool tries to prevent is hidden money exchanges, which affect both methods of taxing, not only flat taxes but also income-based taxes (since a hidden sale is giving the seller a hidden income and potentially placing them at a lower income tax class).

Define lack of design. You mean theming? because Linux has way more customizable theming options than the proprietary alternatives, to fit all kinds of subjective tastes.

You mean usability? it’s the one system that you can rice up to do absolutely whatever you want to do to fit your workflow, you can configure any key to automate literally anything a desktop can do.

The catch is that you actually do have to get your hands dirty if you want to mold the system to your liking… as opposed to being your own tastes the ones molding to adapt to whichever the designer of the OS decided should be the new tacky fashion or workflow.

it may as well be a system managed folder at that point.

In a way it is. But user-level system, as opposed to root-level system.

interoperability == API standardization == API homogeneity

standardization != monopolization

But, whichever command I put in autostart.sh will run as if I run in terminal with the & sign. E.g: dunst & to run in the background.

Well, only if it’s one single command, if you have multiple commands inside of the script, they will still run sequentially (the next command will only run after the previous one completely closes) unless you add & to them as well.

The difference is that dwm itself will not have to wait for the autostart.sh to complete before launching itself (thanks to it being run in the background with &)

However, autostart_blocking.sh (which isn’t run with a &) will stop dwm from fully launching until the script completes… I guess this is useful if you need certain things to be set up before dwm actually starts… but it would potentially add a delay on dwm startup.

banned from connecting to wifi networks based on thier mac address

MAC addresses are easy to spoof in a Linux PC though. So you should be able to workaround that limitation if it’s ever a problem.

In fact, in theory you can also spoof the IMEI, it’s just that the software in phones is generally not as open and it would require rooting and some tweaking that not everyone is comfortable doing.

Another thing is that this standard does not allow setting an absolute size… you can only use fractions, for example, 2/3 of normal size, which can still be relatively big if your normal size is big.

I also expect making things bigger for emphasis (or adding headings) would likely be more common than making them smaller (that’s what I hope at least). Outside of things like mathematical notation where superscript/subscript might be useful (see this comment for some examples).

The problem with the web is that some websites use absolute units that might not scale well (like px) to define the sizes.

Personaly I use KeepassXC autotype functionality for this kind of thing (since I’m already using it as a password manager anyway)… I have entries that are just notes and then have the autotype command be: {NOTES}{ENTER} so it types the content of the note and presses enter.

The nice thing is that I can leverage the autotype dialogs from Keepass so I just need to remember 1 shortcut and it will open a dialog showing different Note options based on the title of the window I’m in. It also works across platforms (which is great if at work you still need to use Windows). However, Wayland is still not supported well.

I haven’t tried to use date/time placeholders, but in theory, they are suported in the keepass documentation (no idea if keepassXC in particular supports them): https://keepass.info/help/base/placeholders.html (check out the {CMD:/CommandLine/Options/} placeholder that lets you run arbitrary commands and optionally have their output replace the placeholder, which is very powerful)

In the auto-type docs they also have placeholders that even allow you to add delays, switch active windows, and press all kind of key combinations. Again, I’ve not tested if all of that works in KeepassXC but if not you can always use the official keepass app.

It was just an example of what I’m doing for my particular situation where I don’t have root access and I want some personal scripts for myself, I’m not saying you should choose the same location. If everyone is already sourcing the same file, I expect there’s already a shared storage you are maintaining that everyone has access to.

About something breaking, I guess it’s up to you and your team if you prefer functions, but it also means not everyone will need to be annoyed when someone else’s code has a small syntax error. And also I expect the only errors you are able to get feedback about right now would be only structural syntax errors for the function declaration (I expect you don’t have unit tests or anything like that for your bash functions…) so technically a function could still be broken and you wouldn’t know until you use it.

Scripts also give the advantage of being able to use other languages beyond bash, if perl/python or others are available.

Anyway, you are free to have your reasons, I was just saying that root access is not necessarily needed.

You don’t need root level access though. What I usually do is stick a PATH="$PATH:$HOME/.local/bin and then place all the scripts in there.

It’s ironic that GTK actually used to stand for GIMP ToolKit.

They were the first ones to use Gtk ever… and it’s looking like they will be the last ones to migrate to the newer major versions :P

But in there the virus and Megaman was part of the same software system/universe. What I’m arguing is that it would have been possible to set up 2 separate systems/universes, one is the one where Megaman is plugged, and the other one is one that has read/write access to all inputs/outputs of the first, without the first being able to detect that in any way.

So… Megaman would be sent to the first and see no problem (or worse, see enemies that aren’t real to keep him distracted) while the other alternate OS would have no Megaman in it, but still it would be able to analyze all Megaman is doing in the first system/universe (sort of like in Matrix), and possibly even transmit/translate his actions in a modified way so that it serves a different purpose.

But it’s not something the plugged OS can do anything about, because the malware is not running on it. It’s an attack that uses hardware, you can’t use antivirus against that, you’d need a person to physically manipulate the circuitry in the keyboard/monitor or whatever peripheral that is being manipulated.

Wouldn’t it be kind of insecure to be plugging your private data into public places?

In theory, the publicly available terminals could very well have their own system under the hood, wired into the hardware, just so they can run some keylogging or recording of everything that goes through the peripherals, including the screen, without the plugged OS being able to know, right?

The bad guys in those shows/games could have hijacked the terminals so they can take remote control of the inputs when an OS is inserted and wreak havoc. Dr. Wily could have messed with some terminals so that when Megaman saves its progress on them parts of his brain are saved with different data, so when it’s restored you’ll get a different/evil Megaman.