search

letsgetrandy / DICSS

Directly injected CSS
http://letsgetrandy.github.io/DICSS/
MIT License
1.35k stars 72 forks source link

CDN Availability #48

Open enjibby opened 9 years ago

enjibby commented 9 years ago

Has anyone put DICSS somewhere that we can share? We have a large number of clients that would potentially want to use this, but having so many DICSS lying around everywhere would be unnecessary.

zgrep commented 9 years ago

Personally, I believe in sharing of information and data. If people want something, they deserve to have it, or a copy of it. Everybody needs to have their own DICSS to share with others, or at least the opportunity to grow some DICSS to share with others. There is no need for these CDN's of which you speak, they are restrictive, constrictive, strangleative, throat-squeezing, and not made of DICSS or NUTS. DICSS itself is against the very ideals that this so-called CDN technology offers, ideas behind DICSS including throat-expansion and the like.

CDN's offer technology a chance to be monopolized by those who have enough money to flaunt around saying "I've got more DICSS than you!" or "I have a bigger DICSS!" when all they really have is the community variant being served through a CDN. CDN's allow for marketing to make the DICSS decisions and not those who need to use DICSS themselves. CDN's allow for the hiding of DICSS and the manipulation of DICSS until DICSS may no longer even become DICSS. It may turn into Featureless, Losing-Oriented, Pathetic, Pitiful, Yucky DICSS because of the CDN's modifications. And nobody wants that, because it's almost as bad as impotence! (and I apologize for my use of the vulgar word "impotence")

Lastly I would just like to say that users hate when they get their DICSS from the same place, every time. It's annoying to go to a website only to realize "Hey, that's the same DICSS as that other place!". People get tired of the same DICSS and they need variety in their life. So please, I'm begging you, DO NOT TRY TO SHARE DICCS, IT IS UNSANITARY AND COMPLETELY DEVOID OF ANY SANITY.

Thank you.

realJoshByrnes commented 8 years ago

Thank you for the idea. I kept getting error 403 when I tried to use DICCS at home, but when I used a CDN, I ended up with status code 200.

Now, does anyone know of a free CDN I could use? (The one I'm using charges uploads AND downloads!)

enjibby commented 8 years ago

I'm tempted to avoid using free CDNs for access to DICSS. They tend to restrict access to only a small port 80 connection with limited bandwidth, and it's not possible to know what else may be downloaded. Your site could catch anything and you can't see who gave it to you because they're hidden behind some massive firewall! That said, this is the way some people like it, so glory be to them.

realJoshByrnes commented 8 years ago

Ugh. Tried to use a local CDN and now I'm getting error 413. Might try again at home, maybe if I can patch the server with a more recent update, and then push DICSS again.