←back to thread

323 points plusCubed | 1 comments | | HN request time: 0.31s | source
Show context
egypturnash ◴[] No.18736059[source]
I just dug up info on how Brave’s contributions thing works and it feels like such a mess.

According to https://brave.com/publishers/

- once you have accumulated $100 in contributions they email “the webmaster at your site” and the owner of your domain according to the WHOIS. I assume this is “webmaster@domain.name”, which I sure don’t have set up on my personal site.

- you have to “check your balance frequently and transfer funds wherever you choose”, which suggests that there’s no way to just say “send my my balance every month” and forget about it.

This whole model totally breaks down when you remember that there’s a ton of independent creators who don’t have their own sites, but instead post stuff on another site. Is Brave going to realize that I’m following this particular person on YouTube, that person on Tumblr, this other person on Deviantart, etc, etc? And are they going to ping them or are they just gonna tell the people who own the site?

The page where you sign up to receive payments (https://publishers.basicattentiontoken.org) makes it sound like they understand YouTube accounts and nothing else, and as a creator whos interest in pivoting to video is nonexistent, screw that, I’ll stick with Patreon and it’s opt-in model that just transfers money into my bank account every month as long as I have patrons.

replies(8): >>18736102 #>>18736127 #>>18736278 #>>18736428 #>>18736434 #>>18736772 #>>18736773 #>>18737539 #
egypturnash ◴[] No.18736278[source]
Oh apparently they understand Twitch channels too, huzzah, ugh.
replies(1): >>18736359 #
egypturnash ◴[] No.18736359[source]
So I typed my domain into the setup thing and I got this:

"Hello. It looks like you are using WordPress!"

"Your domain is NOT using HTTPS.Uh oh! Your domain is NOT using HTTPS. You will need to fix that before continuing."

"The following error was encountered: SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: sslv3 alert handshake failure"

Why do I need to be using HTTPS before you'll think about paying me, Brave? I've been getting along posting comics on my HTTP site for an entire decade, and I'm really not interested in bothering to set that up. You are really not built with any understanding of the level of technical knowledge among people who make art, are you. And I'm unusually technical for an artist.

Oh wait there is a 'choose different verification method'. I can place a trusted file in my domain? Nope. Requires HTTPS. Or I can add a record to my DNS settings; let's try that... looks like I gotta wait for the dns to propagate, that's always fun.

replies(3): >>18736511 #>>18738315 #>>18741276 #
brandnewlow ◴[] No.18736511[source]
We're always trying to make the verification process better. On the one hand, it's a pain. On the other, we don't want to let someone other than you pass themselves off as you. The DNS and HTML snippet methods are similar to how verification works for many of Googles publisher and advertiser services, for what it's worth. Sorry this has proven frustrating but I hope DNS updates for you soon!
replies(3): >>18736723 #>>18737693 #>>18741886 #
1. imustbeevil ◴[] No.18736723[source]
> we don't want to let someone other than you pass themselves off as you

Wait, but that's exactly what you're doing to Tom Scott by collecting money in his name after he's asked you not to.