jp/www.byjp.me
1
0
Fork 0
mirror of https://github.com/by-jp/www.byjp.me.git synced 2025-08-22 18:03:49 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Fix reply & add summary

Browse source
This commit is contained in:
JP Hastings-Spital 2024-06-18 06:55:30 +01:00
parent ff662631ab
commit b499b9d1bd
2 changed files with 8 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
content/likes/2024-06-16/fg0hu/index.md
View file

@ -5,5 +5,8 @@ likeOf: https://micropolisweb.com/
references: references:
https://micropoliswebCom/: https://micropoliswebCom/:
url: https://micropolisweb.com/ url: https://micropolisweb.com/
type: game
name: Micropolis
summary: This is Micropolis in WebAssembly! Based on the original SimCity Classic from Maxis, designed by Will Wright, ported by Don Hopkins. This is just an unfinished evolving scrappy fiddle.
slug: fg0hu slug: fg0hu
--- ---

8
content/notes/2024-06-18/ts96a/index.md
View file

@ -1,7 +1,6 @@
--- ---
date: 2024-06-18T06:49:39.132+01:00 date: 2024-06-18T06:49:39.132+01:00
publishDate: 2024-06-18T06:49:39.132+01:00 publishDate: 2024-06-18T06:49:39.132+01:00
draft: true
inReplyTo: https://www.macchaffee.com/blog/2024/ddos-attacks/ inReplyTo: https://www.macchaffee.com/blog/2024/ddos-attacks/
references: references:
https://wwwMacchaffeeCom/blog/2024/ddosAttacks/: https://wwwMacchaffeeCom/blog/2024/ddosAttacks/:
@ -11,10 +10,13 @@ references:
summary: Mac's Tech Blog summary: Mac's Tech Blog
featured: https://www.macchaffee.com/static/favicon.png featured: https://www.macchaffee.com/static/favicon.png
slug: ts96a slug: ts96a
tags:
- IPFS
- web
--- ---
It's not a complete solution by any means (it would only work for static sites) but I'm leaning hard into the use of the peer-to-peer #IPFS to take the teeth out of DDoS attacks. It's not a complete solution by any means (it would only work for static sites) but I'm leaning hard into the use of the peer-to-peer [IPFS](/tags/ipfs) to take the teeth out of DDoS attacks.
Though today most IPFS sites are served from IPFS↔HTTP gateways (which will fall to a sufficient DDoS attack, like any other server), using the p2p IPFS protocol itself would mean an attacker could only ever take out specific peers. Though that's still unpleasant, the aim (taking down a given site) is unachievable, so it disincentivises site-specific attacks. Though today most IPFS sites are served from IPFS↔HTTP gateways (which will fall to a sufficient DDoS attack, like any other server), using the p2p IPFS protocol itself would mean an attacker could only ever take out specific peers. Though that's still unpleasant, the aim (taking down a given site) is unachievable, so it disincentivises site-specific attacks.
For example; you can read this comment over HTTP at www.byjp.me (protected by a mega-corp at the moment), or you could use IPFS and read it at /ipns/www.byjp.me (protected by any- and everyone using IPFS who's ever been to any part of my site). For example; you can read this comment over HTTP at https://www.byjp.me (protected by a mega-corp at the moment), or you could use IPFS and read it at /ipns/www.byjp.me (protected by any- and everyone using IPFS who's ever been to any part of my site).