#web30 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #web30, aggregated by home.social.
-
https://www.tkhunt.com/2299209/ 自律型AIエージェント戦略：データ活用と未来型ビジネス構築 #AgenticAi #AI #ArtificialIntelligence #DAO #DX #IoT #Web30 #アナリティクス #エージェント型AI #クラウド #ソーシャル #ブロックチェーン #人工知能
-
https://www.tkhunt.com/2299209/ 自律型AIエージェント戦略：データ活用と未来型ビジネス構築 #AgenticAi #AI #ArtificialIntelligence #DAO #DX #IoT #Web30 #アナリティクス #エージェント型AI #クラウド #ソーシャル #ブロックチェーン #人工知能
-
https://www.tkhunt.com/2299209/ 自律型AIエージェント戦略：データ活用と未来型ビジネス構築 #AgenticAi #AI #ArtificialIntelligence #DAO #DX #IoT #Web30 #アナリティクス #エージェント型AI #クラウド #ソーシャル #ブロックチェーン #人工知能
-
https://www.tkhunt.com/2299209/ 自律型AIエージェント戦略：データ活用と未来型ビジネス構築 #AgenticAi #AI #ArtificialIntelligence #DAO #DX #IoT #Web30 #アナリティクス #エージェント型AI #クラウド #ソーシャル #ブロックチェーン #人工知能
-
https://www.tkhunt.com/2299209/ 自律型AIエージェント戦略：データ活用と未来型ビジネス構築 #AgenticAi #AI #ArtificialIntelligence #DAO #DX #IoT #Web30 #アナリティクス #エージェント型AI #クラウド #ソーシャル #ブロックチェーン #人工知能
-
自律型AIエージェント戦略：データ活用と未来型ビジネス構築 https://www.yayafa.com/2792347/ #AgenticAi #AI #ArtificialGeneralIntelligence #ArtificialIntelligence #DX #đạo #IoT #Web30 #アナリティクス #エージェント型AI #クラウド #ソーシャル #ブロックチェーン #人工知能 #汎用人工知能
-
自律型AIエージェント戦略：データ活用と未来型ビジネス構築 https://www.yayafa.com/2792347/ #AgenticAi #AI #ArtificialGeneralIntelligence #ArtificialIntelligence #DX #đạo #IoT #Web30 #アナリティクス #エージェント型AI #クラウド #ソーシャル #ブロックチェーン #人工知能 #汎用人工知能
-
自律型AIエージェント戦略：データ活用と未来型ビジネス構築 https://www.yayafa.com/2792347/ #AgenticAi #AI #ArtificialGeneralIntelligence #ArtificialIntelligence #DX #đạo #IoT #Web30 #アナリティクス #エージェント型AI #クラウド #ソーシャル #ブロックチェーン #人工知能 #汎用人工知能
-
Opera: Rewind The Web to 1996 (Opera at 30)
#HackerNews #Opera #Rewind #1996 #Web30 #Nostalgia #BrowserHistory
-
Opera: Rewind The Web to 1996 (Opera at 30)
#HackerNews #Opera #Rewind #1996 #Web30 #Nostalgia #BrowserHistory
-
Opera: Rewind The Web to 1996 (Opera at 30)
#HackerNews #Opera #Rewind #1996 #Web30 #Nostalgia #BrowserHistory
-
Opera: Rewind The Web to 1996 (Opera at 30)
#HackerNews #Opera #Rewind #1996 #Web30 #Nostalgia #BrowserHistory
-
Opera: Rewind The Web to 1996 (Opera at 30)
#HackerNews #Opera #Rewind #1996 #Web30 #Nostalgia #BrowserHistory
-
@GossiTheDog "Honestly', this update sounds like Mastodon is finally ready for mass adoption. Just needs a native token for gas fees. 🤑🤑🤑
#web30 (a solution still looking for a problem)
-
@GossiTheDog "Honestly', this update sounds like Mastodon is finally ready for mass adoption. Just needs a native token for gas fees. 🤑🤑🤑
#web30 (a solution still looking for a problem)
-
@GossiTheDog "Honestly', this update sounds like Mastodon is finally ready for mass adoption. Just needs a native token for gas fees. 🤑🤑🤑
#web30 (a solution still looking for a problem)
-
@GossiTheDog "Honestly', this update sounds like Mastodon is finally ready for mass adoption. Just needs a native token for gas fees. 🤑🤑🤑
#web30 (a solution still looking for a problem)
-
@GossiTheDog "Honestly', this update sounds like Mastodon is finally ready for mass adoption. Just needs a native token for gas fees. 🤑🤑🤑
#web30 (a solution still looking for a problem)
-
TIM ganha prêmio de inovação internacional com uso de APIs abertas e Spatial Web
-
TIM ganha prêmio de inovação internacional com uso de APIs abertas e Spatial Web
-
Around 2008 (+/- 3y) was the time, when that Internet (TM) #web20 has died. We believed in the freedom of speech and stuff.
After that, the (a) social #web30 brought us to algorithmic controlled mindset of people based on the most populist content.
It's legit. Populist stuff creates the most emotions thus clicks thus money.
So, do not blame single players. Blame walled gardens with capitalist interest.
-
Around 2008 (+/- 3y) was the time, when that Internet (TM) #web20 has died. We believed in the freedom of speech and stuff.
After that, the (a) social #web30 brought us to algorithmic controlled mindset of people based on the most populist content.
It's legit. Populist stuff creates the most emotions thus clicks thus money.
So, do not blame single players. Blame walled gardens with capitalist interest.
-
Around 2008 (+/- 3y) was the time, when that Internet (TM) #web20 has died. We believed in the freedom of speech and stuff.
After that, the (a) social #web30 brought us to algorithmic controlled mindset of people based on the most populist content.
It's legit. Populist stuff creates the most emotions thus clicks thus money.
So, do not blame single players. Blame walled gardens with capitalist interest.
-
We have some good news coming from France! 🗞️ 🇫🇷
🏆 Two of our #NGISargassoInnovators have been selected as top companies in France working with #Web30 technologies: Startin'blox, founded by Alex Bourlier, and @werenode, whose CEO is Benoît Maïsseu. The list has been made by the F6S Community
🌊 Discover in this article which are their #NGISargasso projects selected by our evaluators to shape an #InternetOfHumans:
https://ngisargasso.eu/2025/01/14/the-ngi-sargasso-innovators-startinblox-and-werenode-included-in-the-top-26-web-3-0-companies-and-startups-in-france/Congratulations!
-
We have some good news coming from France! 🗞️ 🇫🇷
🏆 Two of our #NGISargassoInnovators have been selected as top companies in France working with #Web30 technologies: Startin'blox, founded by Alex Bourlier, and @werenode, whose CEO is Benoît Maïsseu. The list has been made by the F6S Community
🌊 Discover in this article which are their #NGISargasso projects selected by our evaluators to shape an #InternetOfHumans:
https://ngisargasso.eu/2025/01/14/the-ngi-sargasso-innovators-startinblox-and-werenode-included-in-the-top-26-web-3-0-companies-and-startups-in-france/Congratulations!
-
We have some good news coming from France! 🗞️ 🇫🇷
🏆 Two of our #NGISargassoInnovators have been selected as top companies in France working with #Web30 technologies: Startin'blox, founded by Alex Bourlier, and @werenode, whose CEO is Benoît Maïsseu. The list has been made by the F6S Community
🌊 Discover in this article which are their #NGISargasso projects selected by our evaluators to shape an #InternetOfHumans:
https://ngisargasso.eu/2025/01/14/the-ngi-sargasso-innovators-startinblox-and-werenode-included-in-the-top-26-web-3-0-companies-and-startups-in-france/Congratulations!
-
Privacy Implications of Web 3.0 and Darknets – Source:www.darknet.org.uk https://ciso2ciso.com/privacy-implications-of-web-3-0-and-darknets-sourcewww-darknet-org-uk/ #rssfeedpostgeneratorecho #1CyberSecurityNewsPost #rssfeedsAutogenerated #CyberSecurityNews #Darknetorg #darknets #privacy #web30
-
Privacy Implications of Web 3.0 and Darknets – Source:www.darknet.org.uk https://ciso2ciso.com/privacy-implications-of-web-3-0-and-darknets-sourcewww-darknet-org-uk/ #rssfeedpostgeneratorecho #1CyberSecurityNewsPost #rssfeedsAutogenerated #CyberSecurityNews #Darknetorg #darknets #privacy #web30
-
Privacy Implications of Web 3.0 and Darknets – Source:www.darknet.org.uk https://ciso2ciso.com/privacy-implications-of-web-3-0-and-darknets-sourcewww-darknet-org-uk/ #rssfeedpostgeneratorecho #1CyberSecurityNewsPost #rssfeedsAutogenerated #CyberSecurityNews #Darknetorg #darknets #privacy #web30
-
Interview with Page Howe | New ICANN Round: How it can Affect Web3?
https://youtube.com/live/eFsvbLgM58k?si=LTE1j9l8tdJAjx8m
#web3 #web30 #web3domain #web3domains #freename #unstoppabledomains #ens
-
Interview with Page Howe | New ICANN Round: How it can Affect Web3?
https://youtube.com/live/eFsvbLgM58k?si=LTE1j9l8tdJAjx8m
#web3 #web30 #web3domain #web3domains #freename #unstoppabledomains #ens
-
My difficulty with IPFS specifically has to do with some of its unique characteristics as a storage mechanism, the primary characteristic being the inability to modify or delete content. This is not a side effect of the cryptographic methods used, nor of some limitation in software engineering. This is a specific design goal of IPFS and IPFS is unique in this regard even among major storage technologies like hard drives used in personal computers and servers, cloud storage technologies (AWS S3, Google Cloud Storage, Azure Blob Storage, etc.) and commercial storage offerings like Dropbox, iDrive and others.
What harms follow from this type of implementation? Here are two:
Clearly illegal and harmful content can be permanently stored on IPFS. I am thinking of CSAM, malware, defamatory content, and other harmful content. This type of content cannot be deleted or moderated by the core IPFS technology. This is not a theoretical issue as there are known cases of harmful content on IPFS. Harmful content can be deleted from a relational database, not so with IPFS.
The second issue is that I think IPFS goes a long way towards depriving citizens of their data rights under the EU GDPR and California CCPA and CPRA. These regulations brought forward by democratic governments express the rights of citizens related to the ownership of their private information. Under these regulations (and others) an individual has the right to be forgotten (right of deletion), right to know and control who their personal data is shared with, the right to correct erroneous information, and so forth. To me it appears that IPFS intentionally prevents the exercise of these rights.
I don’t deny that there are positive aspects of IPFS. Where else would we store our precious NFTs? Just kidding. I can definitely see some benefits of a decentralized and distributed storage mechanism. I don’t see that IPFS or other decentralized technology prevents censorship in any meaningful way – censorship appears to me to be more of a political force than anything else. I don’t think any technology can be effective in that regard. As it stands now I feel that the harms of IPFS outweigh the benefits, and the harms are not even necessary.
I’ve discussed these issues with the IPFS community. The response has been a general washing-of-hands related to the moral dimension of IPFS technology. I personally find this indefensible and hope that there will be a reevaluation going forward. Years ago I was inspired by Phillip Rogaway, a well-known cryptographer, when he published an article on the moral character of cryptographic work. I wrote about his work back in 2016. My blog piece is here and it has links to his work:
https://info.townsendsecurity.com/phillip-rogaway-said-something-important
I would recommend his commentary to any software developer or engineer. And Phillip Rogaway is not the only technologist who has written about CS and ethics. He was just the first to impact my thinking on the subject, and I am grateful for his work.
In regards to SQL databases: I don’t have these issues with relational and no-SQL databases for what should be obvious reasons. I am a happy SQL developer. Any crankiness I have with SQL has nothing to do with the issues above.
I am happy to be corrected if I am wrong about IPFS or any of the points above.
#Web3 #Web30 #IPFS #Cryptography #Ethics -
My difficulty with IPFS specifically has to do with some of its unique characteristics as a storage mechanism, the primary characteristic being the inability to modify or delete content. This is not a side effect of the cryptographic methods used, nor of some limitation in software engineering. This is a specific design goal of IPFS and IPFS is unique in this regard even among major storage technologies like hard drives used in personal computers and servers, cloud storage technologies (AWS S3, Google Cloud Storage, Azure Blob Storage, etc.) and commercial storage offerings like Dropbox, iDrive and others.
What harms follow from this type of implementation? Here are two:
Clearly illegal and harmful content can be permanently stored on IPFS. I am thinking of CSAM, malware, defamatory content, and other harmful content. This type of content cannot be deleted or moderated by the core IPFS technology. This is not a theoretical issue as there are known cases of harmful content on IPFS. Harmful content can be deleted from a relational database, not so with IPFS.
The second issue is that I think IPFS goes a long way towards depriving citizens of their data rights under the EU GDPR and California CCPA and CPRA. These regulations brought forward by democratic governments express the rights of citizens related to the ownership of their private information. Under these regulations (and others) an individual has the right to be forgotten (right of deletion), right to know and control who their personal data is shared with, the right to correct erroneous information, and so forth. To me it appears that IPFS intentionally prevents the exercise of these rights.
I don’t deny that there are positive aspects of IPFS. Where else would we store our precious NFTs? Just kidding. I can definitely see some benefits of a decentralized and distributed storage mechanism. I don’t see that IPFS or other decentralized technology prevents censorship in any meaningful way – censorship appears to me to be more of a political force than anything else. I don’t think any technology can be effective in that regard. As it stands now I feel that the harms of IPFS outweigh the benefits, and the harms are not even necessary.
I’ve discussed these issues with the IPFS community. The response has been a general washing-of-hands related to the moral dimension of IPFS technology. I personally find this indefensible and hope that there will be a reevaluation going forward. Years ago I was inspired by Phillip Rogaway, a well-known cryptographer, when he published an article on the moral character of cryptographic work. I wrote about his work back in 2016. My blog piece is here and it has links to his work:
https://info.townsendsecurity.com/phillip-rogaway-said-something-important
I would recommend his commentary to any software developer or engineer. And Phillip Rogaway is not the only technologist who has written about CS and ethics. He was just the first to impact my thinking on the subject, and I am grateful for his work.
In regards to SQL databases: I don’t have these issues with relational and no-SQL databases for what should be obvious reasons. I am a happy SQL developer. Any crankiness I have with SQL has nothing to do with the issues above.
I am happy to be corrected if I am wrong about IPFS or any of the points above.
#Web3 #Web30 #IPFS #Cryptography #Ethics -
Copypasting from the birdsite:
My recommendation this year is to pay attention to Manifest V3, and look for a way to use less Google products. Don't use any #Chromium based browser (Google Chrome, Brave, Opera GX, etc.) and switch to #Firefox. Use a better email client like Proton Mail and use #Gmail as an ad spam dump; take a day to replace all your email accounts from different sites.
For browsing, despite of getting caught sharing information with #Microsoft, #DuckDuckGo is still the better option for now.
There are alternatives out there to replace google products, you just have to search for them. Use any google thing as a last resort. Don't let #Google pull their Web 3.0 bullshit onto you in the name of Security. Manifest V3 is gonna destroy what it was left of the good internet just to push more and more ADs.
Don't let them win when you have the chance to stop them.
#web10 #web30 #manifestv3 -
Copypasting from the birdsite:
My recommendation this year is to pay attention to Manifest V3, and look for a way to use less Google products. Don't use any #Chromium based browser (Google Chrome, Brave, Opera GX, etc.) and switch to #Firefox. Use a better email client like Proton Mail and use #Gmail as an ad spam dump; take a day to replace all your email accounts from different sites.
For browsing, despite of getting caught sharing information with #Microsoft, #DuckDuckGo is still the better option for now.
There are alternatives out there to replace google products, you just have to search for them. Use any google thing as a last resort. Don't let #Google pull their Web 3.0 bullshit onto you in the name of Security. Manifest V3 is gonna destroy what it was left of the good internet just to push more and more ADs.
Don't let them win when you have the chance to stop them.
#web10 #web30 #manifestv3 -
Copypasting from the birdsite:
My recommendation this year is to pay attention to Manifest V3, and look for a way to use less Google products. Don't use any #Chromium based browser (Google Chrome, Brave, Opera GX, etc.) and switch to #Firefox. Use a better email client like Proton Mail and use #Gmail as an ad spam dump; take a day to replace all your email accounts from different sites.
For browsing, despite of getting caught sharing information with #Microsoft, #DuckDuckGo is still the better option for now.
There are alternatives out there to replace google products, you just have to search for them. Use any google thing as a last resort. Don't let #Google pull their Web 3.0 bullshit onto you in the name of Security. Manifest V3 is gonna destroy what it was left of the good internet just to push more and more ADs.
Don't let them win when you have the chance to stop them.
#web10 #web30 #manifestv3 -
I’m sorry, I designed this poison and there is no antidote. But take it anyway…
- IPFS
I started my security journey by getting pushed into it kicking and screaming. Really. We built a managed FTP solution that was popular. Midsize and Enterprise customers liked it. Then this internet thing took off. Those customers suddenly realized that they were pushing a lot of sensitive data over the internet in the clear. So, they pounded on our door and we agreed, with Phil Zimmerman’s encouragement, to add PGP file encryption to our managed FTP solution. Then we did some database encryption. Then we got pushed onto multiple operating systems. Then, oh crap, we realized we needed to get serious about encryption and key management. So, we did. And we developed some other solutions with encryption for data privacy.
Along the way a friend got interested in blockchain. That looked interesting, it has cryptography! And Merkle trees! Wow, that was awesome. But stuff you posted to the blockchain ledger was in the clear. So, we developed an application for encryption and key management for Ethereum. That did not become a product. That’s a story for another day.
Some years later I discovered the InterPlanetary File System, or IPFS, developed by Protocol Labs. It also has cryptography and Merkle trees (Merkle DAG, actually)! It’s distributed and decentralized. Cool! Said the idiot who never learns a lesson the first time. This led to a managed file system application design based on IPFS, then the addition of encryption and key management, then secure and reliable messaging, then a patent filing, then learning enough go language programming to be seriously dangerous, and some other scratching and pecking. What could go wrong?
This: Once you store a file on IPFS you can never delete it.
That’s a feature, not a bug. The IPFS designers made it this way on purpose. There is literally no way to delete a file from IPFS and its thousands of nodes. This is not because of some limitation in the programming language, or in some limitation of cryptography or of the Merkle tree architecture, or in some inherent aspect of distributed systems architecture. No, this is by design.
Imagine a system that publicly stores files without a delete function and what it implies:
- No way to delete CSAM material.
- No way to delete or inhibit any type of defamatory or abusive content.
- No way to combat doxing and abuse.
- No way to comply with GDPR and CPRA right to know/change/delete/opt-out.
- No way to moderate users or content.
This is just a partial list of problems. No one is accountable, everyone is complicit. It doesn’t get any better from there.
I’ve heard the arguments about this technology helping to prevent censorship. I understand the application and network architecture, and this is just BS, in my opinion. This is toxic technology in the extreme.
I believe that if you create technology that clearly produces irreversible harm, you should bear some responsibility and accountability for that. As technologists we can’t avoid that there is a moral dimension to our work. We should own that aspect of what we do, and operate as compassionate human beings. Personally, I think the harms of IPFS in its current form far outweigh any potential benefits. Until the technology changes it should be avoided. I certainly won’t have anything to do with it.
Mastodon is far from perfect, but it empowers instance administrators and individual users to curate and moderate their own experience. A user can be blocked, and posts can be deleted. Toxic instances can be blocked and defederated. Could it be better? Yes, I think so. But we can already see and personally experience emotionally healthy and life-affirming communities, like this one at infosec.exchange.
This is the way.
#Web3 #Web30 #IPFS #FIL #Mastodon -
I’m sorry, I designed this poison and there is no antidote. But take it anyway…
- IPFS
I started my security journey by getting pushed into it kicking and screaming. Really. We built a managed FTP solution that was popular. Midsize and Enterprise customers liked it. Then this internet thing took off. Those customers suddenly realized that they were pushing a lot of sensitive data over the internet in the clear. So, they pounded on our door and we agreed, with Phil Zimmerman’s encouragement, to add PGP file encryption to our managed FTP solution. Then we did some database encryption. Then we got pushed onto multiple operating systems. Then, oh crap, we realized we needed to get serious about encryption and key management. So, we did. And we developed some other solutions with encryption for data privacy.
Along the way a friend got interested in blockchain. That looked interesting, it has cryptography! And Merkle trees! Wow, that was awesome. But stuff you posted to the blockchain ledger was in the clear. So, we developed an application for encryption and key management for Ethereum. That did not become a product. That’s a story for another day.
Some years later I discovered the InterPlanetary File System, or IPFS, developed by Protocol Labs. It also has cryptography and Merkle trees (Merkle DAG, actually)! It’s distributed and decentralized. Cool! Said the idiot who never learns a lesson the first time. This led to a managed file system application design based on IPFS, then the addition of encryption and key management, then secure and reliable messaging, then a patent filing, then learning enough go language programming to be seriously dangerous, and some other scratching and pecking. What could go wrong?
This: Once you store a file on IPFS you can never delete it.
That’s a feature, not a bug. The IPFS designers made it this way on purpose. There is literally no way to delete a file from IPFS and its thousands of nodes. This is not because of some limitation in the programming language, or in some limitation of cryptography or of the Merkle tree architecture, or in some inherent aspect of distributed systems architecture. No, this is by design.
Imagine a system that publicly stores files without a delete function and what it implies:
- No way to delete CSAM material.
- No way to delete or inhibit any type of defamatory or abusive content.
- No way to combat doxing and abuse.
- No way to comply with GDPR and CPRA right to know/change/delete/opt-out.
- No way to moderate users or content.
This is just a partial list of problems. No one is accountable, everyone is complicit. It doesn’t get any better from there.
I’ve heard the arguments about this technology helping to prevent censorship. I understand the application and network architecture, and this is just BS, in my opinion. This is toxic technology in the extreme.
I believe that if you create technology that clearly produces irreversible harm, you should bear some responsibility and accountability for that. As technologists we can’t avoid that there is a moral dimension to our work. We should own that aspect of what we do, and operate as compassionate human beings. Personally, I think the harms of IPFS in its current form far outweigh any potential benefits. Until the technology changes it should be avoided. I certainly won’t have anything to do with it.
Mastodon is far from perfect, but it empowers instance administrators and individual users to curate and moderate their own experience. A user can be blocked, and posts can be deleted. Toxic instances can be blocked and defederated. Could it be better? Yes, I think so. But we can already see and personally experience emotionally healthy and life-affirming communities, like this one at infosec.exchange.
This is the way.
#Web3 #Web30 #IPFS #FIL #Mastodon -
I’m sorry, I designed this poison and there is no antidote. But take it anyway…
- IPFS
I started my security journey by getting pushed into it kicking and screaming. Really. We built a managed FTP solution that was popular. Midsize and Enterprise customers liked it. Then this internet thing took off. Those customers suddenly realized that they were pushing a lot of sensitive data over the internet in the clear. So, they pounded on our door and we agreed, with Phil Zimmerman’s encouragement, to add PGP file encryption to our managed FTP solution. Then we did some database encryption. Then we got pushed onto multiple operating systems. Then, oh crap, we realized we needed to get serious about encryption and key management. So, we did. And we developed some other solutions with encryption for data privacy.
Along the way a friend got interested in blockchain. That looked interesting, it has cryptography! And Merkle trees! Wow, that was awesome. But stuff you posted to the blockchain ledger was in the clear. So, we developed an application for encryption and key management for Ethereum. That did not become a product. That’s a story for another day.
Some years later I discovered the InterPlanetary File System, or IPFS, developed by Protocol Labs. It also has cryptography and Merkle trees (Merkle DAG, actually)! It’s distributed and decentralized. Cool! Said the idiot who never learns a lesson the first time. This led to a managed file system application design based on IPFS, then the addition of encryption and key management, then secure and reliable messaging, then a patent filing, then learning enough go language programming to be seriously dangerous, and some other scratching and pecking. What could go wrong?
This: Once you store a file on IPFS you can never delete it.
That’s a feature, not a bug. The IPFS designers made it this way on purpose. There is literally no way to delete a file from IPFS and its thousands of nodes. This is not because of some limitation in the programming language, or in some limitation of cryptography or of the Merkle tree architecture, or in some inherent aspect of distributed systems architecture. No, this is by design.
Imagine a system that publicly stores files without a delete function and what it implies:
- No way to delete CSAM material.
- No way to delete or inhibit any type of defamatory or abusive content.
- No way to combat doxing and abuse.
- No way to comply with GDPR and CPRA right to know/change/delete/opt-out.
- No way to moderate users or content.
This is just a partial list of problems. No one is accountable, everyone is complicit. It doesn’t get any better from there.
I’ve heard the arguments about this technology helping to prevent censorship. I understand the application and network architecture, and this is just BS, in my opinion. This is toxic technology in the extreme.
I believe that if you create technology that clearly produces irreversible harm, you should bear some responsibility and accountability for that. As technologists we can’t avoid that there is a moral dimension to our work. We should own that aspect of what we do, and operate as compassionate human beings. Personally, I think the harms of IPFS in its current form far outweigh any potential benefits. Until the technology changes it should be avoided. I certainly won’t have anything to do with it.
Mastodon is far from perfect, but it empowers instance administrators and individual users to curate and moderate their own experience. A user can be blocked, and posts can be deleted. Toxic instances can be blocked and defederated. Could it be better? Yes, I think so. But we can already see and personally experience emotionally healthy and life-affirming communities, like this one at infosec.exchange.
This is the way.
#Web3 #Web30 #IPFS #FIL #Mastodon -
I’m sorry, I designed this poison and there is no antidote. But take it anyway…
- IPFS
I started my security journey by getting pushed into it kicking and screaming. Really. We built a managed FTP solution that was popular. Midsize and Enterprise customers liked it. Then this internet thing took off. Those customers suddenly realized that they were pushing a lot of sensitive data over the internet in the clear. So, they pounded on our door and we agreed, with Phil Zimmerman’s encouragement, to add PGP file encryption to our managed FTP solution. Then we did some database encryption. Then we got pushed onto multiple operating systems. Then, oh crap, we realized we needed to get serious about encryption and key management. So, we did. And we developed some other solutions with encryption for data privacy.
Along the way a friend got interested in blockchain. That looked interesting, it has cryptography! And Merkle trees! Wow, that was awesome. But stuff you posted to the blockchain ledger was in the clear. So, we developed an application for encryption and key management for Ethereum. That did not become a product. That’s a story for another day.
Some years later I discovered the InterPlanetary File System, or IPFS, developed by Protocol Labs. It also has cryptography and Merkle trees (Merkle DAG, actually)! It’s distributed and decentralized. Cool! Said the idiot who never learns a lesson the first time. This led to a managed file system application design based on IPFS, then the addition of encryption and key management, then secure and reliable messaging, then a patent filing, then learning enough go language programming to be seriously dangerous, and some other scratching and pecking. What could go wrong?
This: Once you store a file on IPFS you can never delete it.
That’s a feature, not a bug. The IPFS designers made it this way on purpose. There is literally no way to delete a file from IPFS and its thousands of nodes. This is not because of some limitation in the programming language, or in some limitation of cryptography or of the Merkle tree architecture, or in some inherent aspect of distributed systems architecture. No, this is by design.
Imagine a system that publicly stores files without a delete function and what it implies:
- No way to delete CSAM material.
- No way to delete or inhibit any type of defamatory or abusive content.
- No way to combat doxing and abuse.
- No way to comply with GDPR and CPRA right to know/change/delete/opt-out.
- No way to moderate users or content.
This is just a partial list of problems. No one is accountable, everyone is complicit. It doesn’t get any better from there.
I’ve heard the arguments about this technology helping to prevent censorship. I understand the application and network architecture, and this is just BS, in my opinion. This is toxic technology in the extreme.
I believe that if you create technology that clearly produces irreversible harm, you should bear some responsibility and accountability for that. As technologists we can’t avoid that there is a moral dimension to our work. We should own that aspect of what we do, and operate as compassionate human beings. Personally, I think the harms of IPFS in its current form far outweigh any potential benefits. Until the technology changes it should be avoided. I certainly won’t have anything to do with it.
Mastodon is far from perfect, but it empowers instance administrators and individual users to curate and moderate their own experience. A user can be blocked, and posts can be deleted. Toxic instances can be blocked and defederated. Could it be better? Yes, I think so. But we can already see and personally experience emotionally healthy and life-affirming communities, like this one at infosec.exchange.
This is the way.
#Web3 #Web30 #IPFS #FIL #Mastodon -
Latest update: 2023-05-18
🕸️ “The Federated #SNS Timeline” (#Fediverse history). Key events in the #history of federated #socialnetworks.
Q: Who first coined the “fediverse”?
Q: What was the first fediverse #protocol?
Git: https://codeberg.org/ddfon/federated-sns
👉🏾 https://im.youronly.one/techmagus/kb/ddfon/federated-social-network-timeline-2022346/
I hope this consolidated timeline is useful for the community, and writers.
Enjoy! ^_^
#CCBYSA 4.0 International
---
#FederatedWeb #SocialWeb #Federation #Web3 #Web30 #YourOnlyOne #Misskey #Friendica #Pleroma #Hubzilla #Mastodon #diaspora #ActivityPub #MycelialNetwork #MyceliumNetwork #Mycelial #Mycelium -
Latest update: 2023-05-18
🕸️ “The Federated #SNS Timeline” (#Fediverse history). Key events in the #history of federated #socialnetworks.
Q: Who first coined the “fediverse”?
Q: What was the first fediverse #protocol?
Git: https://codeberg.org/ddfon/federated-sns
👉🏾 https://im.youronly.one/techmagus/kb/ddfon/federated-social-network-timeline-2022346/
I hope this consolidated timeline is useful for the community, and writers.
Enjoy! ^_^
#CCBYSA 4.0 International
---
#FederatedWeb #SocialWeb #Federation #Web3 #Web30 #YourOnlyOne #Misskey #Friendica #Pleroma #Hubzilla #Mastodon #diaspora #ActivityPub #MycelialNetwork #MyceliumNetwork #Mycelial #Mycelium -
Latest update: 2023-05-18
🕸️ “The Federated #SNS Timeline” (#Fediverse history). Key events in the #history of federated #socialnetworks.
Q: Who first coined the “fediverse”?
Q: What was the first fediverse #protocol?
Git: https://codeberg.org/ddfon/federated-sns
👉🏾 https://im.youronly.one/techmagus/kb/ddfon/federated-social-network-timeline-2022346/
I hope this consolidated timeline is useful for the community, and writers.
Enjoy! ^_^
#CCBYSA 4.0 International
---
#FederatedWeb #SocialWeb #Federation #Web3 #Web30 #YourOnlyOne #Misskey #Friendica #Pleroma #Hubzilla #Mastodon #diaspora #ActivityPub #MycelialNetwork #MyceliumNetwork #Mycelial #Mycelium -
Latest update: 2023-05-18
🕸️ “The Federated #SNS Timeline” (#Fediverse history). Key events in the #history of federated #socialnetworks.
Q: Who first coined the “fediverse”?
Q: What was the first fediverse #protocol?
Git: https://codeberg.org/ddfon/federated-sns
👉🏾 https://im.youronly.one/techmagus/kb/ddfon/federated-social-network-timeline-2022346/
I hope this consolidated timeline is useful for the community, and writers.
Enjoy! ^_^
#CCBYSA 4.0 International
---
#FederatedWeb #SocialWeb #Federation #Web3 #Web30 #YourOnlyOne #Misskey #Friendica #Pleroma #Hubzilla #Mastodon #diaspora #ActivityPub #MycelialNetwork #MyceliumNetwork #Mycelial #Mycelium
