Talk:Futurehome Smarthub mandatory subscription fee: Difference between revisions
HTTPS/SSL is a trust system |
m Keith moved page Talk:Futurehome Smarthub Mandatory Subscription Fee to Talk:Futurehome Smarthub mandatory subscription fee: sentence case |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 20: | Line 20: | ||
I tried to find a way to contact you as well, but without email, here I am! | I tried to find a way to contact you as well, but without email, here I am! | ||
* P2P platform. More resilient against DMCA since it allows more peoples to participate. Still can cause issues since some peoples are more likely to be backbone of content. It is also great on the resources sides. Easy to expend the storage, add new contents. | |||
** Worst case, you end up with different communities ("private archiving services" | |||
* P2P over ToR? Don't even ask me if that is even possible. | |||
* Possible issues: | |||
** Captcha | |||
** Cloudflare (trying to block bots) | |||
** dynamic pages. As per, it is unlikely two peoples will get the same exact page. Maybe the page append a timestamp for example. Maybe it offuscate html against automation, ... Now, you may not know if the page is indeed different or if somebody is messing with the page. On the good side, that shouldn't be too much of your case right now? That alone, could cause security in the whole system around integrity if enough of bad actors are there.* | |||
=== Integrity === | === Integrity === | ||
| Line 36: | Line 36: | ||
Each user has an identity (using a public/private certificate, what is driving HTTPS, also named SSL certificate). So you can't impersonate someone else (except if its private certificate leak). | Each user has an identity (using a public/private certificate, what is driving HTTPS, also named SSL certificate). So you can't impersonate someone else (except if its private certificate leak). | ||
==== SSL Features (if you want to read more) === | ==== SSL Features (if you want to read more) ==== | ||
SSL certificates allow sub-certificate, which allow trust to be inherited. | SSL certificates allow sub-certificate, which allow trust to be inherited. | ||
| Line 53: | Line 53: | ||
You could also do it more on a passive way (which may also be an issue for the page integrity, as per, if only one guy visit it in 5 years... it is possible the page has been updated in the meanwhile). Peoples add a browser extension that try to push into the system page they are looking. (But for privacy... that may be another issues) | You could also do it more on a passive way (which may also be an issue for the page integrity, as per, if only one guy visit it in 5 years... it is possible the page has been updated in the meanwhile). Peoples add a browser extension that try to push into the system page they are looking. (But for privacy... that may be another issues) | ||
== Internet Archive with Signed Timestamps? == | |||
Perhaps we could interest the Internet Archive to add timestamps/digital signatures to pages they archive, so that we could then download said page, with a timestamp and a signature that could persist past any DCMA takedowns in our own archives and be used for proof of past existence of content despite legal denial of service? | |||
The flow would be.... see website page with bad terms, ask archive.org to archive said page with timestamp/signature, wait for that to happen, then grab a local copy and use that with "retrieved on" added to the footnote on a given wiki page. | |||
[[User:Mikewarot|Mikewarot]] ([[User talk:Mikewarot|talk]]) 19:24, 1 September 2025 (UTC) | |||