Could you please write the same comment, but without the namecalling for what seems to be an honest mistake?
Good Lord, for all the talk about the Fediverse being a nicer place than corporate-controlled social media, comments like yours really show how that is very far from the rule.
https://fediverse.hanbitgaram.com/
410 Gone!
I was creating an implementation for the activity pub instance service transfer, but it seems to have spread far.
We are very sorry to those who have experienced inconvenience.
All temporarily used data has been removed and all data has been removed.
The figures in the data will soon converge to zero.
I trawled unintentionally.
The whole paragraph starts with "as a backer". I can rewrite it, but to be honest it's not that difficult to comprehend it as is.
I think you should have 2 “shortcut” buttons
Yeah, I think having sensible defaults would make a lot of sense and it is not hard to implement.
UI-wise, I'd try to implement a page where you can see all the artists you want to support, and each of one them would get a slider scale. It's (relatively) easy to program it in a way that the payout distribution percentage is preserved even if you add/remove artists.
Again, is it that different from Patreon?
With Patreon, the resource allocation signal is determined by the creators, but the people will support as many artists as they can/want. Letting the backer determine the amount given to each just makes this more granular, but besides that the mechanism is the same, no?
company taking all the money that customers have paid
I think you misunderstood. What I mean is that the customer will choose how much of their allocated budget goes to each artist.
Yeah, lots of pieces to be built, but taking this a bit to a meta-level one of the reasons I am thinking about this is because I believe this could also be the future of R&D for software and the services in the digital economy. To illustrate, I am not working on Communick because it is hugely profitable, but because the more I grow the amount of customers the more I am free to work and contribute to open source projects that can benefit everyone.
Oh, yeah, I think there could be many "default split strategies": play time, play count, direct/inverse correlation to general popularity, cutoffs for artists that already hit a funding threshold, extra weights for new work vs old catalog...
only make arbitrary payments to me based on nothing but a whim.
How is that different from the current situation? For most people, supporting indie artists is already an optional thing, those using Patreon could cancel "on a whim" as well, no?
based on the number of times an artist gets played
Doesn't that create a huge skew towards the pop-stars, who are already making money through other means (touring) anyway?
It doesn't have to be related to crypto. The point is that we have some technologies that are meant to make things more convenient, but in a lot of cases too much convenience is a bad thing.
Example: "tap-to-pay" credit or debit cards based on NFC are incredibly easy to be skimmed. You can go with a POS terminal to a really crowded area, and activate a transaction just by walking really close to people.
We’re talking about Meta
No, we talking about Bluesky.
Dorsey’s baby
He's moved on to Nostr. Also, Bluesky is open source and their work can be forked by anyone. You might disagree about whether it makes sense to work on another different protocol instead of trying to improve the ActivityPub ecosystem, but let's please not get into mud-slinging and this stupid tribal mentality.
Using a CDN does not come without downsides, though. Cloudflare itself is becoming another "too big to fail" entity of a system that is not supposed to depend on the resilience/capacity/budget of any single actor.
Personally, I'd rather see a tiered architecture for data, where servers are only responsible for guaranteeing the data from actors on their own servers, but everything else stored in a distributed, append-only stream of data. This would make a lot cheaper to run individual instances and would allow clients to obtain the data from multiple sources.