SEEKING WORK | UK | REMOTE | FULL-TIME | PART-TIME
I'm a full-stack developer and contractor proficient in Go, PHP, JavaScript, HTML, and CSS, with over a decade of expertise. Specializing in React, TypeScript, Go and associated technologies for more than six years.
YouTube works fine and has for years. Earlier this year Google started blocking some requests and due to the use of a redirect you often need to create a `New Identity` to get around it. It _usually_ helps if you visit the youtube.com homepage first, though.
There are some 6,000+ relays active so even in the most minimal interpretation of "most" that's ~3,000 short of most. Or subtracting the 8 specified if one considers them trusted that's somewhere around ~3,000 (i.e. it doesn't help you make out anything you couldn't have made out before).
Sorry for the late reply. The HN reply app doesn't seem to notify post replies...
We'd love to know what URL it was. Over the last week we've fixed a number of failures as well as actually report more failures without you having to click the report.
Those scores seem to be one of said failures. Possibly the site redirects away from the original URL - an issue that should be fixed now.
Thanks. It seems that it simply takes too long to load so the profiling hits the timeout limits. We'll investigate more to see if we can improve the situation.
To expand a little: since the tested sites are not actually connected to oya.to, we don't really know what is and isn't part of the site so end up proxying and optimize every request.
Some sites redirect to different domains or paths e.g. m.example.com or example.com/en-gb. Some sites have ads and other scripts that do polling so the page never really finishes loading, etc.
Today I'd like to share with you oyato cloud (aka https://oya.to)
We use Google-recommended[1] dynamic rendering techniques and other best practices to automatically optimize your pages and images on a per-page and per-visitor basis. So you can e.g. have your home-page fully statically rendered and everything else as normal like Netflix does/did.
Your React apps and client-side rendered sites are automatically pre-rendered (like SSR) to guarantee search engine and social-network indexability.
Your images are automatically optimized and resized depending the browser window size and image formats it supports.
Even a static server-rendered site like HN can see Lighthouse score improvements[2] :)
This looks quite impressive, how does it work with dynamic (per user) content? If I have such a vue site for example, do I have to modify anything to get it to work?
The pricing mentions unlimited bandwidth, but limited requests. what counts as a request?
I'm actually running a service that does lighthouse checks (amongst other things) so nice to see more people focussing on making things faster.
You can see the report for your site here, there are some minor issues it found: https://app.pagewatch.dev/b326ab115e9f00bac779d9851d4687a3fa...
> I'm actually running a service that does lighthouse checks (amongst other things) so nice to see more people focussing on making things faster. You can see the report for your site here, there are some minor issues it found:
Thanks! I'm especially impressed with the spelling check. It works even better than Sublime Text's builtin spell-checker :)
The layout issue seem to be not supporting 320w viewports: it's intentional (analytics, etc.). It would be nice, though, if the tool was able to show something like the amount of users who still use certain screen sizes.
The broken link issue looks like a 302 redirect which isn't a broken link.
> This looks quite impressive, how does it work with dynamic (per user) content?
It should work completely transparently. We only render text/html content and like everything else, its keys include cookies so if you send cookies with user-specific content everything should be just fine.
> If I have such a vue site for example, do I have to modify anything to get it to work?
You shouldn't need to do anything. We want the whole process to be:
* Sign up
* Add your site
* Point your DNS at our servers
* Forget about it
Of-course you can add page-specific rules or use the (somewhat hidden) API, but everything apart from the the caching and image optimizations are turned off by default for normal users. Search engines and other bots like social networks get a static version of every page requested by default.
> The pricing mentions unlimited bandwidth, but limited requests. what counts as a request?
A request is any request that hits our servers (html, scripts, images, api requests). Of-course, we also do things like changing src urls where we can to include our own content-hash, so we can tell the browser to cache it for a long time which reduces the number of requests even if your caching headers are set up perfectly.
That would be quite ironic :)
I dont see it though, would you mind pointing it out? Are you talking about spellling, because that one is intentional (and even underlined) to show an example.
As a non-native speaker, I thought the correct form would be "Fast, working pages mean better rankings.", "mean" in singular. I checked it against a grammar app and it said the same, but I see how it could be used in plural for the header, as in "having fast, working pages means...".
> No matter how correct you are, you won't get anywhere by making the other person feel stupid.
I came to the same realization some time after an incident at Uni...
In a Uni class I tried to correct the lecturer about some Unix/Solaris? feature using my Linux knowledge and when he wouldn't agree, I basically ignored everything he taught for the rest of the class.
I think it was maybe something about file systems and IIRC I looked it up after (realizing what a dick I was) and I found that I was indeed correct, but I still feel bad about the way I acted to this day.
Although, in my defense, earlier in the class I had to show a whole bunch of students how to exit Vi/Vim so as you can imagine, I was already starting to feel like some kinda Unix god at that point.
I think both of you failed to learn from each other there. He had an opportunity to learn from you but refused it. For me, every person presents an opportunity to learn, but I maintain a filter for each person because there are varying levels of bullshit and presence of a little knowledge about certain things. I consider it one of my talents that I can quickly and effortlessly gauge these levels for people and discover what it is I can learn from them and what I definitely can't learn from them.
I'm a full-stack developer and contractor proficient in Go, PHP, JavaScript, HTML, and CSS, with over a decade of expertise. Specializing in React, TypeScript, Go and associated technologies for more than six years.
Location: UK
Remote: Yes
Willing to relocate: No
Technologies: React, etc. (8+ years), TypeScript/JavaScript (8+ years), Go/Golang (10+ years)
Résumé/CV: https://1li.dev/resume
Email: hn@1li.dev
Github: https://github.com/amitybell