@atomicpoet
Its not just the domain name of the instance itself that we need to be mindful of but also the #CDN that the server is using for images. Many instances use a seperate CDN.
The instance we are on uses what we understand to be a popular one by #BunnyCDN, namely https://cdn.masto.host.
As a secondary concern such CDN appears to block #Tor. We are again unable to post images again. (@witchescauldron)
1/2
@atomicpoet @witchescauldron @mensrea @gisiger
If a CDN becomes too big the result is a just another #centralisation problem. Again, censorship and suppression at scale in the form of denial of serving content like #images and #videos is possible.
The #TooBigToExist CDN can also begin to gather data on users, for example when they are accessing the content and what content do they tend to look at etc.
The very nature of the #legacyInternet is unworkable. Alternatives like #I2P and Tor exist.
@atomicpoet @witchescauldron @mensrea @gisiger
If a CDN becomes too big the result is a just another #centralisation problem. Again, censorship and suppression at scale in the form of denial of serving content like #images and #videos is possible.
The #TooBigToExist CDN can also begin to gather data on users, for example when they are accessing the content and what content do they tend to look at etc.