Please tell me this is a joke. The fact tether trades readily on an exchange is a major factor for it being convertible, even if at a price you don’t like.
>>tether trades readily on an exchange is a major factor for it being convertible
... for now
We've seen lots of the crypto exchanges fail to make exchanges for hours to days when things get hot
Official stock exchanges have a standard practice of halting trading in stocks when unusual events happen. Sometimes this cools the market and things get back to normal, sometimes the thing has gone to zero when
If Tether crashes to $0.01, I'd be a bit surprised if it didn't stop being convertible for a significant time.
I don’t know where you got this advice from but this is precisely wrong from my reading of the rules.
An asset exchange between two non legal tender assets is treated exactly the same as any other disposal and acquisition and absolutely is a chargeable event.
it looks like in the future it might be a better way of implementing khttpd by handing over from a userspace control program the accept->read->sendfile->close sequence of async operations to the kernel
the rise of this submission to the front page and the swift sinking back under the waves, along with the vote war on comments here is interesting. this place isn't nearly so left-leaning as i'd assumed.
I like CDK because:
1. it's type-checked (using your choice of language/compiler)
2. modularity is done using in-app code, rather than extending serverless with plugins in javascript
3. i think cdk scales better to projects composed of multiple stacks
4. it's somewhat testable
I'm assuming your point is that words get shortened for convenience and that that's OK. That's a fair point. It's also true that language doesn't always evolve in ways that make sense, and I get that.
With that being said, there's a huge difference between shortening "weblog" into "blog" and shortening "blog post" into "blog":
First, when "weblog" was shortened to "blog," "blog" didn't already mean something (and certainly didn't mean anything in the relevant context). When "blog post" got shortened to "blog," "blog" already had a meaning - AND it already had a meaning _in the context of the internet_. One of these leads to confusion, one of them doesn't.
Second, when "weblog" was shortened to "blog," we didn't already have a shorthand way of saying "weblog." But we've been shortening "blog post" to "post" basically since the beginning. There was no reason to shorten it to "blog" also. "Post" was just fine.
I'd argue that a more fair comparison would be if, after using "blog" for a while, we decided to shorten "weblog" into "web" instead. It would have been silly, because "web" already meant something, and because we already had a shorthand version of "weblog" (i.e., "blog") - so why did we need another?
But I guess your sarcasm and the down votes answer my question anyway. The internet has accepted "blog" as meaning "blog post." I might as well get on board.
RAF allows moustaches too.
Apparently "not to extend below the edge of the mouth" which still leaves quite a lot of room for expression I would guess.
Rule still applies while on secondment [1].
My Grandfather was born before the days of safety razors and tells me that Navy personnel were able to petition to avoid shaving on account of delicate skin (something about the salt water and fresh air). I think anybody who could grow a beard would have done.
Interesting observation. The area of the upper lip is known as the "Danger triangle" of the face, in which due to way blood circulates in that area, including the upper lip, infections can spread back towards the brain:
I never thought that mustaches had a health / self preservation / natural selection origin, but it could very well have been the case. Shaving every day without modern tools and products could easily cause infections, which in that area could prove fatal.
