-- Leo's gemini proxy
-- Connecting to gemini.tuxmachines.org:1965...
-- Connected
-- Sending request
-- Meta line: 20 text/gemini;lang=en-GB
Tux Machines
Posted by Roy Schestowitz on Dec 23, 2022
> Relative units used in container queries work differently than relative units in media queries.
> If you use em in a media query, the font-size of the
, , or any other element on the page doesn't matter. That's because relative length units in media queries are based on the initial value, which means that units are never based on results of declarations. em in a media query is relative to the font-size, defined by the user agent or the user’s preferences.
> With cascade layers comes a new CSS-wide property value, revert-layer.
> You can use the rever-layer keyword to roll back the cascade to a value defined in a previous layer.
> Okay, okay, I know, these keywords aren't new at all, except for revert maybe which is newish, but if I want to write about revert-layer, which is brand new, I need a basic understanding of all keywords. Also, I had the feeling that most of you, like me, don't know what all of these keywords do, and I was right. At least, if you want to trust this poll on Mastodon.
> Problem: My wife and I are going on a long plane journey and don't have seats next to each other. How can we communicate?
> Constraints: The plane WiFi is ruinously expensive. The in-seat messaging service isn't private. We both have Android phones.
> Preferences: Open Source. Secure. Easy to use.
> Solution: Use Bluetooth messaging app Briar.
> I recently wrote about some aspects of my dmenu setup, including using a custom $PATH that contains a bunch of little utility scripts. These little scripts are an important part of making my dmenu setup so useful and a crucial building block of my environment, but in turn a lot of them are enabled by something else. In practice, a lot of what I do with dmenu is to open a Firefox window on some sort of URL, and in turn this is relies on being able to create URLs that do useful things, like perform a web search.
> DNSViz presents a domain on a Web page and I can hover over individual elements to see details about them, as the example above demonstrates. (See the full output here.) Domains are typically visualized from the root down to the domain I wish to test. DNSViz keeps a history (which was unavailable for a long time) so I can “walk back” in time looking at previous analyses.
> If you've been doing the wifi thing for a while, you've probably followed the successive rounds of "security" that get layered on top. Back more than 20 years now, it was WEP, the so-called "wired equivalent privacy". That claimed to be 64 or 128 bits, but was closer to 40 or 104 due to the whole 24-bit "IV" thing, and a whole bunch of dumb problems with the crypto generally meant it was weaker than that in practice. Collect enough packets and burn some CPU power and the network is yours.
> Let me start with; there is no perfect security. Your goal is it to make it as difficult as possible to 'break in', so it is simply not worth it. There is a balance between security and usability, and you have to find a good middle ground.
> I try to keep it as short as possible, and focus on the 'what' and 'why', not the 'how'. There are many ways to achieve the goals, but this is a topic for itself, and depends on the circumstances.
-- Response ended
-- Page fetched on Sat Jun 1 06:32:47 2024