Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introducing Open Web Docs

opencollective.com

Post reply on HN
Print view View original

61–70 of 77 posts

Re: Introducing Open Web Docs

#61

Post by rini17 »

jefftk wrote: post #56
rini17 wrote: post #43

Earlier quoted context omitted.

Not much to be happy about here. The "Living standard" ensures that independent browser implementation from scratch is impossible. Even not from scratch, see MS Edge.

Impossible? Tell that to Flow: https://www.quirksmode.org/blog/archives/2020/01/new_browser...

Sounds like they have yet to implement the proverbial last 20% of features which is going to take 80% of development time.

> Well, it can render and interact with Gmail quite well. It’s pretty much perfect on a few sites we’ve targeted as focuses during development, but it struggles with many others.

Re: Introducing Open Web Docs

#62

Post by rini17 »

derangedHorse wrote: post #52
rini17 wrote: post #43

Earlier quoted context omitted.

Not much to be happy about here. The "Living standard" ensures that independent browser implementation from scratch is impossible. Even not from scratch, see MS Edge.

How does the standard disallow independent browser implementations?

Same as Microsoft's OOXML standard. There are independent implementations but not one is 100% compatible. Even if that complexity wasn't deliberate on MS's part, it's surely a welcome feature.

And AFAIK OOXML isn't currently evolving as much as this Open Web.

Re: Introducing Open Web Docs

#63

Post by deweller »

thinkmassive wrote: post #57
3395810 wrote: post #55

Earlier quoted context omitted.

What is the idea here? Open a channel with each website that I visit. Lockup the BTC that I will ever send them but only send it to them slowly each time I visit it.

Why wouldn’t you open a single channel with a well-connected routing node, and use it for all your payments?

Yes. In reality, users would have a connection open with one or a small number of routing nodes.

The end result is very cheap and quick funds transfers to any node on the network. This lightning network infrastructure would make micropayments feasible.

Granted, there are still problems to solve. But this is the dream.

Re: Introducing Open Web Docs

#64

Post by _vvhw »

mike-cardwell wrote: post #59
ahopebailie wrote: post #45

Earlier quoted context omitted.

That's where the idea started but that means the user has to be able to send Bitcoin. The purpose of Interledger is to abstract away that issue which is why Web Monetization is built on Interledger. You don't have to sign up with Coil to earn. There are other wallets that are on the Interledger network such as Uphold and Gatehub that can give you a payment pointer to put into your site's HTML. If you want your earnin…

I understand that the person paying probably needs an account somewhere, so that payments can be batched together to reduce transaction fees. However, there's no reason for me to have an account anywhere in order to receive bitcoin. All I need is a bitcoin address. I don't want to sign up with Coil, Interledger, Uphold, Gatehub, or any other random third party, in order to receive bitcoin. And there is zero reason wh…

Except that Interledger is not a "random third party", it's a protocol: https://interledger.org/

So that you can make payments to someone else regardless of whether they want to use Bitcoin or not.

I believe Interledger is the right level of abstraction for this, in the same way that you wouldn't want your email server to have to know or code against the lower protocols, e.g. Ethernet or WiFi, but only IP, TCP and SMTP. This way your email server can EHLO any email server, regardless of the network topology or underlying protocols.

Interledger does the same for payments.

Re: Introducing Open Web Docs

#65

Post by mike-cardwell »

_vvhw wrote: post #64
mike-cardwell wrote: post #59

Earlier quoted context omitted.

I understand that the person paying probably needs an account somewhere, so that payments can be batched together to reduce transaction fees. However, there's no reason for me to have an account anywhere in order to receive bitcoin. All I need is a bitcoin address. I don't want to sign up with Coil, Interledger, Uphold, Gatehub, or any other random third party, in order to receive bitcoin. And there is zero reason wh…

Except that Interledger is not a "random third party", it's a protocol: https://interledger.org/ So that you can make payments to someone else regardless of whether they want to use Bitcoin or not. I believe Interledger is the right level of abstraction for this, in the same way that you wouldn't want your email server to have to know or code against the lower protocols, e.g. Ethernet or WiFi, but only IP, TCP and SM…

Ok, so my bitcoin address is "bitcoin:1PQLtWnjUi1itHLG6QCQeHM3Nxua8pRsq1". What tag do I put in my HTML in order to receive payment from this system, without having to sign up anywhere?

Re: Introducing Open Web Docs

#67

Post by kaycebasques »

admax88q wrote: post #66

Remind me of webplatform.org another documentation project supported by multiple industry players. In the end everyone just went back to MDN.

> This is not a new docs platform: Open Web Docs is instead working closely with existing platforms, and its current priority is contributions to MDN Web Docs.

https://web.dev/open-web-docs/

Disclosure: I work on web.dev

Re: Introducing Open Web Docs

#68

Post by dflock »

mike-cardwell wrote: post #65
_vvhw wrote: post #64

Earlier quoted context omitted.

Except that Interledger is not a "random third party", it's a protocol: https://interledger.org/ So that you can make payments to someone else regardless of whether they want to use Bitcoin or not. I believe Interledger is the right level of abstraction for this, in the same way that you wouldn't want your email server to have to know or code against the lower protocols, e.g. Ethernet or WiFi, but only IP, TCP and SM…

Ok, so my bitcoin address is "bitcoin:1PQLtWnjUi1itHLG6QCQeHM3Nxua8pRsq1". What tag do I put in my HTML in order to receive payment from this system, without having to sign up anywhere?

You can just put that there - and then you hope that user agents implement this - or you can use interledger.

Re: Introducing Open Web Docs

#70

Post by bobajeff »

teruakohatu wrote: post #22

I don't understand why Mozilla cannot see that MDN should be part of their core mission. I can understand spinning off Thunderbird and Sunbird, but this really seems a big step in the wrong direction. Today their Mission webpage[1] states : "Our mission is to ensure the Internet is a global public resource, open and accessible to all." According to the Wayback Machine, 8 years ago that page[2] said: "Our mission is t…

I suspect this is part of Mozilla pulling what Netscape did at the end of their life.

Spinning off all their valuable products so they'll remain after their gone.

Post reply on HN