Avatar
Pip the WoT guy
f683e87035f7ad4f44e0b98cfbd9537e16455a92cd38cefc4cb31db7557f5ef2
simplifying the social graph so you can focus on building great experiences

It's a stupid observation, but it didn't click before for me, so maybe it's useful to you as well

1st post:

text and image under the name

2nd post:

text and image under pfp

Very cool!

I love the column of images right after the bio. However, the first and second posts after the column bugs me.

In the first post, the text is slightly shifted right.

I thought about a simple algorithm to fix this problem.

It's not perfect, but it will work most of the times.

Monday I'll publish

well, that's nothing new. App stored normally verify the code and provide the opinion showing what's allowed in the app store and what is not

That's why I like the idea of showing the list of people that you know that endorse/follow the target (app, podcast, mint...)

Among those people, maybe you'll find the developers you trust, maybe you'll find the podcasters you trust, depending on the use case.

The alternative is to build specified competency/recommendation events for each relevant topic/category, but who chooses the categories?

helps others only if the others have the same values as the reporter.

What if they have opposite values?

What kind of values has the reporter, on average?

#asknostr is there a client that supports long form articles with Latex?

Replying to Avatar Bitcoin Optech

Bitcoin Optech newsletter #305 is here:

- describes a proposed light client protocol for silent payments

- summarizes two new proposed descriptors for taproot

- links to a discussion about whether opcodes with overlapping features should be added in a soft fork

- summarizes popular Q&A from Stack Exchange

- Optech Newsletter #305 Recap on Twitter Spaces

https://bitcoinops.org/en/newsletters/2024/05/31/

Setor Blagogee posted to Delving Bitcoin to describe a draft specification for a protocol to help lightweight clients receive silent payments (SPs)...

https://bitcoinops.org/en/newsletters/2024/05/31/#light-client-protocol-for-silent-payments

Oghenovo Usiwoma posted to Delving Bitcoin about two new proposed descriptors for constructing taproot spend conditions...

https://bitcoinops.org/en/newsletters/2024/05/31/#raw-taproot-descriptors

Pierre Rochard asks if proposed soft forks that can provide much of the same features at a similar cost should be considered mutually exclusive, or whether it would make sense to activate multiple proposals and let developers use whichever alternative they prefer...

https://bitcoinops.org/en/newsletters/2024/05/31/#should-overlapping-soft-fork-proposals-be-considered-mutually-exclusive

Selected Q&A from Bitcoin Stack Exchange:

- What’s the smallest possible coinbase tx / block size?

- Understanding Script’s number encoding, CScriptNum

- Is there a way to make an address public but hide how many BTC it contains?

- Testing increased feerates in regtest

- Why is my P2P_V2 peer connected over a v1 connection?

- Does a P2PKH tx send to the hash of the uncompressed or compressed key?

- What are different ways to broadcast a block to the Bitcoin network?

https://bitcoinops.org/en/newsletters/2024/05/31/#selected-qa-from-bitcoin-stack-exchange

Bitcoin Optech will host an audio recap discussion of this newsletter with special guests Oghenovo Usiwoma and Pierre Rochard on Twitter Spaces Tuesday at 14:30 UTC. Join us to discuss or ask questions!

https://twitter.com/i/spaces/1eaKbgnYgOBGX

Why can't I zap you, damn it

I think the reverse is better, meaning relays want to accept only from whitelisted mints.

Otherwise, I can spin up a new mint , print tokens and DoS attack Keychat since any new mint by definition can't be in the blacklist.

✨ Interested in the Social Graph / Web of Trust?

I am looking for feedback on one of my articles.

DM me if you want to get a preview.