For everyone getting on me about the OP_RETURN stuff:

I’m 100% open to being wrong, I was wrong about CTV and how I thought it could be maliciously used, but I’ve also only heard a handful of the exact same arguments about this issue for years and have been very clear why I don’t think they are sufficient and why I believe some of them are not even relevant.

• “Filters for what goes into the chain are censorship,” this is false and filtering what can be done on chain is literally how and why Bitcoin works in every way that it works. This completely begs the question about what is spam and what is an exploit, which is the whole debate.

• “You can get around it” isn’t relevant either, as standards make a difference, which is exactly why the discussion is around changing the standards. Same as someone can jump over my fence, but that doesn’t mean having one vs not being allowed to build one has no effect at all.

• “Your node doesn’t do anything,” Is the same argument I was told during the blocksize war. I’m aware it doesn’t alter the entirety of the network and it’s just my node, so don’t tell me like you’ve discovered some new information, but it is still *my* node and someone proposing to remove my control over what I should or should not accept and propagate isn’t why I run a node. I use my node to mine and wish to build my own templates. Explain how putting Bitcoins use as money ahead of as a place to store jpegs is bad. I don’t care how ineffective you think it is, but why is it bad for Bitcoin?

• “Just run Knots.” Correct, I will be now. But that doesn’t mean I don’t have an opinion about changes being made to core, and when feedback is asked for I’ll give you my honest opinion. If that bothers someone then being part of a decentralized protocol is probably not the best path for them. All anyone has done since I got into bitcoin was argue. That’s how decentralization works.

• “They paid a fee and it’s valid.” See point 1. Every bug and malicious transaction and spam in the past was always valid and paid the proper fee. Again, completely begs the question as to what is spam and what the highest purpose of Bitcoin is.

This is a conversation about the purpose of Bitcoin, and yes that’s subjective, but that doesn’t mean it’s arbitrary or it doesn’t matter. Convince me that allowing random data in unrestrained sizes will make Bitcoin better money, or the technical argument doesn’t matter, imo. Technical conversations matter only after we decide what is *worth* building technical solutions for and what the purpose of any technical change is… so again, it begs the question and comes back to the same old disagreement.

This is how I see it and I don’t see how this is at all an unreasonable perspective. Just my 2 sats

No, it is still from January indeed. We are in the middle of a massive refactoring.

Epic Games v. Apple judge Yvonne Gonzalez Rogers just ruled that, effective immediately, Apple is no longer allowed to collect fees on purchases made outside apps and blocks the company from restricting how developers can point users to where they can make purchases outside of apps.

i have spent my afternoon tonight working on making a variable length integer encoding

the standard zig-zag varint scheme uses the 8th bit to indicate a further byte is part of the number, and it goes backwards, which confuses me

it took me ages to figure it out, but i have a similar encoding that instead of the extra bit being the sign of continue, instead it means the end, and the number sequence is reversed

so each byte in the buffer represents the smallest to largest places of what is effectively a base 128 encoding

when it finds a number that is bigger than that, with the 8th bit set, it removes the 8th bit and then stops and the sum of each base 128 digit multiplied by the power of the place, produces the result

i'm not sure why the standard method is done the exact opposite because it seems to me like this is simpler

to encode, i just AND the last 7 bits of each byte, then divide the number by 128, and once that gives a zero, the result of the last operation has 128 added

to decode, i first put the first byte value in the return value, and then each subsequent value i multiply by 128 (bitshift left by 7 bits) and then add that to the result, and when it finds a value over 128, it subtracts 128 and does the same operation and terminates

gotta formalize it into an actual algorithm now, but it's mostly written

i'm obsessed with encoding data and i wanted an encoding that can be read one byte at a time to scan the length values, without needing to have a second buffer to decode the variable integer numbers used for the length prefixes of fields

this is how i enjoy myself. fuck you, math is awesome.

I have memory turned off

it started to reply and then it detected something "harmful" it then the answer went away

Hack squat feels superior to traditional squat

#realy #devstr #progressreport

i slept on it and figured out the best way to do this was to have the relay check for configuration and if it's missing, it generates a first time password that you can use with the web UI at /api and you must add an npub to the admins list, after which the admin functions require auth from this

i also put the nurl CLI tool and the nauth tool that can generate expiring authorization tokens, which can then be used to do any function that is authorised on the HTTP UI

gotta finish up make sure all the HTTP endpoints actually are working and then i'm moving to putting the websocket in

yesterday i finally got the router i wrote working, so the main application is very lightweight... ah yes i need to make some build tags and separate files to be able to disable the apis once they are working, getting them initialised is a one liner in the main, but could be in a separate function in a separate file that can be masked out to disable it

All the NIPs so far are kinda retarded

But at least these retards built a social media platform with no bans, while nobody else was getting that done in this whole retard world

i have issues with several android nostr apps

they refuse to accept my nsec in bech32 form, the nsec.... format

idk why, because it works perfectly in my relay, and with alby, but amber right now is one signer i'm having trouble with at the moment, and it seems that new version of coracle android uses it, and without my nsec in it, it refuses to post notes, and without it installed, it refuses to run

i have no fucking idea what is wrong with you stupid devs that you can't even write a simple fucking bech32 decoder correctly, is there something wrong with your brains?

in order to decode my nsec into hex i have to sit down and spend 10 minutes writing a piece of code to deal with the problem that you guys are causing me, so, i'm just not using nostr on my mobile. coracle android is abominably slow anyway, waste of time, and i'm not using mister fucking hipster rockstar vitor pamplona's trash, which seems to be the nearest thing to a client that actually works on android

it's embarrassing as a programmer to be associated with you people, and it's embarrassing that you think that you are building freedom tech, but you really don't even know how to build a fucking fried egg

yes but it only takes maybe 200kbit or so to have one node on mars synced in realtime to earth, so a single 100mbit connection would probably let them share the chain

i'm pretty sure nikola tesla was scratching at the surface of how to do gravity nullification

i'm also pretty sure that gravity is an effect created by electrons in a quantum state we don't understand yet, so what i'm saying is essentially gravity nullification is about creating a field around an object that deflects this kind of particle, without that resistance to motion created by gravity you have the ability to travel a lot faster, this doesn't mean you can travel faster than light (that would be teleportation), but if you could get to mars in a day that would be sufficient i think

Compared to Bitcoin, Nostr has no single chain of blocks to represent a global state.

Our "nodes" don't pick the longest chain and censor every other alternative.

There are no miners to pick which posts are allowed to go into the chain.

There is no proof of work to create space in the chain.

There is no single core codebase to control any changes to the protocol.

There is just freedom.

The most raw encoding of freedom one can have.

What happened to RethinkDB?