rlpb

32 ms·

421.
by rlpb 3y ago
+Zim for desktop integration (Markor supports Zim's text markup format)
422.
by rlpb 3y ago
This changed a while ago. See "Pause or stop automatic updates" at https://snapcraft.io/docs/managing-updates
423.
by rlpb 3y ago
I'd like parental controls at sub-app granularity. For example, to monitor a child's chats, with full knowledge of the child. To see all social media activity and add to the blocklist remotely. That kind of thing.
424.
by rlpb 3y ago
People always have the option of calling things other than how their proponents want them known. This has been used to great effect by the media in the UK (eg. "bedroom tax"). Perhaps there's space for an organisation that &q
425.
by rlpb 3y ago
Indeed, and you can see for example something that is fixed by that version here: https://ubuntu.com/security/CVE-2022-48434
426.
by rlpb 3y ago
If it's "recreational carbon emission categories" you want to ban, whether as a proportion of global carbon emissions or recreational carbon emissions per person, then I think there are much larger categories that would be ba
427.
by rlpb 3y ago
How does moving bags from overhead lockers to the hold reduce the weight? Or are you claiming that doing so moves the center of mass in a way that makes some practical difference?
428.
by rlpb 3y ago
> TOFU is secure if you verify the host key fingerprint against information received via a sufficiently secure channel. Verifying the fingerprint out-of-band is the opposite of TOFU. TOFU is generally understood to mean not verifying i
429.
by rlpb 3y ago
> You have much more context about your environment- you know what you need to connect to, what needs to connect to you, and what ciphers, key length, and other configuration that you must support. Therefore if you take all that into acc
430.
by rlpb 3y ago
In my world, most production services need to last longer than twelve years, so need relative pricing stability and no complete pricing restructures over a longer period. Perhaps your world is different.
431.
by rlpb 3y ago
"Coders howl over Google's App Engine price hike (natch)" https://www.theregister.com/2011/09/02/google_app_engine_use... I don't know if Google App Engine falls under Google Cloud service
432.
by rlpb 3y ago
> because of a misunderstanding of the versioning system > ... > I did not come away with positive impressions of their packaging processes I am not coming away with positive impressions of your upstream versioning or release proce
433.
by rlpb 3y ago
Another kind of patch is when a common dependency library is being updated, and laggard upstreams need patching to make their current releases work against the newer library; it's either that or a Debian release with those packages mis
434.
by rlpb 3y ago
You seem to assume that Debian users are hapless and are ending up in these situations by accident. That's not true. Most users choose Debian's model because they want to use software maintained by people who care about their us
435.
by rlpb 3y ago
As if this isn't an issue with fast-moving "let's bundle everything" upstream code drops either? Distribution releases have the advantage that they have a large number of followers who share the same set of versions, and
436.
by rlpb 3y ago
What about the user? If your goal is to consume software for which you need long term reliability, accepting software that bundles an unmaintainable (to you) set of dependencies does not make sense. Unless you have no better option [edit: o
437.
by rlpb 3y ago
"Self-contained" and "No bundled libraries" are two very important concepts that a subset of our ecosystem decided was too much work. Then they re-discovered all the problems that result, and have now coined terms like &
438.
by rlpb 3y ago
Debian has a user-first philosophy as well as a focus on integration between packages. When required, that means patching upstreams that don't meet that expectation for whatever reason. The ability to do this is precisely the point of
439.
by rlpb 3y ago
> ...but my username email is private and NEVER used or known. This feels like an architectural flaw to me. If it's supposed to be private, then why is it available to send to on the public Internet, in a way that you are now theref
440.
by rlpb 3y ago
> They will find some other reason to remove these sellers. That's be much harder work, though, so regulation might well still have the intended effect. Either their reason will need to be through their seller terms and conditions,
441.
by rlpb 3y ago
No need of "blockchain" for that. Just do a hash drop to any publicly archived place, or use a timestamping service.
442.
by rlpb 3y ago
By being early, I hope that you have acquired expertise that you can now export.
443.
by rlpb 3y ago
Security: what's this? Person subject to security: it's a device I can use to compromise your security Of course they'll confiscate it then. This would probably apply to any device they choose to describe to security this way
444.
by rlpb 3y ago
> it wouldn't just disrupt planes, it would crash planes if this were not even planned as a contingency. It would not. Aircraft have other navigation systems they can use instead, such as inertial reference and ground-based VOR navi
445.
by rlpb 3y ago
I think you missed the point. The guidance you quote doesn't cover the case described.
446.
by rlpb 3y ago
> The exact same dynamic exists for on-prem services. With on-prem, you can choose to defer deploying that significant (and therefore higher risk) change when it's crunch time for your business. That can reduce regression impact con
447.
by rlpb 3y ago
One problem is that it's anti-competitive in the sense that a new video streaming service cannot compete because an ISP will charge extra to use them but not for (eg.) Netflix. > Bandwidth is finite and if you have a little more mon
448.
by rlpb 3y ago
> If you wish to carry on plugging in a telephone to your landline without any configuration then you will have to start using the telephone socket on your wifi router and only the router provided by your isp. I find the need to configur
449.
by rlpb 3y ago
My prediction of future bandwidth growth is that to get super high speed wi-fi you'll need line of sight to an access point that has fast enough (ie. wired) backhaul. Even today you can get considerable speedup by doing that. So I thin
450.
by rlpb 3y ago
> Shared objects do in fact allow doing the safe subset of this, which is to load 2 versions of D that are used by packages B and C without exchanging API objects. It's a fair point. But in practice this can only be done when the ve

More ›