Well well well - here we go again.

Coming Soon to UK plebs....

Mill Rule Timber Frame Structures

- Design

- Consult

- Fabricate

- Install

- Finish

Low Time Preference

Proof of Work

Regenerative Forestry System

Stump to doorstep supply chain

Large spends with no KYC

Much Pleb, very wow

Buy a house with Bitcoin no KYC.

DM inquiries until the new website is up. Or comment below 👊

Hello everyone!

My name is Sarah, just joined NOSTR.

I am simply a 25 yo female who loves real financial educational and Bitcoin.

Since returning from Bitcoin++ in Austin, I've been trying to alternate between working on Lightning one week, and Bitcoin hacking on the other.

Mainly, I've been finishing my Script interpreter cpp modification so I can make more comprehensive benchmarks. I've also given in and ordered a raspberry pi 3, 4 and 5 to benchmark.

I hope to answer the key questions on what a realistic budget for large stack objects should be. In particular, there are four reasonable limits on their size (I'm not considering changing the 1000 stack element limit, since that seems roomy!)

1. 520 bytes. We are here now, but as Script gets better that will be very limiting.

2. 520,000 bytes: simply limit the total stack size, not individual entries.

3. 4,000,000 bytes. This allows you to put the largest possible transaction on the stack. But you need a total limit of at least twice this, so you can make a copy: you can't do much in script without doing this!

4. 400,000 bytes. If number 3 is too much of a reach, this means you can put any standard tx on the stack. Again, you want a total limit of at least twice this.

My laptop, with something stupid like 26MB of level 3 cache, and my build machine with 32MB, can handle this fine. But what about the Pi?

I'll find out next week...

Ever wonder what it was like working for a Bitcoin company in the early days? Did you know users back then were part crazy, part generous?

I started working at BitInstant late 2012, which allowed people to buy Bitcoin with cash. In the fall of 2013, I joined Blockchain(dot)info (BCI). The early days at BCI is what I want to focus on here.

BCI was the biggest non-custodial web wallet & the most used block explorer. I wore many hats as the first employee, but my main job was handling the support tickets.

My first day at BCI was chaos. I logged into Zendesk and saw THOUSANDS of tickets as old as January 2013. There was one guy, Ben Reeves, doing everything since inception. Support wasn't the highest priority.

After initially feeling overwhelmed, I decided to clean things up. I closed all tickets older than a few weeks, and included a message apologizing for the lack of response. I assured people this would no longer be the norm, and to open a new ticket if their issue was ongoing.

I had free reign over my job, and became obsessed with making sure users received help in a reasonable amount of time. It started as a goal to respond within 24 hours of a new ticket, which turned into 12 hours. Within a few months, the average response time was down to 2-4 hours, only because I had to sleep at some point! 😂

I didn't realize how little I knew about Bitcoin until I had to answer tickets about the Bitcoin network itself. After all, we weren't just a web wallet, but a block explorer! I spent many late nights digging around on BitcoinTalk, trying to learn more, so I could help users with their questions. Learning about Bitcoin back then wasn't impossible, but it wasn't easy.

Many early users were shocked to receive a response to their questions. To hear back so quickly was unheard of. There were many Bitcoin projects back then, but most didn't have dedicated support staff. If you received a response, it would be from the founder or some other developer. These guys didn't have the resources to tackle support, especially in a timely manner.

I quickly learned about the generosity of bitcoiners. Many users requested a btc address from me so they could send a tip for the help provided. Even when I told them it was unnecessary, as I was a paid employee, they insisted on tipping.

Many of these users were nuts. 😂 Here's an example that didn't happen frequently, but it happened:

A user opens a ticket during the time I'm actively watching the queue. I see it come in, respond within minutes with a solution, and he insists on tipping. I'm like, "Bro it's cool, don't sweat it," but this madlad won't leave me alone until he tips me.

I look at my tip jar - 0.5 BTC, which is worth a few hundred USD at the time. WTF, ARE YOU INSANE?! 🤯

Part of this generous attitude was about saying thank you, but I believe a bigger part was about the early proliferation of Bitcoin.

We preach the HODL mentality today, but Bitcoin wouldn't be what it is without the generosity of early adopters. So many bitcoins were given out freely so people could learn about it firsthand.

I believe many of the tips I received were from people who, at one point, also received free btc. It felt wrong to HODL these tips, so I paid it forward. I purchased work related items so I could do my job better. I tipped people on Reddit. I donated towards bitcoin-backed fundraisers, including when Andreas fundraised for Dorian Nakamoto. I did everything I could to keep that spirit of giving alive.

The landscape today has changed, but that spirit of generosity lives on. The best example is zapping on Nostr, where people are tipping each other via LN for posts and comments. It's beautiful to see!

Thank you, early adopters, for your generosity. You're a big part of why Bitcoin is what it is today. 🧡

Be kind, be generous, and be a little crazy. 😄

Given its historical purchasing power appreciation, I think it’s helpful for some to think of #Bitcoin as an annuity.

You don’t try to “take profits” on an annuity, like some sort of degenerate trader.

Rather, you build up your annuity/savings during your prime working years, then draw down (or borrow against) the balance over the ensuing decades, as needed.

This just in:

BITFINEX DATA BREACH CONFIRMED, 2.5TB OF DATA AND 400K CUSTOMERS DATA LEAKED: SHINOJI RESEARCH

Trusted third parties are security holes.

Do you consider cashu a bitcoin layer 2 or layer 3? Or is it not a layer at all? #asknostr

should we invite david chaum

Before the 1990s most computing was done on mainframes that were expensive and difficult to access, because that was simply the state of hardware.

Then we had a couple decades of software running on personal computing hardware because networking hardware sucked.

Now with broadband we're back to running software on servers because cloud computing has made it cost efficient, and software companies can have far greater control over the user experience.

The looming question in my mind: can we swing the pendulum back in the other direction by focusing on development of p2p apps and infrastructure?

A Saturday morning confession.

I am not in sales. I actually really despise the traditional salesman techniques.

I don’t like to ‘shill’ products, I’ve always believed if the product is awesome, people will hear about it and it will sell itself.

I’ve been feeling like a shiller of nostr.build accounts for a while now, and this was never my intention on nostr. I always just wanted to shitpost and help grow the nostr community.

With that said, media is very expensive to host and manage, and nostr.build now hosts ~80%+ of nostr medi (1.5mil files /1.1TB and growing). The best way I can continue to help support nostr is to keep nostr.build strong. To do this I have to shill accounts since it is our only income..

We do have some killer features that I’m really excited about, so that makes it easier.

Please know, I just want to be a normal nostr and Bitcoin psychopath 💜