I think https://liberapay.com/ does that?

Stripe has an amazing amount of currencies for payouts and accepts all kinds of payment methods, really really comprehensive. Pretty low fees too. Simple API and great great docs. They’re all good.

That’s really nicely done, good work!

We really need to figure out the payment system for the fediverse… Good to see someone trying things.

When I put Stripe integration into PieFed I had absolutely zero donations through there, meanwhile my Patreon and Librepay had dozens of dollars in donations. Dozens!

People really really didn’t want to donate directly, for some reason. So I disabled the Stripe option.

Instead, Patreon takes 8% and their only payout method is Paypal so Paypal takes a percentage (5%?) and then when I transfer it to my bank from Paypal there’s a currency conversion so they take another 5%? and then I pay tax on whatever remains…

I wish CrowdBucks better luck than I had.

If I ever start my own dev agency this will be our secret weapon. Every developer gets an office with a door.

It doesn’t access old browser history but from the moment it is installed onwards it sends every url you visit to 7 instances, to do a search. Any one of those instances could save those urls and over time build up a profile on someone.

I guess if the logic for finding the posts was done on the server then you would only need one API call - the extension would just send through whatever url it had. That would be more efficient.

If this gets popular I’d be open to adding a dedicated API endpoint for this to PieFed.

Kind of a privacy nightmare though, aye. Sending your whole browser history to a third party… But that’s a whole different issue.

All it would need is about 10 simultaneous users and the load on the server would be unacceptable to me, as an instance admin. I only run PieFed instances so this isn’t going to impact me unless you add PieFed support (please don’t).

This is going to absolutely hammer the search API endpoint. Every single time you visit any web page there will be around 5 different requests to lemmy-instance/api/v3/search (see generateUrlVariations()) and running a search is pretty heavy on the server.

I just read the code, didn’t actually install the extension, so I could be wrong but at first glance this looks like it would cause real problems if a significant number of people started using it.

The outbox on a Lemmy community only has the last 50 posts and there is no pagination to get another 50. Also Lemmy posts have no replies collection so it’s impossible to get the replies without using their API.

a similar amount of energy to running a hair dryer

We see a lot of those kinds of comparisons. Thing is, you run a hair dryer once per day at most. Or it’s compared to a google search, often. Again, most people will do a handful of searches each day. A ChatGPT conversation can be hundreds of messages back and forth. A Claude Code session can go for hours and involve millions of tokens. An individual AI inference might be pretty tame but the quantity of them is another level.

If it was so efficient then they wouldn’t be building Manhatten-sized datacenters.