Re: Twitter Bluesky -- Building a Social Web

hi john / tim

thanks for the comments, I think there is a degree of singal to noise, that
we should try and move the needle back towards standards to read and write
to the web

im super interested in your use case of web payments, and have been for 1-2
decades

if you think about ledgers, and distributed ledgers, they are as old as
time or writing, and the data structure is simply that of an entity and a
balance

changes in that ledger are what we call transactions, which is a form or
reading and writing to the "web" which is really designed to be a multi
protocol space

i absolutely agree with you in that zero conf tx should be first class as a
user experience, so mempool for example close to definitive, and edits such
as replace by fee have potentially negative side-effects

creating a middle layer on the web, with basically royalty-free settlement
(e.g. bitcoin / lightning) I think is for me the most compelling use case
for the RWW

would be quite happy to pivot conversation into how to do that etc.

for example I was working with @bumi last week to add lightning payments to
the web via his extension

to do so I added :

<meta name="lightning" content="
lnurlp:LNURL1DP68GURN8GHJ7MRWVF5HGUEWVDHK6TMVDE6HYMRS9ASHQ6F0WCCJ7MRWW4EXCTECXQCQWSRAQ7"
/>

which routes to

https://lnbits.com/

this is a brilliant service

tim, it's fine to vent from time to time, I certainly am more guilty that
most of that, but id ask you to moderate that a bit and try and orient
posts also towards innovation around read and write web standards

best
melvin

On Fri, 24 Sept 2021 at 20:32, Bitcoin Error Log <bitcoinerrorlog@gmail.com>
wrote:

> Please remove me from this mailing list, it seems to be all noise and
> ranting about failed designs.
>
> On Fri, Sep 24, 2021 at 1:29 PM Timothy Holborn <timothy.holborn@gmail.com>
> wrote:
>
>> Seems foolish for me to highlight cimba / old rww server examples, but
>> perhaps we here the fastest path to peace?
>>
>> Perhaps someone who better understands the code could speak up to them?
>>
>> See, it something soon is preferred over something eventually.
>>
>> People have been shot with rubber bullets as a health measure in my
>> hometown.
>>
>> AFAIK: there were a few old pieces to it, in. Webizen.org which I'm happy
>> to gift to a suitable custodian.
>>
>> Personally, I tried in 2018 to make a mobile RWW app (very similar to gov
>> versions now being deployed, with different functionality).
>>
>> There's a couple of examples about mobile phones being used as webservers.
>>
>> Obviously also, the WebID-TLS goes away on a (personal) mobile device.
>>
>> Alot of people are using telegram, which uses alot of local data storage.
>>
>> I'm starting to build a list of non-US based apps, just to see if it's
>> possible.
>>
>> I care about human rights / rule of law.
>>
>> I do not support redaction of reality to support people who harm others.
>>
>> I also firmly believe, the place to sort out problems is courts of law.
>> Not otherwise.
>>
>> The challenge is in ensuring our tech, does that.  This has been the
>> problem that let me to W3C, given the focus of others, it remains the
>> problem. I'm not happy about it.
>>
>> Timothy Holborn.
>>
>> On Tue, 17 Aug 2021, 4:01 am Melvin Carvalho, <melvincarvalho@gmail.com>
>> wrote:
>>
>>> Might be interest to some folks here
>>>
>>> Jack's tweet:
>>>
>>> https://twitter.com/jack/status/1427315839666118662
>>>
>>> Website
>>>
>>> https://blueskyweb.org/
>>>
>>> "We're focusing on re-building the social web by connecting disconnected
>>> silos and returning control of the social experience to users. Our mission
>>> is to develop and drive the adoption of technologies for open and
>>> decentralized public conversation."
>>>
>>> I've added a page in our wiki, which we can track progress, and add
>>> links over time:
>>>
>>> https://www.w3.org/community/rww/wiki/Bluesky
>>>
>>
>
> --
> ~ John Carvalho
>
> Schedule: https://calendly.com/bitcoinerrorlog
> Chat: https://t.me/bitcoinerrorlog
> Social: https://twitter.com/bitcoinerrorlog
>