3 ms·

> "had their nephew throw up a wordpress site instead of hiring a professional" The web is supposed to be accessible to everyone. This type of "blame the vict

> "had their nephew throw up a wordpress site instead of hiring a professional" The web is supposed to be accessible to everyone. This type of "blame the victim" attitude is a poor way to handle criminal activity.

charcircuit 5y ago
and anyone can hire me to design them a website.
pixl97 5y ago
There are plenty of places that you can go to on this planet with little to no law enforcement. Don't be surprised if you end up dead there. Handling global crime is very difficult.
jiggawatts 5y ago
If they had used static content, it would remain 100% accessible to them, but also vastly more secure. Dynamic content generation on the fly for a blog is unnecessary complexity that invites attacks.
- jiggunjer 5y ago
  wouldn't that preclude a few popular features like a rich text editor?
  - jiggawatts 5y ago
    You can have a separate system, even a locally running desktop app do that. You can still have a database, complex HTML templating, and image resizing! You just do it offline as a preprocessing step instead of online dynamically for each page view. Unfortunately, this approach never took off, even though it scales trivially to enormous sites and traffic levels. I recently tried to optimise a CMS system where it was streaming photos from the database to the web tier, which then resized it and even optimised it on the fly. Even with caching, the overheads were just obscene. Over a 100 cores could barely push out 200 Mbps of content. Meanwhile a single-core VM can easily do 1 Gbps of static content!
  - vbezhenar 5y ago
    I thought about "serverless" blog. Here's some rough scheme I came up with (I never implemented it, though): 1. Use github pages to serve content. 2. Use github login to authenticate using just JS. 3. Use JS to implement rich text editor and other edit features. 4. When you're done with editing, your browser creates a commit and pushes it using GitHub API. 5. GitHub rebuilds your website and few seconds later your website reflects the changes. JavaScript with localStorage can reflect the changes instantly to improve editor experience. 6. Comments could be implemented with fork/push request. Of course that implies that your users are registered on GitHub, so may not be appropriate for every blog. Or just use external commenting system.
    - mkotowski 5y ago
      So, essentially a site generated with Jekyll, hosted on GitHub Pages with Utterances [0] for comments and updated with GitHub Actions. I don’t know if https://github.dev https://github.dev version of Visual Studio Code supports extensions/plugins, but if so, then there is also a rich text editor for markdown ready. All that’s left would be an instant refresh for editing. [0]: https://utteranc.es https://utteranc.es
    - pc86 5y ago
      If this is a serious suggestion (I really hope it isn't), you have never met the kind of person setting up the blogs the GP is talking about.
- pc86 5y ago
  Static content is definitively not as accessible to the typical person asking their nephew to put up a WP blog on shared GoDaddy hosting.
deleted 5y ago
[deleted]

charcircuit 5y ago

and anyone can hire me to design them a website.

pixl97 5y ago

There are plenty of places that you can go to on this planet with little to no law enforcement. Don't be surprised if you end up dead there. Handling global crime is very difficult.

jiggawatts 5y ago

If they had used static content, it would remain 100% accessible to them, but also vastly more secure. Dynamic content generation on the fly for a blog is unnecessary complexity that invites attacks.

jiggunjer 5y ago
wouldn't that preclude a few popular features like a rich text editor?
- jiggawatts 5y ago
  You can have a separate system, even a locally running desktop app do that. You can still have a database, complex HTML templating, and image resizing! You just do it offline as a preprocessing step instead of online dynamically for each page view. Unfortunately, this approach never took off, even though it scales trivially to enormous sites and traffic levels. I recently tried to optimise a CMS system where it was streaming photos from the database to the web tier, which then resized it and even optimised it on the fly. Even with caching, the overheads were just obscene. Over a 100 cores could barely push out 200 Mbps of content. Meanwhile a single-core VM can easily do 1 Gbps of static content!
- vbezhenar 5y ago
  I thought about "serverless" blog. Here's some rough scheme I came up with (I never implemented it, though): 1. Use github pages to serve content. 2. Use github login to authenticate using just JS. 3. Use JS to implement rich text editor and other edit features. 4. When you're done with editing, your browser creates a commit and pushes it using GitHub API. 5. GitHub rebuilds your website and few seconds later your website reflects the changes. JavaScript with localStorage can reflect the changes instantly to improve editor experience. 6. Comments could be implemented with fork/push request. Of course that implies that your users are registered on GitHub, so may not be appropriate for every blog. Or just use external commenting system.
  - mkotowski 5y ago
    So, essentially a site generated with Jekyll, hosted on GitHub Pages with Utterances [0] for comments and updated with GitHub Actions. I don’t know if https://github.dev https://github.dev version of Visual Studio Code supports extensions/plugins, but if so, then there is also a rich text editor for markdown ready. All that’s left would be an instant refresh for editing. [0]: https://utteranc.es https://utteranc.es
  - pc86 5y ago
    If this is a serious suggestion (I really hope it isn't), you have never met the kind of person setting up the blogs the GP is talking about.
pc86 5y ago
Static content is definitively not as accessible to the typical person asking their nephew to put up a WP blog on shared GoDaddy hosting.

deleted 5y ago

[deleted]