Hacker Newsnew | past | comments | ask | show | jobs | submit | more arrayjumper's commentslogin

> 2. It's not just less humans, it s of worse quality

what do you mean by this? that humans not of the western world are "lower quality"?


I think GP meant that lower egg quality leads to more birth defects, etc. So not just fewer humans born, but those born have more problems. A statement which is completely independent from point 1.


I assumed that this characterization in this context meant "less capable to protect Earth/environment/humanity", which is not too controversial given the inverse correlation between average education level and birthrates


No , i mean lower sperm/egg quality. Why are people quick to jump to extreme conclusions here?


citation needed


Wow, was checking out the transactions at https://opencollective.com/open-web-docs/transactions?offset... and I see that Google and Microsoft have collectively contributed $500k.

Happy to see that there is corporate sponsorship for this. Gives me some hope that this will allow MDN to outlast any eventuality that might befall Mozilla.


Or as The Reg called it: “Google, Microsoft pitch in some spare change to keep Mozilla's Web Docs online bible alive. Turns out having coherent API documentation is useful for, well, everyone”

https://www.theregister.com/2021/01/26/mozilla_web_docs/



And a small Coil, who you've probably never heard of before, donated 40% of Google's/Microsoft's amount ($100k).

That's pennies to Google/Microsoft. For Coil.com on the other hand...

For the unaware, Coil is a subscription service that you pay a certain amount to, and that amount gets spread through websites you visit that have a WebMonetization tag in the <head> element:

    <meta name="monetization" content="crypto-address-here">
Pretty cool initiative. My personal website earned a total of $1 from it so far.


I've come across this before. In order to receive money, I should just be able to put:

  <meta name="monetization" content="bitcoin:my-bitcoin-address">
Or similar, on my website.

Doesn't work that way though. I have to sign up with somebody like coil.com and put an address they give me on my websites. This is just worse. Much much worse than it needs to be.


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 earnings to be converted to BTC that's possible I think.


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 why I would have to.


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.


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.


The documentation for Interledger appears to be for people who want to build software, not for people who want to send or receive money. And it talks about setting up accounts with xpring.io or rafiki.money.

I see no evidence that Interledger can be used for receiving money without having to set up accounts or run software. Plenty of evidence to the contrary.

As I said before, to receive bitcoin from one of these systems, there is nothing I should need to do other than advertise my bitcoin address. Anything more than that, and the system sucks.


> the system sucks

Correct.

What you want requires support in the user agent (web browser) though.


This is a dream that the lightning network aims to one day fulfill.


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.


bitcoin is not a currency, it's not a "money"


Thank you for your valuable contribution to the conversation.


Same here, I tried it and liked it. I've made a few dollars too, it's early days but it looks very promising. I especially like the fact that the site can know you're paying an unlock articles, hide ads, etc for you, even though you're paying a few pennies per minute.


Honestly, committing 100k to this is probably a more effective marketing spend than many...


Well... this is how I just found out about them. I find coil very interesting! Strongly thinking about becoming a member, but I would like to find out if the websites I follow use the web monetization tag first.


As far as I'm aware, there are two ways of discovering that:

1. Start a one month subscription and browse your websites. The add-on changes colour depending on whether the current site is monetized or not.

2. Try to find them here: https://coil.com/explore. If you click on "blogs", there's a search bar that you can use.

There's also a Twitter bot that tracks how many websites have it (https://twitter.com/WebMotized). Currently at 1400, with about a dozen of sites added weekly.


Finally someone seems to have done this right. Subscribed now, lets see how it goes!


so did they actually donate or did they pay the monetization amount that their algorithm determined MDN should have?


Not sure if this is ironical. Either way, it is a donation as the MDN pages do not have a <meta name="monetization" ...> tag and the payment wouldn't go through OpenCollective which does not seem to support Web Monetization.


This was a straight donation. A thriving Web ecosystem of independent developers and creators building and hosting their own content is what gets us out of bed in the morning.

Credit to Ali Spivak who kicked this all off and helped us realise what a crucial role good platform documentation plays and how important it is to fund good knowledgeable writers.


Click on the parent link, filter by $5k or more, scroll to the bottom. They actually donated. MDN doesn't seem to have that meta tag.


Pretty sure they donated, no need to doubt the donation like that.


Ok, I wasn't necessarily doubting the donation. I thought though that if they didn't donate but gave the money that their algorithm determined that it would be an interesting thing for several reasons:

1. would show coil is getting quite a bit of money.

2. would show importance of MDN.


Ah, yeah, I don't think that many people have the extension installed yet, but I can see them not requiring big sites to add a monetization header and just sending the money to them instead.


We're working to make the Web Monetization API a standard that browsers can adopt natively: https://webmonetization.org

The extension helps us bootstrap the ecosystem but a native integration is far superior. Check out Puma browser for an example of the integrated experience for mobile.


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.



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.


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.


I used wasm for a computer vision related feature we built at work. It allowed us to reuse a bunch of things from opencv without having to reimplement those things in JS.


They have an API using which you get a json representation of your files. That is the same as sketch (whose file format is essentially zipped json files).


> Native is nice, native is fast

Only if you are using a Mac. On linux, the zoom client is neither fast nor (in my admittedly slightly subjective opinion) nice.


Zoom is Electron isn't it? That's not native.


No, it's native. At least on Mac.

edit: judging by `strings`, it's Objective C/Cocoa app on Mac. As native as it can be. No idea on Linux.


It's Electron on Linux and what's being discussed is that it's slow on Linux. Nobody refuted that it's slow on macOS, it was even stated.


I will need to check if you’re right.

edit

just judged on dependencies of the deb package, it looks like a native app. But, I will check the actual app.

https://support.zoom.us/hc/en-us/articles/204206269-Installi...


That's an interesting anecdote, as I've only used zoom on linux, but not really related to what you quoted.


Interesting. I'm curious what machine spec you're on. I'm running Ubuntu 20.04 on an dell laptop (XPS 7590 with an i9 processor, 32gb ram, discrete Nvidia graphics card).

I see my processor spin up to 90% utilization whenever I do a zoom call.


The OP is talking about Android becoming closed "source". Not about it becoming a closed ecosystem.


> Guess which ones often have problems joining zoom meetings

As a linux user, I'd like to say that I've seen that happen just as often with OSX users on my team. I think that's just Zoom's shitty app. But I do agree about peripheral hardware issues plaguing Linux. Bluetooth headphones are still such a hassle on Ubuntu 20.04.


I think it's crazy to seriously consider using an OS where something as basic as Bluetooth is a hassle.


Bluetooth has never not been a hassle in my experience - and that goes for Android, Windows, Linux, OS X, iOS. There’s always something with the device or driver.

This goes especially for audio.

I’m going to guess that Apple peripherals + Apple OS on Apple hardware is actually hassle-free but then what’s the point of a standard.


Bluetooth in general isn't a hassle. Bluetooth audio is a little bit of a hassle in the sense that there's a workaround that you have to do.


> That it exists at all, as a democracy, is due to the immense efforts of the British....Indian citizens should be grateful to all of the above groups of people who have given them democracy as it is today

What? Are you serious with this line of thought that Indians should be grateful to the British for democracy? I'd like to quote Shashi Tharoor's arguments here from an Oxford Union debate [0] -

> It's a bit rich to oppress, enslave, kill, torture, maim people for 200 years and then celebrate the fact that they're democratic at the end of it. We were denied democracy sir! We had to snatch it, seize it from you! With the greatest of reluctance it was conceded.

[0] - https://youtu.be/f7CW7S0zxv4?t=722


I agree wholeheartedly. In my opinion, UPI has been an unmitigated success. Nearly everyone from a roadside street-food vendor to a 5 star hotel accepts UPI and it makes the whole flow of day-to-day payments entirely contactless which is especially useful with the COVID-19 situation.

Now if only they could introduce some way to enable subscription payments, it'd be the cherry on top.


So, subscriptions are possible - just programmatically request a payment on a recurring basis.

As a consumer I actually prefer this approach because I get a payment request that I must explicitly accept for my subscription to be renewed, as opposed to forgetting about a subscription and have it show up on my bank statement.

For example: Every month Netflix sends me a payment request asking me to pay for another month's service.

Perhaps they could allow for auto-withdrawing to reduce friction for subscriptions you definitely know you want, but I strongly feel this request-before-withdrawing model should be the default for any subscription service and anything else should be explicit opt-in.



Ohh. Thanks for linking this. I'm excited for this.


And completely trackable


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: