Taler ensures asymmetric privacy. The buyer does not expose their identity to the seller (or the government), nor what they bought to their bank/payment-provider. But the seller needs to expose their income for tax purposes. This is a good compromise as it follows existing law and prevents tax-evasion and (to some extend) money laundering.

Yes, like cash.

Except for some very niche crypto-currency users no one stores “money” like that. You have a bank account where you store money.

The same audience as Paypal, which seems to be reasonably popular. Except this is privacy preserving and an open standard that many providers can use.

It can be many different ones. Usually your home bank would allow you to exchange some Euro into Taler tokens and then use those to pay in compatible stores. But instead of a centralized system there can be many different exchanges that follow the same standard (protocol) and can be used with the same software and wallet apps.

Taler is not a store of value. Exchanging some Taler is like going to the ATM and withdrawing some cash to put in your wallet.

If there’s one thing that we learnt from the cryptocurrecy industry, it’s that users don’t care to understand how the technology works, and will do stupid things.

Yes, like turning a digital payment system into a speculative asset and making it basically impossible to actually buy anything with it.

But it seems you are totally missing the point of Taler, as it doesn’t even aim to be anything like so called crypto-“currencies”. It’s a digital payment system like Paypal, but decentralized.

It is what you make out of it. Basically it is an ActivityPub federated framework with various modules including one for microblogging.

The bigger question is why Matrix didn’t follow the long established standard for this, which is using @.

But I guess it fits into the general pattern of: Monolithic, Awefully Trendy ReImplementation of XMPP (MATRIX).

P.S.: it’s nice to be able to have your ActivityPub, XMPP and Email all on the same address 👍

Seems like an obvious suggestion, but Nextcloud can do that quite well.

That seems like a fun toy. Thanks for sharing.

Being worked on apparently.

https://bewcloud.com/

https://github.com/bewcloud/bewcloud

Is a new option I recently learned about.

Like a sister comment here already said, mini-ITX boards and cases often come with unexpected space contraints, and annoying things like the RAM not fitting under the CPU cooler etc.

You will probably save yourself some hassle if you go for one of these N100 NAS boards that come with a soldered on CPU and a built in cooler.

https://garagehq.deuxfleurs.fr/ maybe?

Except for one addition route in the reverse-proxy (which might not be needed anymore in newer versions) it is really only changing the port that points to Lemmy-ui to point to Anubis instead.

You might have to sit through a slightly longer waiting time every now and then, but Anubis is not invoked on every connection and once your browser is found to be worthy you can surf as before.

The bigger issue might be if that old hardware can’t run a modern up to date browser, because then it doesn’t work at all, which is the real down-side of Anubis.

I tried it with the default settings of the Tor browser though and that worked ok surprisingly.

Ah, ok. Yes that kinda makes sense if you think of Anubis as a CAPTCHA equivalent, but it really isn’t as I tried to explain in my other post.

Yes and so far only minor issues that are hard to replicate. Thanks again for helping us to find out the final issue with the setup a few weeks ago.

I agree that it would make more sense to only enable it for unauthenticated visitors, but that seems a bit hard to do with an external software like Anubis.

It does not stop them, but it does make it more expensive and slower for the attacker.

This is a bit of a misconception of what Anubis does. It uses PoW to enforce a full browser environment, but the PoW is only used once a week or so (or when there is some suspicious things detected). The PoW is then used to autogenerate a kind of password to store in the browser cookies, and to generate this “password” you can’t use the simple servers that are used at scale to scrape (practically ddos) the open internet right now.

The main problem is with complex websites like git forges that these AI scrapers hit all the computational expensive deep endpoints and practically force them to shut down from overloading the CPU.

Since I was forced to implement Anubis for my Forgejo instance I also experimented with it on Lemmy. Right now the results show that while Lemmy isn’t as badly effected by this AI scraping, there is still quite a bit of it happening. After adding Anubis the overall traffic went down by about a third on our instance, and it prevents the regular traffic spikes we previously saw and had no real explanation for.

But we also ran in some strange issues with it. Most likely it is caused by Anubis detecting mobile connections with switching IP addresses as possible scrapers (who are known to first access pages from a more complete server to get cookies and so on and then switch to a cheaper server on a different IP to do the actual scraping). But we are still figuring out how to replicate those issues, and they might have been fixed in the latest Anubis update we applied yesterday.