The mobile number requirement was always a feature of signal.
The friction is slight for users, but higher for scammers that might go through thousands of accounts. Telegram is too easy to sign up, so it's mostly scams.
297 karma · joined February 3, 2021
The friction is slight for users, but higher for scammers that might go through thousands of accounts. Telegram is too easy to sign up, so it's mostly scams.
Perhaps even more so, since 1F is a meaningless level of precision for most activities.
Usually when a player is walking up to a hidden enemy the crowd changes in a noticeable way, even on the stream. It's not an individual shout so much as the overall noise.
After enabling iterative calculation and manual calculation, every press of refresh runs a loop. Fun stuff.
Presumably they don't harrass users to accept the agreement once already accepted.
Proponents think it will collapse the dollar and bankrupt all governments.
Opponents think it's negative-sum and the sooner cryptocurrency dies the better for industries that actually create value.
Either way it's a (mild) attack on effective government and civilization more generally. The less subsidies for traders the better, from the perspective of a currently-influential government.
The hope is that some sucker will buy them for $10, thinking that it's a bargain.
e.g. https://dbatools.io/commands/ https://github.com/microsoft/ReportingServicesTools https://learn.microsoft.com/en-us/rest/api/power-bi/
Also all the normal Active Directory and file system tools, but those are too broad to go into.
> Simon Orrell: My first exposure to “The Plumber Problem” was sitting in a theatre with my dad in 1973 watching “Emperor of the North” and my dad leans over to whisper, “They didn’t make culvert pipe like that back in the ’30s. It was plate, not corrugated.”
If the session language is non-US, the ISO formatted string '1991-02-03' becomes 2rd March rather than 3rd Feb. yyyyMMdd works as expected.
You might be mixing up cmd with windows terminal though. Cmd is truly crap which is why it was replaced with powershell 20 years ago.
Everywhere there's dark patterns, performance overhead, mandatory updates degrading user experience, unnecessary JS and walled gardens breaking accessibility/compatibility, online-only etc.
Then there's all well-known bugs like floating point addition and locale-dependent function names and 1904 dates.
Conditional formatting accidentally pasting is all over the place.
There's so little liquidity post-merge that it's only worth mining as a way to launder stolen electricity.
The bitcoin people still waste raw materials, and prices are relatively sticky with so few suppliers and a backlog of demand, but we've already seen prices drop heavily since then.
Remade in 3d, then remade again in 2d to appeal to nostalgia for that style.
The production quality is rough in some sections (I found the female echo-voice particularly grating near the start), so if you're looking for a specific highlight rather than watching the whole thing 36:25-42:37 has a nice example of the "oracle problem" that underlies many of web3's issues.
It's for parsing rather than search though, you'd still need regex if e.g. searching unstructured logs for IPs.
e.g. (powershell syntax for easy reproduction) returns parsed, or throw if invalid. [uri]"\\ServerName1\Folder\UserName" [version]'1.2.3.4' [ipaddress]'1.1.1.1'
A browser doesn't need to be an operating system.
Running commands over WinRM or SSH can return objects of any type from remote machines. In the background I believe it's converting them to serialized CLIXML over the wire.
e.g. $RemotePSVersion = Invoke-Command -ComputerName 'SomeOtherComputer' -ScriptBlock {$PSVersionTable}
Rather than the variable $RemotePSVersion being a string it's an object with the type "System.Management.Automation.PSVersionHashTable", just like if you ran $PSVersionTable locally.
For anything that returns text (e.g. external tools like curl/robocopy) you'll usually convert to an object in your script before further processing. That way it can be passed into whatever next steps in a generic way.
e.g. curl https://catfact.ninja/fact | ConvertFrom-Json | Export-Csv '.\HighlyImportantInfo.csv'
curl https://catfact.ninja/fact | ConvertFrom-Json | Out-Gridview
That's less important when working interactively, but one major difference between Powershell/Bash is the relative focus on scripting vs interactive terminal use.
It's for wrappers around existing CLI tools.
Still feels experimental, but it's a nice idea to get objects from e.g. robocopy without dropping into regex and parsing it yourself.
"Crescendo" has been marketed as a solution and looks cool, but it means relearning the tool or documentation being less useful. The sheer amount of existing time people spent learning arcane git syntax means they're not going to switch to a hypothetical "New-GitCommit" function, even if it accepts arrays or PSCustomObject as input.
They could seize assets of miners big enough to need specialised energy deals, which would get rid of 90% of mining in the USA.
They could crack down on exchanges banking in USD, which would get rid of 90% of mining worldwide.
Stopping a single person running an algorithm on a single ASIC in a home environment is the impossible tail-end. I don't know if they even care about those, I'm not too worried about them.
That Kf8 really is the move of somebody living in another universe.
Truncate in MSSQL requires alter permissions, so a user that can wipe a table can also change its definition. Not true with delete.
You've got a list of countries and are pulling each country's national flower, national bird, largest port city etc.
Without outer joins, Liechtenstein with no ports doesn't show in the list at all. Sad news for people who want to know all countries, or Liechtenstein's national bird (eagle).
e.g.
select questions.Id , questions.Text , answers.Id , answers.Text
from questions left join answers on answers.QuestionId = Questions.Id
answers.Id is non-nullable as a primary key, so if answers.Text is null but answers.Id is not null they've declined to answer.