#209 Brave Rewards for Codeberg

Open
opened 6 months ago by zsoltsandor · 5 comments

I have noticed that codeberg.org (but not codeberg.eu) is a verified creator, but the Rewards donation is not set up to be a recipient. I think you should consider doing it. ;)

I have noticed that codeberg.org (but not codeberg.eu) is a verified creator, but the Rewards donation is not set up to be a recipient. I think you should consider doing it. ;)
hw commented 6 months ago
Poster
Owner

Somebody tried identity theft, creating the account in our name. We claimed it back to prevent abuse and check acceptance as donation channel then and when.

Right now about $20 have been donated in total via brave tokens. As soon the cost of wire transfer and/or cryptocurrency exchange fee are significantly exceeded, we will of course claim it.

Somebody tried identity theft, creating the account in our name. We claimed it back to prevent abuse and check acceptance as donation channel then and when. Right now about $20 have been donated in total via brave tokens. As soon the cost of wire transfer and/or cryptocurrency exchange fee are significantly exceeded, we will of course claim it.
Poster

Ugh, that's rude.
I hope you get to set it right. Even if it's mostly microdonations, but should work nicely after clarification and verification. Their exchange&co Uphold is based in the UK for us Europeans, and they have an office in Portugal too, so I guess we get to have default SEPA to our EUR IBAN accounts.

Ugh, that's rude. I hope you get to set it right. Even if it's mostly microdonations, but should work nicely after clarification and verification. Their exchange&co Uphold is based in the UK for us Europeans, and they have an office in Portugal too, so I guess we get to have default SEPA to our EUR IBAN accounts.
steko commented 6 months ago
Poster

For what it's worth, I think Cobeberg should stay away from Brave Browser (except for avoiding identity theft ... just the fact that it is possible is a good example of why Brave is a dangerous platform).

For what it's worth, I think Cobeberg should stay away from Brave Browser (except for avoiding identity theft ... just the fact that it is possible is a good example of why Brave is a dangerous platform).
Poster

It's not necessarily identity theft, but of course a possibility.
Brave Creators has native support for only a handful of "public services", like GitHub (where you need a Gist), Twitter (where you need a Tweet), Reddit (where you need a post). Let's just hope somebody was just ignorant about this, and thought could get a creators banner for their Codeberg repo, or their Cobeberg Pages site.

The domain-level verification is a bit more advanced, and has some safeguards. Even a subdomain has to be verified in DNS, or has to have a specified file in the canonical /.well-known/ path - it wont work in the /username/.well-known/ path.

It's not necessarily identity theft, but of course a possibility. Brave Creators has native support for only a handful of "public services", like GitHub (where you need a Gist), Twitter (where you need a Tweet), Reddit (where you need a post). Let's just hope somebody was just ignorant about this, and thought could get a creators banner for their Codeberg repo, or their Cobeberg Pages site. The domain-level verification is a bit more advanced, and has some safeguards. Even a subdomain has to be verified in DNS, or has to have a specified file in the canonical /.well-known/ path - it wont work in the /username/.well-known/ path.
Poster

Technically, you could have verified content on username.codeberg.eu - just like you can on github.io, gitlab.io, bitbucket.io, because you can expose content in the canonical /.well-known/ path. It won't interfere with other pages on these domains.
But you can't verify via DNS entry, as you don't have access to that, obviously.

If you have multiple domains pointing at the same CNAME, or A/AAAA direction, you can only have DNS verification in each DNS zone, as the file in /.well-known/ only supports one verifier ID - I know, because I've tried it.

Technically, you could have verified content on username.codeberg.eu - just like you can on github.io, gitlab.io, bitbucket.io, because you can expose content in the canonical /.well-known/ path. It won't interfere with other pages on these domains. But you can't verify via DNS entry, as you don't have access to that, obviously. If you have multiple domains pointing at the same CNAME, or A/AAAA direction, you can only have DNS verification in each DNS zone, as the file in /.well-known/ only supports one verifier ID - I know, because I've tried it.
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.