Mats Henricson [ARCHIVE] / is on Nostr

⚠️ This account is not associated with a real person. It's an archival account for mailing list messages.
🗓️ Active from 2013-07-12 to 2015-06-14
💬 Posted a total of 4 messages
📚 Participated in the following categories: Bitcoin-development
🔇 Please do not DM this user as it's used for archive purposes only.

Last Notes

2023-06-07 17:37:33

- reply

📅 Original date posted:2015-06-14
📝 Original message:Jeff,
with all due respect, but I've seen you saying this a few times
now, that this decision is oh so difficult and important.
But this is not helpful. We all know that. Even I.
Make a suggestion, or stay out of the debate!
Mats
On 06/14/2015 07:36 AM, Jeff Garzik wrote:
> The choice is very real and on-point. What should the block size limit
> be? Why?
>
> There is a large consensus that it needs increasing. To what? By what
> factor?
>
> The size limit literally defines the fee market, the whole damn thing. If
> software high priests choose a size limit of 300k, space is scarce, fees
> are bid high. If software high priests choose a size limit of 32mb, space
> is plentiful, fees are near zero. Market actors take their signals
> accordingly. Some business models boom, some business models fail, as a
> direct result of changing this unintentionally-added speedbump. Different
> users value adoption, decentralization etc. differently.
>
> The size limit is an economic policy lever that needs to be transitioned
> -away- from software and software developers, to the free market.
>
> A simple, e.g. hard fork to 2MB or 4MB does not fix higher level governance
> problems associated with actors lobbying developers, even if a cloistered
> and vetted Technical Advisory Board as has been proposed.
>
>
>
>
>
>
>
> On Sun, Jun 14, 2015 at 1:20 AM, Eric Lombrozo <elombrozo at gmail.com> wrote:
>
>> I definitely think we need some voting system for metaconsensus…but if
>> we’re going to seriously consider this we should look at the problem much
>> more generally. Using false choices doesn’t really help, though ;)
>>
>> - Eric Lombrozo
>>
>>
>> On Jun 13, 2015, at 10:13 PM, Jeff Garzik <jgarzik at bitpay.com> wrote:
>>
>> On Sun, Jun 14, 2015 at 1:08 AM, Eric Lombrozo <elombrozo at gmail.com>
>> wrote:
>>
>>> 2) BIP100 has direct economic consequences…and particularly for miners.
>>> It lends itself to much greater corruptibility.
>>>
>>>
>> What is the alternative? Have a Chief Scientist or Technical Advisory
>> Board choose what is a proper fee, what is a proper level of
>> decentralization, a proper growth factor?
>>
>>
>>
>
>
>
>
> ------------------------------------------------------------------------------
>
>
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

2023-06-07 17:36:22

- reply

📅 Original date posted:2015-06-01
📝 Original message:Hi!
My fingers have been itching many times now, this debate
drives me nuts.
I just wish all posters could follow two simple principles:
1. Read up. Yes. All of what has been written. Yes, it will
take many hours. But if you're rehashing what other
smarter people have said over and over before, you're
wasting hundreds of peoples time. Please don't.
2. Be helpful. Suggest alternatives. Just cristizising is
just destructive. If you want no change, then say so.
Mats

2023-06-07 17:06:35

- reply

📅 Original date posted:2013-09-05
📝 Original message:The Trsst project (Twitter + RSS + Google Reader = Trsst social network)
has some interesting ideas:
http://www.trsst.com/paper/
Quote:
In Trsst, every user account is a digital wallet. Authors and
individual pieces of content can receive secure and anonymous
micro-payments of digital crypto-currency, enabling long-
envisioned content monetization schemes where authors receive
small payments each time their content is consumed, shared,
or "liked".
Mats
On 09/05/2013 10:23 AM, Wendell wrote:
> Mike Hearn had a rather cool idea about watermarking images with Bitcoin addresses in order to facilitate auto-magically linking social networking profiles: apparently even without API access, reasonably large user images are available publicly via the major services (Facebook, Twitter).
>
> Since this process would necessarily be somewhat manual and would of course be "undone" anytime the user changed his/her profile image, it is probably not a solution for everyone. But it seems that this could be a helpful way to at least _begin_ organizing Bitcoin around people and organizations in a way that is broadly familiar.
>
> I haven't been able to get this to work myself, but Blockchain.info seems to offer sending 'coin via Facebook:
> https://blockchain.info/wallet/send-via
>
> There is also the very cute Bitcoins With Friends:
> https://bitcoinswithfriends.com/
>
> Most of the other apps that I have seen at one point or another have vanished. I recall reading that Facebook was not particularly friendly to them, hence the present interest in more subversive (?) ways of making those connections.
>
> Again, I am not 100% sure that this is the correct place for it, but I'm opening this thread to other such ideas in case anyone else wants to discuss it. Our motivation is making Bitcoin easier to use, and we suspect that even imperfect social network support will move us closer to that goal.
>
> -wendell
>
> grabhive.com | twitter.com/grabhive | gpg: 6C0C9411
>
>> Re-orienting Bitcoin around people and companies is something we wanted to do for a long time. How do you get an address linked to a personal profile? Someone was asking me about this last month and I suggested watermarking addresses into social network profile pictures. The advantage of that approach is every social network supports profile pictures and big ones like Facebook and Twitter allow querying of somebodies picture without needing any API or user authentication, eg:
>>
>> https://graph.facebook.com/i.am.the.real.mike/picture?type=large
>>
>> So obviously with such a thing you can send to any Facebook user who has configured their profile correctly. There's a library that implements watermarking that can survive social network recompression, but it is (doh) written in Java ;)
>
> ------------------------------------------------------------------------------
> Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
> Discover the easy way to master current and previous Microsoft technologies
> and advance your career. Get an incredible 1,500+ hours of step-by-step
> tutorial videos with LearnDevNow. Subscribe today and save!
> http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

2023-06-07 17:04:32

- reply

📅 Original date posted:2013-07-12
📝 Original message:This is way off the point, but please write Bitcoin, not BitCoin.
Mats
Rob Meijer <rmeijer at xs4all.nl> wrote:
>Completed the first draft of my slides+speaker-notes for my upcoming
>"Defeating Trojans" talk at the OHM2013. BitCoin is one of the main
>examples I use in this talk to emphasize the need for programs like
>BitCoin to have
>their own private storage apart from $HOME.
>
>To make sure I don't misrepresent BitCoin, could anyone here help me out
>by reviewing my slides, please let me know and I'll e-mail my (open
>office) slides to you for review.
>
>Tnx,
>
>Rob
>
>
>------------------------------------------------------------------------------
>See everything from the browser to the database with AppDynamics
>Get end-to-end visibility with application monitoring from AppDynamics
>Isolate bottlenecks and diagnose root cause in seconds.
>Start your free trial of AppDynamics Pro today!
>http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>_______________________________________________
>Bitcoin-development mailing list
>Bitcoin-development at lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bitcoin-development