Autoscaling isn’t only used the grow the number of servers under load, but also to guarantee availability of a fixed number. If the max is set to 1, the bastion host is protected against hardware failure, zone outages, or just you screwing up. Accidentally killed your bastion host? No problem, within a few minutes autoscaling will have provisioned a new one and you’re good to go again.
Ah yes the classic dangerous command made safe by a modifier key. Put the gun to your head and pull the trigger, just make sure you’re holding down the shift key and it’s all good!
This is how my secure crt is set up when im accessing switches. If i use ctrl+c it cancels what im doing and drops back to priv mode and its so frustrating.
Almost completely pure way of storing ideas. With this I mean that you don’t store unnecessary data such as “background should be white” or “left page margin is 1.3cm”. It’s just text. What’s important is what it says + minimal markup.
Presentation is left to the reader’s client. Do you want dark mode? Get a markdown editor/reader that supports it. Do you want serif font? Again, that’s client’s choice and not part of the document.
I wish browsers would support markdown out of the box, so you could open example.com/some-post.md
Presentation is left to the reader’s client. Do you want dark mode? Get a markdown editor/reader that supports it. Do you want serif font? Again, that’s client’s choice and not part of the document.
I remember when that is how the web worked. All that markup was to define the structure of the document and the client rendered it as set by the user.
Some clients were better than others. My favourite was the default browser in OS/2 Warp, which allowed me to easily set the display characteristics of every tag. The end result was that every site looked (approximately) the same, which made browsing so much nicer, in my opinion.
Then someone decided that website creation should be part of the desktop publishing class (at least at the school I taught at). The world (wide web) has never recovered.
There are four properties in an accessibility tree object:
name
How can we refer to this thing? For instance, a link with the text “Read more” will have “Read more” as its name (find more on how names are computed in the Accessible Name and Description Computation spec).
description
How do we describe this thing, if we want to provide more description beyond the name? The description of a table could explain what kind of information the table contains.
role
What kind of thing is it? For example, is it a button, a nav bar, or a list of items?
state
Does it have a state? Examples include checked or unchecked checkbox states and collapsed or expanded states for the <summary> element.
We’re getting closer to winter. I’ve got most of those preparations done. “Just” have to finish building the heater for my shop. My programming based project list is coming together: learn me some Rust, contribute some documentation to a project I’m following, look deeper into the potential of the Accessibility tree. That should keep me busy for a while!
It’s a simple and elegant way of covering 95% of document structuring needs, while being as close to readable plaintext as possible.
The vast majority of documents currently written in MS-word could just be markdown. The vast majority of web content could just be markdown. This would save the modern world petabytes of XML bloat.
If you need something fancier, either use a vector format or do fancy client-side styling.
@Zeragamba@QuazarOmega just because something is paranoia doesn't mean it isn't true. Whenever I turn on the DuckDuckGo "VPN" to stop tracking by third party apps, I'm amazed at how many request are happening from apps I hardly use and many I don't expect (though I should know that something can still be open source Free Software and that the open code contains surveillance capitalsm tracking in order to fund the project)
The thing I dislike most about Atlassian products is that each of them has a completely different formatting engine and markup syntax. You’d think they’d be consistent but noooo
Atlassian doesn’t even have consistency within single products! I’m using Jira Cloud at work, and while most fields support markdown (e.g. three backticks to start a code block) there are a few that only support Jira’s own notation (e.g. {code} to start a code block). It’s always infuriating when I type some markdown in one of the fields that doesn’t support it for some inexplicable reason.
I only do webdev occasionally and yeah, I’ve noticed this tendency that I want to put everything in a CSS grid. At this point, I’m worried I end up with a layout that’s about as responsive as the early-2000s table layouts. 🙃
Yeah, I’ve done responsive grids before. Problem is, I’m currently working on a single-page web music player and it’s so easy to just nail all the UI elements down. Like I might want to have the play button always appear to the left of the playback bar. But that obviously can’t reflow naturally on smaller screens. Although reflowing that example won’t look good either.
I guess, I’m still figuring out, if I ever actually want things to reflow. I might just need to define static rules, so that on a small screen, the play button should appear in a different grid cell, next to the previous/next buttons, for example…
You forgot “don’t say ‘thank you for pointing out that we were sending social security numbers to everyone who visits our website that anybody could stumble across,’ but rather ‘you will be prosecuted to the fullest extent of the law, hacker!’” Courtesy of the Missouri Department of Education.
I’ve been having trouble getting syntax highlighting to work on my ‘```’ fenced code blocks. I give it the right/supported language identifier, but nothing changes.
I’m using neovim with a bunch of lsp plugins and treesitter. Anyone have dotfiles with markdown code syntax highlighting working?
programmer_humor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.