Wait. I thought the problem of being DDoS-ed is widely solved, i.e., just pick someone else (cloudflare, akamai, fastly, etc) to be the "proxy" of your site, and then let them defend the attack for you. No?
If you have deep enough pockets, sure, just pay anyone ASAP. But as far as I can tell, Codeberg is a non-profit entirely dependent on donations and, according to Drew DeVault, paying Cloudflare to protect SourceHut is prohibitively expensive even at his scale, so I doubt Codeberg is in any better position to finance this.
> More than 100.000 projects as of late on Codeberg. Codeberg e.V. has 401 members in total, these are 281 members with active voting rights, 113 supporting members and 7 honorary members.
[0] Joining: https://web.archive.org/web/20240106140505/https://join.code...
[1] Donating: https://web.archive.org/web/20240106140512/https://docs.code...
Afaik you can also do wire transfers in other countries but there are some fees involved, so isn't IBAN available to anyone with any bank account if they're okay seeing fees which the payment platform would otherwise hide?
https://en.wikipedia.org/wiki/International_Bank_Account_Num...
https://en.wikipedia.org/wiki/Single_Euro_Payments_Area
Only European bank accounts can do SEPA transfers.
Europe is many nations, not one.
SEPA is the Eurozone area that treats all transfers as domestic - usually free or near-free, and fast (max 1 day normally, max 10 seconds for instant transfer).
IBAN is just a numbering scheme to uniquely identify bank accounts worldwide. It has nothing to do with transfers. The closest thing would be SWIFT, though that's just an information protocol and says nothing about fees or times.
IBAN is also used by some countries outside of EU. It's basically just a way to assign an alphanumeric code to an account so that it also includes a country code, bank code, and checksum.
Also when getting money from Japan (mtgox), I had to put in the bank's branch address and some funny details one doesn't usually need, but it's possible to receive it on my IBAN account
.
According to SWIFT, the account is defined by a combination of bank identifier and account identifier. That is, account identifiers are supposed to be unique only within the bank. (Not sure about this part.)
There are many ways to identify an account, IBAN is one of them. Other methods require you to specify a "schema" (one of predefined codes 1-4 characters long), an "issuer" (string up to 35 chars), and "id" (string up to 34 chars).
I suppose banks know the values that make sense for their customers, and otherwise just forward the information to other banks.
IBAN is an alphanumeric string, where the first two characters are country code, and the meaning of the rest is country-specific. BIC is encoded in IBAN, so the information provided is redundant (in the payment you specify both the bank and the account, but the account also specifies the bank).
.
SEPA is a subset of SWIFT, with extra rules imposed. The currency is EUR, and the only allowed account identifier is IBAN.
That means, SEPA requires IBAN, but you can also use IBAN outside of SEPA as one of many possible ways of identifying the account. For example, if I pay from EU to USA, I am using my IBAN account in a non-SEPA payment.
(I can certainly see where you're coming from, I just wanted to provide some additional insight.)
They are just using sloppy language. SEPA is just a payment system for cheaper and faster payments. It uses still uses regular bank accounts to send from and to, it can be regarded as backwards compatible with normal bank transfers.
Instead of finding ways to isolate and blackhole the offending networks - granted that refining this data into small enough ranges would be quite difficult - they instead punish the targets, who are already suffering to begin with. This is mobster mentality.
You can bet that if random ISPs ranges would get blackholed when there are missbehaving clients, they would instantly come up with ways to detect and mitigate excessive traffic, net neutrality be damned.
This information can trickle down from the tier one that presently just blackholes the victim.
Nobody says that infrastructure that was designed in the late eighties can't be improved upon with additional functionality, namely passing top down information about missbehaving network ranges and or IPs.
As an ISP you already see devices on your network sending traffic in unusual patters, and when receive the warning that they are part of a DDoS you shut them down. If not, your whole range goes down, etc.
Let's add a fourth to the three-napkin protocol.