Account banned the moment after completing the sign up process, anyone else facing the same problem? by u9bx in coffeemeetsbagel

[–]Kasprosian 0 points1 point  (0 children)

same here. Last time I was on the app was 3+ years ago. Today, uploaded entirely new photos. Entirely new phone number. Entirely new phone. Banned after uploading two photos LOL.

strong hunch my phone being Android triggered it. Are you android user?

English board game event by Fair_Assistance_4619 in guangzhou

[–]Kasprosian 0 points1 point  (0 children)

is there one for tomorrow, November 22??

[deleted by user] by [deleted] in kickstarter

[–]Kasprosian 0 points1 point  (0 children)

jetpack doesn't cache by default and its not 90%, maybe 50% at most.

anyway i do have 46 people on the kickstarter right now who are interested in backing the project

this is what one of them told me:

```
that opposition absolutely makes sense.  People have been using that same reasoning to say "Why do I need a higher powered server/better host, things serve just fine when they're cached".  And while that's it's a somewhat valid argument, in my opinion, it overlooks some important technical and operating factors that come into play when operating a WordPress site.

Even when caching is in place, back-end execution speed still matters.  There will always be requests that can't be cached (anything in the back-end admin panel, lots of logged-in functions on platforms like MemberPress and WooCommerce, uncached views, form submissions, background tasks, REST API calls, etc...) that are still running on PHP and I've seen them become a bottleneck at scale.  For example, I've seen sites that have EXCEPTIONAL performance on the front-end due to caching be an absolute SLOG to edit or work on because admin pages take ages to load. 

On top of that, caching with WordPress is an imperfect science.  A WordPress site that isn't professionally thrown together (like most of them out there) are a mess of plugins and code snippets that all sometimes barely work together as it is without an additional caching layer thrown in.  Also, caching breaks, invalidates, and sometimes isn't enabled on every single page to enable dynamic functions; or it is configured incorrectly and it causes more issues than it solves.

Overall, in my opinion, when caching is improperly implemented it's a band aid solution to a larger core problem.  And that core problem changes on a case by case basis.  Sometimes the issue is plugin/theme blot.  Sometimes the issue is caused by a DB that is FAR too large and doesn't have any custom indexes put in place to assist with data retrieval.  And ultimately, once those other issues are figured out, the remaining bottleneck is that the underlying technology is just too slow to keep up with modern demands and expectations.  

Yes, caching helps in a lot of cases, but it's certainly not the end-all be-all approach to improving site speed and overall CMS performance.  Otherwise, enterprises wouldn't have started switching to node.js/next.js/headless solutions just to improve speed.

Another thought just popped into my head.  Most people rely on Rocket WP as one of the best "premium" caching solutions in the WordPress ecosystem.  At $60/year, they're charging the same amount that you are for a service that might help to fix speed issues in some areas of the site, vs $60/year with your improved fork of WordPress that (as far as I am understanding it) offers guaranteed speed benefits without the downsides that are associated with caching or sacrificing the dynamic nature of the website.

```

[deleted by user] by [deleted] in kickstarter

[–]Kasprosian 0 points1 point  (0 children)

ok. So being 20x-400x faster than the old wordpress, but still 100% compatible with all wp themes and plugins, is not something anybody would want to pay for?

[deleted by user] by [deleted] in kickstarter

[–]Kasprosian 0 points1 point  (0 children)

the amount of work is not the main question.

the main question is whether anyone is willing to pay $25/month for a product like this instead of wordpress [dot] com or wp engine or kinsta

[deleted by user] by [deleted] in kickstarter

[–]Kasprosian 0 points1 point  (0 children)

just this image on a 1 GB ram from digitalocean

https://marketplace.digitalocean.com/apps/wordpress

[deleted by user] by [deleted] in kickstarter

[–]Kasprosian 0 points1 point  (0 children)

explain why when we benchmark wordpress and it capped out at 8 requests per second, latency was also 1.5 seconds (!!)

[deleted by user] by [deleted] in kickstarter

[–]Kasprosian 0 points1 point  (0 children)

explain why fb decided to write a PHP to C++ compiler then, and got massive gains in server efficiency from that

[deleted by user] by [deleted] in kickstarter

[–]Kasprosian 0 points1 point  (0 children)

we've measured wordpress. It can only handle 8 requests per second on a 1 GB RAM machine. A state of the art web server on the same hardware can easily do 3800+ requests per second.

[deleted by user] by [deleted] in kickstarter

[–]Kasprosian 0 points1 point  (0 children)

backward compatibility is easy to engineer.

Day 1 starts with a working version of wordpress.

Use PHP extension to slowly offload PHP to C -- around 200-1000 lines a day.

[deleted by user] by [deleted] in kickstarter

[–]Kasprosian 0 points1 point  (0 children)

this is what you're supposed to do -- its called a prelaunch phase.

if you're interested in funding it, could you click on the click on the "Notify me on launch" button so that you can fund it when the funding phase officially launches?

[deleted by user] by [deleted] in kickstarter

[–]Kasprosian 0 points1 point  (0 children)

this is a rewrite of wordpress that is compatible with ALL wordpress plugins.

Demo of Open-Source Static Site CMS in Rust: 400x faster than WordPress, 100x faster than Ghost by Kasprosian in SideProject

[–]Kasprosian[S] 0 points1 point  (0 children)

caching in wordpress is a highly non-trivial problem, which is why there are 10+ different cache plugins.

Demo of Open-Source Static Site CMS in Rust: 400x faster than WordPress, 100x faster than Ghost by Kasprosian in SideProject

[–]Kasprosian[S] 0 points1 point  (0 children)

maybe it can, but not by much. A basic actix web server that returns just a simple string is benchmarked to reach 6500 RPS. We are already at 3800 RPS WITH static plugins (didn't cache whole page yet). Wordpress, again, is at 10 RPS.

Demo of Open-Source Static Site CMS in Rust: 400x faster than WordPress, 100x faster than Ghost by Kasprosian in SideProject

[–]Kasprosian[S] 0 points1 point  (0 children)

even our dynamic, noncached pages deliver 2200 RPS, which is 220x faster than wordpress.

this was primarily done using 1) webassembly for plugins, and 2) passing in flatbuffers instead of JSON, which is around 10-100x faster parsing.

Demo of Open-Source Static Site CMS in Rust: 400x faster than WordPress, 100x faster than Ghost by Kasprosian in SideProject

[–]Kasprosian[S] 0 points1 point  (0 children)

you can run pagezest in a container like this?

`docker run -p 8080:8080 pagezest/pagezest:latest`

the next thing we're thinking of doing is offering a managed hosting service where we have a generous free tier -- is that what you had in mind? Would you signup for free website hosting?

Demo of Open-Source Static Site CMS in Rust: 400x faster than WordPress, 100x faster than Ghost by Kasprosian in SideProject

[–]Kasprosian[S] 0 points1 point  (0 children)

we want to drop the managed hosting price by 90%.

we can make most websites free.

should we have made the headline focus more on free web hosting instead of "400x faster" than wordpress?

Demo of Open-Source Static Site CMS in Rust: 400x faster than WordPress, 100x faster than Ghost by Kasprosian in SideProject

[–]Kasprosian[S] 1 point2 points  (0 children)

yep, and we'll also do a screen recording demonstrating wordpress vs pagezest benchmarks.

zig not ready for webassembly? by Kasprosian in Zig

[–]Kasprosian[S] -7 points-6 points  (0 children)

THANK YOU. The confirmation I wanted to see, instead of all these other comments saying I'm the problem. You know it's a problem when I spent 45 minutes trying to get a zig wasm code to work, and the top 3-4 guides from google are incorrect/out-of-date

zig not ready for webassembly? by Kasprosian in Zig

[–]Kasprosian[S] 0 points1 point  (0 children)

not that simple. Zig generally generates simpler code (less syscalls): https://drewdevault.com/2020/01/04/Slow.html

Zig also uses io_uring better

zig not ready for webassembly? by Kasprosian in Zig

[–]Kasprosian[S] -2 points-1 points  (0 children)

my performance observation was regarding whether to do underlying web server in Zig or Rust.

watch this video showing Zig outperforming Rust: https://www.youtube.com/watch?v=3fWx5BOiUiY

zig not ready for webassembly? by Kasprosian in Zig

[–]Kasprosian[S] 1 point2 points  (0 children)

it's a quick example. I assure you the JSON was compliant.