| Screwtape |
Posted on 19-08-19, 03:49 in (Mis)adventures on Debian ((old)stable|testing|aghmyballs)
|
|
Full mod
 Post: #321 of 443 Since: 10-30-18 Last post: 1101 days Last view: 172 days |
Posted by tomman Yeah, that bit me once. Once upon a time I installed Timitidy, probably to try out the MIDI soundtracks in ScummVM, and at some point the timidity package started depending on timidity-daemon, which runs at startup and grabs exclusive access to the sound-card. It was super-annoying until I figured it out, but oh well. Oh, don't forget to add -N to your ls alias definition on your .bashrc, otherwise you will get those annoying quotes wrapping any filename with spaces (because that's a Windows-ism that must die, nevermind that the Real World goes beyond Unicrud and its collection of space characters). Spaces, or other weird shell-meta-characters. I find it quite convenient that I don't have to figure out how to quote whatever weird characters appear in a filename, I can just copy/paste whatever ls prints. The ending of the words is ALMSIVI. |
| Screwtape |
Posted on 19-08-19, 07:40 in Board feature requests/suggestions
|
|
Full mod
Post: #322 of 443 Since: 10-30-18 Last post: 1101 days Last view: 172 days |
Yeah, so this site is serving up its own cert (signed by Let's Encrypt), but the browser for whatever reason doesn't know about Let's Encrypt. I'm very surprised that any up-to-date browser in 2019 doesn't automatically trust the Let's Encrypt cert, and even more surprised at the idea of browsers downloading plausible-looking certs, but apparently that's a thing that can happen. Actually, now that I think about it, maybe between the time that it broke and the time that it worked, you happened to visit another Let's Encrypt-secured website that *did* provide the intermediate cert, and the browser cached that somewhere so it was available the next time you visited this site. And then when you shut down the browser, it clears all its caches and the problem resurfaces. I guess we can test that hypothesis: - Restart your browser - Visit https://helmet.kafuka.org/ - Confirm that the site is not trusted - Restart your browser - Visit https://lobste.rs/ (a Let's Encrypt-protected site that does serve the intermediate) - Confirm that the site is trusted - Restart your browser - Visit https://helmet.kafuka.org/ - Confirm that the site is still not trusted - Visit https://lobste.rs/ - Confirm that the site is still trusted - Visit https://helmet.kafuka.org/ again - See if the browser trusts it now The ending of the words is ALMSIVI. |
| Screwtape |
Posted on 19-08-19, 08:39 in Typesetter.css, make semantic HTML readable
|
|
Full mod
Post: #323 of 443 Since: 10-30-18 Last post: 1101 days Last view: 172 days |
Posted by funkyass Harsh. I was trying to go for contrast without being boring and monochromatic, so I picked a nice, pale yellow. If there's some reputably-recommended readable colour-scheme I'm interested, but honestly, there's a reason I put all the colouring in a separate CSS file. For my own site, I just went with Solarized because that's my go-to answer for anything colour-scheme related. Posted by sureanem It's nice to see people putting effort into measuring such things, but if I read the first bit of that page correctly, "success" means "the user stayed on the page for at least 40 seconds. I'm sure they're accurately measuring *something*, but I'm not sure it's a metric I personally care about. Isn't the point of indenting paragraphs that you don't need the space between them? Yeah, somebody else mentioned that. I'll definitely change it. If you want 60 chars of width, you can specify width as 60ch. According to MDN, 1ch is the width of the 0 glyph, so measuring line-length in ch is nearly as arbitrary as measuring it in em. The book I'm cribbing from says "On a conventional book page, the measure, or length of line, is usually around 30 times the size of the type", so that's why I use the em unit. It also makes it impossible to do (compact) footnotes with small text, because the line width is forced to be the same everywhere. I assume by "width" you mean "height". Keeping a consistent line-height is very deliberate, and is the main thing I wanted to achieve when I set out - text feels more consistent with a vertical rhythm, and less like a bunch of separate blocks pasted together. The book I'm working from is very consistent about vertical rhythm in the main body, but it does use a smaller line-height for footnotes (at the bottom of the page) and side-notes (in the left or right margins). Unfortunately, HTML doesn't really have footnotes as such, and although I use the HTML5 <aside> for side-notes, if the browser is narrow enough they get folded back into the main body. I'll think about using a smaller line-height for side-notes that actually appear on the side, but I'll tackle paragraph spacing first. Posted by sureanem Unlike the default background and foreground colors, it's actually quite practical for a user to change their default font-size without breaking web-pages, so I respect that instead of trying to choose something myself. The ending of the words is ALMSIVI. |
| Screwtape |
Posted on 19-08-20, 12:07 in Typesetter.css, make semantic HTML readable
|
|
Full mod
Post: #324 of 443 Since: 10-30-18 Last post: 1101 days Last view: 172 days |
Posted by sureanem That looks pretty nice, although I'd feel a bit awkward straight-up stealing somebody's colour-scheme unless it was deliberately made available, like Solarized.
I got rid of the blank lines between paragraphs; the demonstration site is updated. I also made a bunch of other changes following the example and instruction of the typography book I'm following: - The book has all headings the same size as everything else, with a single line-break before and after, but makes them fancier in various ways (all-upper-case, small-caps, italic) - The book doesn't use underlines or outlines for anything other than table headers and footers - The book doesn't use shaded backgrounds or bold text Unfortunately, I don't think it's practical or useful for me to follow the book exactly. - Although the book's headings don't stand out very much, it's still easy to navigate the book because it has section titles printed in the left and right margins of every page so you can just flick through. You can't (easily) do that in HTML, and you can't flick through it the same way. The closest thing is quickly scrolling through, and bold headings definitely help there. - The book is like 90% prose, so the line spaces around headings and the like really stand out. In comparison, the kind of documents I write tend to have a lot of bullet-point lists and code-blocks which add a lot of whitespace of their own, and heading whitespace isn't as notable. - The book has the privilege of a rigid and well-defined document structure, but although there's an official algorithm for building an outline of an HTML document, it's not available to CSS, so I just have to do my best. Ideally I'd use <h1> for the document title, <h2> for sections and <h3> for sub-sections, but Markdown only makes <h1> and <h2> pleasant to use, so either I use h2 for sections and lose subsections, or have the document title look the same as a section heading. So I'm not *entirely* happy with the way the stylesheet looks now, but I can't think of any changes that are likely to improve *every* semantic-markup HTML document - it seems like every improvement for one document makes a different document worse. The ending of the words is ALMSIVI. |
| Screwtape |
Posted on 19-08-21, 01:07 in (Mis)adventures on Debian ((old)stable|testing|aghmyballs)
|
|
Full mod
Post: #325 of 443 Since: 10-30-18 Last post: 1101 days Last view: 172 days |
I wish VirtualBox had the same fate as OpenOffice.org, i.e. hard-forked by community members who actually cared and did a better job than Oracle. Unfortunately, while OpenOffice was strategically important to, say, RedHat, RedHat doesn't need VirtualBox because they've got libvirt and qemu. Which is pretty slick, but I don't know what the "build a VM in app X and run it in app Y" compatibility story is like (for X and Y in: VirtualBox, VMware, VirtualPC, Hyper-V, bhyve, QEMU, Parallels, etc.) The ending of the words is ALMSIVI. |
| Screwtape |
Posted on 19-08-22, 06:53 in (Mis)adventures on Debian ((old)stable|testing|aghmyballs)
|
|
Full mod
Post: #326 of 443 Since: 10-30-18 Last post: 1101 days Last view: 172 days |
Posted by tomman As I understand it, it's great for Linux VMs, because the Linux kernel generally includes all the drivers for everything everywhere, but I can just run Linux software directly, I don't need a VM for it. I need a VM to run Windows software, but Windows installations tend to have very specific hardware drivers installed in the registry, so moving an installation from one VM platform to another (or one motherboard to another) gets you blue-screens. libvirt's virt-manager is a shiny easy-to-use front-end like VBox has, but.... it's designed by RedHat for RedHat's customers. So, for example, you don't keep a bunch of VM images in your home directory, you connect to a daemon that manages all the VMs on a system. Bad luck if you've got a small root partition and a big home partition! Video always runs through VNC or SPICE, for ease of managing a fleet of VMs on servers from your workstation, but bad luck if you wanted 3D acceleration. When creating a VM, it asks for a bootable CD image to install from, which is exactly what you want when dealing with modern server OSs, but sucks if you want to install Win95 or something a bit niche. GNOME's "Boxes" is an even shinier, even simpler libvirt front-end, but... well, GNOME 3. QEMU is vastly more powerful and flexible, but of course much trickier to use. It's actually pretty easy for the real simple stuff; you can boot up a floppy image with "qemu-system-i386 -fda disk1.img", but of course more complex things like ejecting one floppy and inserting another are... less easy. The ending of the words is ALMSIVI. |
| Screwtape |
Posted on 19-08-22, 08:33 in Typesetter.css, make semantic HTML readable
|
|
Full mod
Post: #327 of 443 Since: 10-30-18 Last post: 1101 days Last view: 172 days |
Posted by sureanem This surprises me. The only similar publications I can think of are Bloomberg and the Australian Financial Review, and neither of them are pink. In fact, the article you link says "The paper, first published in 1888, tinted its pages in 1893 to distinguish itself from its rival", so I'm guessing it's not actually a standard for such newspapers after all. Ideally I'd use <h1> for the document title, <h2> for sections and <h3> for sub-sections, but Markdown only makes <h1> and <h2> pleasant to use So, Markdown supports two different heading syntaxes: ATX headings with the leading hashes (inherited from ATX), and Setex headings (inherited from Setext), which look like this: As a purely personal opinion, I love Setext headings and hate ATX headings. Setext headings *look* like headings, even in plain text, while ATX headings sometimes get confused with hashtags. A level-1 Setext header uses more "ink", so it looks more important than a level-2 Setext header, while a level-1 ATX header looks *less* important than a level-2 ATX header. This kind of heading numbering stuff is a common problem for HTML documents, so I kind of assumed Markdown processing tools would have a "renumber heading levels" option so you could render Markdown to HTML and have the heading levels properly nested. Unfortunately, neither Python-Markdown or even Pandoc seem to have such a feature. A minor gripe is the aggressive hyphenation. I don't think code should be hyphenated, for instance. "src/typeset- \n ter*.less" looks completely wrong, to me. Letting inline code stretch rightward forever is ugly, force-wrapping it with a hyphen is (potentially) misleading, and force-wrapping it without a hyphen is also (potentially) misleading). I guess we probably shouldn't insert glyphs into what is supposed to be a verbatim string, though. Also, I think the code should have a bit more spacing. The exclamation mark after "typesetter.css" is a bit too snug, at least to me. That's entirely up to the fonts your browser has chosen, I'm afraid. It probably defaults to Times New Roman and/or Ariel; I recommend reconfiguring your browser to something nicer. On my machine (1000x600), the navigation on the demo page gets cut off, about half of the "N" in "Navigation" is hidden and I get an ugly horizontal scroll bar (which only goes to the right). I'm using a CSS media-query to move the <nav> and <aside> elements to the margins, when there's enough room for them. Unfortunately for me, browsers define the "viewport width" to include the width of the vertical scrollbar, even though that space isn't available for my content. I'd changed the media-query to add a bit of safety margin, so the wide layout should only be used when you really, truly have enough room for it... unless your browser's default text size is smaller than your operating system's scrollbar size. The ending of the words is ALMSIVI. |
| Screwtape |
Posted on 19-08-24, 12:44 in Blackouts
|
|
Full mod
Post: #328 of 443 Since: 10-30-18 Last post: 1101 days Last view: 172 days |
I'm gonna guess... Singapore. The ending of the words is ALMSIVI. |
| Screwtape |
Posted on 19-08-25, 03:24 in (Mis)adventures on Debian ((old)stable|testing|aghmyballs)
|
|
Full mod
Post: #329 of 443 Since: 10-30-18 Last post: 1101 days Last view: 172 days |
> ls -U shows that the MATE provider was created first... Is that a straight "ls -U", or something like "ls -U *Notifications*"? Because if it's the latter, the list of items is provided by the shell, rather than by ls, and the shell might do its own sorting or something. > WTF Loonix?! I think renaming does put the new name at the end of the "ls -U1" list, so that would explain why renaming the KDE service put it last. However, note that ext4 filesystems support "directory indexing", which stores a directory's filenames in a B-Tree index, so they'll always be iterated in sorted order regardless of creation order. The ending of the words is ALMSIVI. |
| Screwtape |
Posted on 19-08-25, 14:22 in Blackouts
|
|
Full mod
Post: #330 of 443 Since: 10-30-18 Last post: 1101 days Last view: 172 days |
Posted by CaptainJistuce But if I'd been anywhere close to right, I would have looked like a goddamned genius. The ending of the words is ALMSIVI. |
| Screwtape |
Posted on 19-08-27, 02:20 in I have yet to have never seen it all.
|
|
Full mod
Post: #331 of 443 Since: 10-30-18 Last post: 1101 days Last view: 172 days |
Posted by Kawa How did you figure out exactly which URL caused the entire site to be flagged? The ending of the words is ALMSIVI. |
| Screwtape |
Posted on 19-09-02, 14:06 in I have yet to have never seen it all.
|
|
Full mod
Post: #332 of 443 Since: 10-30-18 Last post: 1101 days Last view: 172 days |
zFRAG, the Zen hard-disk defragmenting simulation. The ending of the words is ALMSIVI. |
| Screwtape |
Posted on 19-09-04, 04:25 in Sales and giveaways
|
|
Full mod
Post: #333 of 443 Since: 10-30-18 Last post: 1101 days Last view: 172 days |
The Humble RPG Bundle is another third-party Steam sale, but some of the games in it are also available DRM-free. What's kind of interesting to me is that Tyranny and Pillars of Eternity are *not* available DRM-free from Humble, even though they're available DRM-free through, say, GOG. The ending of the words is ALMSIVI. |
| Screwtape |
Posted on 19-09-04, 04:30 in bsnes v108 released
|
|
Full mod
Post: #334 of 443 Since: 10-30-18 Last post: 1101 days Last view: 172 days |
For anyone who doesn't watch byuu's Twitter or /r/emulation, byuu's made some notable changes in bsnes nightlies: - bsnes emulation core ported to libretro (although I don't know if/when it will be available in RetroArch's built-in core downloader) - options to emulate the inaccuracies of older emulators required for compatibility with old romhacks and fan-translations that are no longer being updated by their authors - making it easier to use patches in the error-prone IPS format - a system for patching bugs in commercially-released games since some games did goofy things even on the original hardware The latest nightly is available for Windows, for Linux, and other platforms if you want to try it out for yourself. The ending of the words is ALMSIVI. |
| Screwtape |
Posted on 19-09-06, 04:17 in bsnes v108 released
|
|
Full mod
Post: #335 of 443 Since: 10-30-18 Last post: 1101 days Last view: 172 days |
Yes, although right now it's a database with exactly one entry. And I don't think it patches the game, so much as it patches RAM at power-on to match what the game expects. But, y'know, we'll see how the feature evolves. The ending of the words is ALMSIVI. |
| Screwtape |
Posted on 19-09-06, 06:24 in bsnes v109 released
|
|
Full mod
Post: #336 of 443 Since: 10-30-18 Last post: 1101 days Last view: 172 days |
Official changelog Official downloads The ending of the words is ALMSIVI. |
| Screwtape |
Posted on 19-09-08, 08:12 in bsnes v109 released
|
|
Full mod
Post: #337 of 443 Since: 10-30-18 Last post: 1101 days Last view: 172 days |
When the git repo moved from GitLab to GitHub, I looked at a few different CI systems, and I think Cirrus CI was the only service that supported both MacOS and Windows (the fact that it also supported FreeBSD was a nice bonus). Unfortunately, their list of available OS versions is just Mojave and High Sierra, and High Sierra is marked "not maintained". If there's some special environment variable or pre-processor #define you can use to say "yes, I'm building with the latest SDK but I want a binary that works on Mavericks", we might be able to sort something out (unless bsnes already uses Mojave-only features somehow). Right now, the macOS build scripts for bsnes and higan are basically just copy/pasted from the Linux build script, and tweaked until the build stopped failing. I haven't personally built anything on macOS since they stopped supporting PowerPC and I reformatted my G5 with Debian. The ending of the words is ALMSIVI. |
| Screwtape |
Posted on 19-09-09, 02:52 in Mozilla, *sigh*
|
|
Full mod
Post: #338 of 443 Since: 10-30-18 Last post: 1101 days Last view: 172 days |
Posted by tomman From the article you linked: At a high level, our plan is to [...] Fall back to operating system defaults for DNS when split horizon configuration or other DNS issues cause lookup failures. So Firefox will initially query both the local DNS and DNS-over-HTTPS providers, and only stick with DNS-over-HTTPS if it's generally giving the same results. Presumably, DNS-based adblocking will trigger pretty often on the modern Internet, automatically preventing DNS-over-HTTPS from being used. Of course, if you *really* want to disable DNS-over-HTTPS, if the domain-name "use-application-dns.net" returns NXDOMAIN instead of its real address, Firefox will disable DNS-over-HTTPS in order to respect local DNS filtering. The ending of the words is ALMSIVI. |
| Screwtape |
Posted on 19-09-10, 09:24 in Mozilla, *sigh*
|
|
Full mod
Post: #339 of 443 Since: 10-30-18 Last post: 1101 days Last view: 172 days |
Nightly 71 already has a slightly different UI from that. So far as I can tell, Firefox generally won't let you grant a site special permissions unless the site has tried to do something. If a site doesn't set any weird cookies that Firefox blocks, Firefox won't let you grant weird-cookie permissions to that site. In particular, if you're using an ad-blocker, Firefox probably won't ever see any weird stuff, so it will never let you grant permissions. The ending of the words is ALMSIVI. |
| Screwtape |
Posted on 19-09-13, 06:51 in Mozilla, *sigh*
|
|
Full mod
Post: #340 of 443 Since: 10-30-18 Last post: 1101 days Last view: 172 days |
Traditionally, retrieving a web-page involves trusting a lot of people: - the browser vendor - the os vendor - other apps installed on the same PC - the local network admin - all the upstream ISPs between you and the website - all the governments with jurisdiction over all the above parties That's a lot of trusted parties, and everybody agrees the world would be a lot safer if we didn't have to trust as many of them. But eliminating one of them means trusting the others even more, and *all* of those parties have been untrustworthy at different times in different places. So when one person says "we should encrypt everything to protect ourselves from the local network admin" (the Firesheep attack/malicious wifi access points), another person says "But I'm my local network admin, and I want things to trust me so I don't have to trust upstream ISPs". And so on and so forth for every possible pair of parties in the above list. And none of those people are wrong, but also none of them are right. So far as I can see, there's a few ways this could go: 1. status quo (chaos) 2. "the needs of the many outweigh the needs of the few" 3. educate everybody involved to the point where they can make an informed choice about what approach suits their personal threat model Given how much power browsers wield in the modern Internet, and how over-eager they are to wield that power responsibly, my bet is on #2 in the long-term, even despite the heavy inertia of our technology stack, and despite how much I'd prefer #3. The ending of the words is ALMSIVI. |
