I was expecting there to be Doxygen comments in there, but there wasn’t. So, no, this header is not documentation. I don’t want to read all the code to understand how to use a library; I want examples.
If an average person were laid off today and couldn't find a job for 1-2 months, would they go bankrupt? I think most people would be able to survive on their savings for a month or two. Companies should also be held to the same standard. They should have enough savings to survive this sort of disruption, just like a person would.
So yeah, if your company can't survive a month without revenue, it is a crappier than average business.
That is a gross oversimplification. They are a huge multinational, even if they had saved their entire net income of over a billion euros it would not have been enough.
As a Keepass(keepassxc on Ubuntu) user I recently switched to Strongbox from the now abandoned MiniKeePass, which I have been very happy with. It supports using FaceID with a Pin, which is great for quick access on my phone. Syncing with wireguard/resilio sync.
+1 for bitwarden, it's open-source (both client and server), and does the job well (only issue is the UI in the firefox extension can be a little frustrating).
2-) Sftp = not cloud, dedicated non-public server which you can also setup in your home environment such as a nas drive which only and only you have access to.
3-) I am convinced it is the safest, because no 3rd party is involved in my perfectly synced password system.
I have a setup with syncthing to transfer it between all my devices without going to devices I do not control. Previously I used Dropbox, which while putting your encrypted vault on a third party service, is easily accessible to non-techies
I have wireguard setup for my home network and phone. Then I use Resilio Sync to perform the synchronization between my phone and my home network once wireguard is connected. Allows me to synchronize from anywhere securely.
I don't like wfh because I don't like being all alone at home all day. But my preference for office hinges upon the presence of other people in office too! That's why I encourage everyone to come to office and work.
Perhaps find a good video chat solution, it's not safe to come to work right now and hopefully you'll find having chat gives you the sense of being with others that you need.
Social interaction in one's free time is a matter of preference - you can stay home alone, or ring up a friend and go for a coffee.
Maybe eventually people can find a group of friends/acquaintances with which they can also hang out and have a coffee, while each tends to their own work?
At least if the person has any authority/influence, "encourage" in a work context means something different than my encouraging you to try out a new TV show.
No, it's not. That's an order. You're redefining the word to mean what you want. When my boss encouraged me to work from office, they said there will be pizza - where is the order in that?
> the commission should make rulings that require that providers of Internet service (ISPs) shall not intentionally or unintentionally interfere with any legitimate use of the network bandwidth between the end user and the service provider communicating with that end user.
You forgot the most important part of the comment that the FCC really wants to hear from the public : why?
This is certainly a valid observation, I don't necessarily agree that "why" would be ranked as most important. And why I don't agree with that could use some elaboration.
I see governance as having two primary missions, preventing harms and preserving rights. That said, rulemaking is a policy action, it creates rules much like a programmer does, that are provided input and act based on that input.
An example of the latter that many readers here are familiar with would be sanitizing user input prior to displaying it on a web page. The programmer creates a rule like "always change the '<' and '>' characters to < and >." That is a rule and the 'why' is implicit. Without making that change, a user might type in their input an arbitrary piece of javascript which when displayed becomes part of the page. So the 'rule' prevents the 'harm' while preserving the 'right' for users to put < and > in their input, like we do here in comments all the time.
The other aspect of policies (or rules) is that making them consistent allows users or clients to not be surprised when something they think should be allowed, isn't. This is sometimes shortened to the principle of least surprise.
In this case the FCC is rule making in what is, relative to there original mission around RF spectrum, a new communication medium, the Internet.
To someone at the FCC, within the context of their past policy/rule making and their understanding of the Internet as a communication mechanism, they have the tools to understand that ruling against interference to other legitimate users of the spectrum is a core principle of their rule making in the RF world. This is particularly true in the portions of the spectrum that are unlicensed, like the 2.4GHz ISM bands.
My comment was written for a commissioner to read and to tie the 'old' with the 'new' and to perhaps dent a little bit the argument that ISPs use of "my wires, my house." Such a commissioner will already have heard hundreds, if not thousands, or arguments which stress the harm that is caused when one entity using spectrum and interfere with another using the same spectrum.
Using our WiFi examples it would be trivial for Cisco access points to recognize Ubiquity access points nearby and jam their channels. That would give Cisco users a "good" experience, and Ubiquity users a "bad" experience. And no doubt there have been examples of access points that had this sort of behavior, intentionally or not, and have been brought before the commission and adjudicated as being interferers and causing harm.
My hope is that one or more commissioners will have that context and read my comment and think, "Hmm, he has a point, it is just like spectrum and we treat people who interfere there as the 'bad guys', why should it be ok here?" And with that thought will come many, many, "Why equal access is the correct policy choice" examples from their work in the management of RF spectrum.
Even if hydrogen is the future, Toyota must realize that the present is battery electric. They can continue research on future tech while they rise to the market demands in the present.
It isn't? There's a difference between dropping 32bit libraries from your OS (after a lot of time in which Apple clearly said "we will drop support!") and banning for using unauthorized APIs inside the MAS.
