Avatar
Thorwegian πŸ‡³πŸ‡΄
c708943ea349519dcf56b2a5c138fd9ed064ad65ddecae6394eabd87a62f1770
1983 vintage. Lives in Oslo, Norway. Interested in tech, cooking, history, music, art and travel.

if you've been following what Microsoft has been doing in the software development space since Bill Gates left, you'll see that their approach has radically changed.

Google already has good AI researchers working for them and have similar AI models, but Microsoft is much freer to act in this space. they have hardly any reputation in search so any crazy stunt they pull will be good PR for them. any crazy stunt Google pulls will be bad PR for Google.

secp256k1 is a setting for ECC (elliptic curve cryptography) and SHA256 is a hashing function.

ECC and SHA are what you should be comparing because both of those are ciphers.

ECC is a type of public key cryptography. the most common type is RSA.

in Bitcoin, transactions are hashed with SHA256 twice and then that hash is encrypted with ECC using a private key. the hash will only decrypt properly with the corresponding public key, meaning that it serves as a signature. using ECC as the encryption method for signing is called ECDSA.

a hashing function takes some input and produces a short unreadable output, so it's a one-way cipher. for the same input it always produces the same output. in digital signatures you always produce a hash of the data that you sign instead of signing the data directly by encrypting all of it, because it's much faster this way.

you really want to read up on public key cryptography and then come back to understand how it's used in Bitcoin.

they're two very different things

i have "verbal nightmares" where people tell men how much i suck

it's an AI startup they acquired earlier that's been doing this stuff

imagine a weed smoking head of state

my friend laughed when i said there are more pretty girls on Nostr than on Mastodon πŸ˜†

still thinking about how to avoid redundant user lookup queries in my indexer.

i'm thinking i might make a collection in MongoDB for queried pubkeys, and it'll have a relay column and a timestamp column, and each time the event handler for a relay connection comes across a pubkey, it checks when was the last time that relay was queried for info about that pubkey, and only if it was before the connection was established does it explicitly run a query.

there must be a way of making a Nostr web client that doesn't cause the fan on your laptop to spin up like a jet engine

i think there are a couple of things but i'd have to think about it. a big one that was recently implemented across many servers was editing. when you edit a post, others can see that it was edited and you can check the edit history if you want. also, if you repost something and it gets edited, you get a notification about it, so you can check if you still approve of what you reposted. but you can't withdraw anything on Nostr. you can't undo a like or a repost.

how dare the animal have spirit

if you want to annoy people, when they ask how you're doing, tell them you're "super"

"do you like cheap groceries?"

"a Lidl"

"how often do you buy them?"

"oh, Aldi time"

Mastodon has a pronounced lack of cool chicks. there are some there but this place has more.