I use both and YouTube Short produces mostly just garbage for me. AI voice videos that will get your attention, but has little content. TikTok's algorithm on the other hand is much better and provides quality, half-long-form content.
The argument I remember goes something like this (and I could be remembering it wrong).
They claimed technical problems prevented them from fulfilling the amount of gas required by their contract for NS1 and NS2. Due to sanctions they essentially had to provide gas for free - or at least in exchange for money they were unable to spend or access.
The pipe blowing up potentially saved them from having to pay a penalty fee in the contract once the gas hadn’t been moving for X number of days.
Why would Russia be concerned about a contract? Reminds me of a story on something like Unsolved Mysteries....lady had her husband killed because she was a christian, and thus, didn't believe in getting a divorce, and wanted to be with another man (his best friend.) And his friend went through with it...
They left one pipe of NS2. It would have been a political victory for Putin with humiliation of the German government if they had switched to this instead of stopping gas imports via NS1&2 completely.
The Ukrainians are flying drones filled with explosives into Russian refineries and we still don't think it was just the Ukrainians taking out the Russian gas pipeline?
The pipeline had the additional complication that it was supplying heating fuel to Europe. Bragging about it to the Germans would have probably been a bad idea.
That's the thing though, at the time it wasn't supplying gas. Gazprom said it was having 'technical difficulties' (that the German equipment manufacturer denied) and had reduced the flows over time to zero to put pressure on the Europeans through high winter gas prices and low supplies.
Your broader point is correct though, admitting to blowing it up would be bad press to any party.
As for the cost, I agree. Just charge me more on the room itself. But in EU and many other countries, you are responsible for knowing who does what through your network.
As for the user experience, why not just give you a personal generated password when you check in? Then they have the info they need, and you just need to enter the password. Both iOS and Android support auto filling SSID and password through a QR-code and NFC, so that's the best solution I think.
> As for the user experience, why not just give you a personal generated password when you check in? Then they have the info they need, and you just need to enter the password.
In my experience, a lot of hotels already do this.
But not Colemak. macOS has supported both Colemak and Dvorak, and I find it infuriating that they not only haven't supported it on iOS yet, but even more infuriating that they only added Dvorak.
I can only be thankful that Colemak is supported on external keyboards on iPadOS, even though the virtual keyboard doesn't support it.
I used to use Colemak on Android before I switched to iOS. As nice as layout parity was in principle, it was noticeably unfit for swipe typing. Too many words just ping-ponged along the home row.
I used Dvorak on Android, before switching to iOS. Same problem, of course. It was nearly unusable with swipe (my now preferred input). It made me realize how badly a swipe optimized keyboard is needed.
Colemak wouldn't be as useful for thumb typing or swipe typing as QWERTY.
The hardware keyboard support is adequate for my needs (on iOS too, it's handy to fold open a Bluetooth keyboard to use with your phone) and I've never seen a need for Colemak in the software keyboards. I can't properly touch type on an iPad even if it supported Colemak because there's no "touch" there and I wouldn't want to accidentally ruin my touch typing skills with a "watch the keyboard" fake touch typing device. Easy enough to just have Bluetooth hardware keyboards handy. The iPad even has nice ones that attach by magnets and act as covers so they are always around.
For what it's worth, SwiftKey on Android supports Colemak and Dvorak, so I presume the iOS versions do as well. It's not the stock keyboard, but it's not bad either.
Why do you want Colemak on your phone? I switched to Colemak for my physical keyboard years ago, and didn't keep up my QWERTY skills, so I'm fairly crippled typing on a QWERTY keyboard; but I have trouble typing on my phone with my thumbs.
Presumably people like us are exactly why it's included on external keyboards for iPadOS.
I too use Colemak for physical keyboards and Qwerty for soft keyboards.
It is nice to have the consistency available. Though, I don't really have a need for it. Only case I can thing of is typing a few, key memorized passwords. I don't really remember the actual password, just the motions. Kind of a pain to motion it out and translate it to qwerty.
Yes, this has also been something I've missed from mostly all markup languages, but the renderer also has to make a distinction between paragraphs inside and outside of a section. To better illustrate:
@section {
@title: This is my section title
Text, paragraph, etc.
@section {
@title: Subsection Title
Text, text, text.
}
More text that belongs to the parent section. But how will the reader know that? Indentation? Blocks with background color maybe?
}
No that is how the system works today. I would like, and have always wanted a way to disambiguate without creating a new title. There should be some sort of visual indicator that we are going up to the parent level without creating a sibling to the parent.
title: ships
p: ships travel on water
p: they are like cars but on water
title: motors
p: ships have motors
p: spin around
p: very powerful
p: ships can be used for many things
title: fishing
p: fish are in water, so the incentives are super-aligned
I've been hacking now and then on a document preprocessor that uses a similar syntax, e.g. this code
@Section[name=quickstart]{@Title{Quickstart}
@P{ The official documentation is very sparse, but as a quickstart here is what you need to do: }
@List{
@Item{Create a fullscreen window to render into}
@Item{Initialize the library with @FuncRef{S3DTK_InitLib}.}
@Item{Create a renderer with @FuncRef{S3DTK_CreateRenderer}.}
@Item{Create an IDirectDraw instance - DirectDraw is mainly used to manage video memory.}
@Item{Setup exclusive and fullscreen cooperative level and set the video mode to 640x480x16bpp or whatever.}
@Item{Obtain the base of the framebuffer (see below) to use for calculating surface offsets.}
@Item{Create a primary surface with a secondary buffer attached to it to act as a swap chain.}
@Item{Create two @TypeRef{TS3DTK_SURFACE} variables to hold info about the surfaces. S3D actually needs very little info about a surface: its size, pixel/texel format and the offset in video memory from the framebuffer. This bit is the trickiest one.}
@Item{Optionally create a 16bit surface to hold a z buffer - again you need to do this via DirectDraw and @TypeRef{TS3DTK_SURFACE}.}
}
@P{ And that is about it. Beyond that it is mainly setting state and drawing triangles. In terms of memory management, S3D relies on DirectDraw to do the video memory allocation/etc so in general the process is allocating a DirectDraw surface and filling a @TypeRef{TS3DTK_SURFACE} variable with info about it. The S3D API itself does not actually know about DirectDraw, it is only used indirectly to obtain the memory offsets and to perform surface flipping. In theory it might be possible to allocate a big surface and chop it to smaller pieces with multiple @TypeRef{TS3DTK_SURFACE}s. }
produces the list at the top of [0]. The main difference in the syntax is that instead of "@title: blah" you type "@title{blah}" because "blah" is just the content for the "title" node and the parser doesn't treat any nodes in a special way, it just creates a tree and then passes it to a script for doing whatever it wants to do (to produce the linked HTML document it is passed to a script that generates HTML in a variety of formats - e.g. single file, multiple files, using HTML5 elements or sticking to "basic" HTML that works in a bunch of primitive viewers, etc).
The "Section" node above uses "P" but strictly speaking it isn't necessary as any text after the } will create text nodes for the parent node (in this case the "Section" node). I did it this way mainly for consistency, but a script could just use the node's own text (which is basically what nodes like "FuncRef", "TypeRef", etc are doing).
(i do not have any releases for the processor yet since i'm still -slowly- tweaking it as i -very slowly- write various documents using it)
Not really since i'm still tweaking it. The base processor is mostly done (though i also add some minor stuff here and there) but the scripts are incomplete. Of course one can use their own scripts instead, but i want to have a default set that works for most manual-style uses.
I have no expertice in this, but; Watch stand-up comedy and observe. They are masters at pacing and story arcing. Observe how they bring the energy up and down. They start off with a premise that needs resolution, so that under the whole bit, the audience has the resolution on their mind, and much of the interest in the bit lies in the interest in the resolution. The resolution cannot be uncovered unless a new premise is brought forward or the story is finished.
