Web.dev by Google VS Random User Generator

“If the sanitization logic in DOMPurify is buggy, your application might still have a DOM XSS vulnerability. Trusted Types force you to process a value somehow, but don’t yet define what the exact processing rules are, and whether they are safe.” — this caution from web.dev makes me want to play around with TrustedTypes more and get a better understanding. - Source: dev.to / 18 days ago

Before we start creating pages in our application, it's important to understand how Next.js renders content. The framework supports multiple rendering methods including server-side rendering (SSR), static site rendering (SSG), and client-side rendering (CSR). There are many pros and cons to each rendering method (too many to cover in this post) so if these concepts are new to you, Google’s web.dev site has a very... - Source: dev.to / 7 months ago

The lifecycle of an interaction. Source: web.dev. - Source: dev.to / 3 months ago

Probably not, it's the CSS used so far, so if there are elements you've not interacted with, that's an issue. This web.dev article gives some tools you can use https://web.dev/articles/extract-critical-css. Source: 5 months ago

I noticed the same for Google's site https://web.dev/ The last article pushed to the feed was "Changes to the web.dev infrastructure" few months ago https://web.dev/blog/webdev-migration The feed still there but with no updates https://web.dev/feed.xml and on the site you can see new articles published. Is sad that on a infrastructure revamp of a modern site, the RSS feed was left out of the features list (at... - Source: Hacker News / 5 months ago

Currently I use Fastmail to host my own domain, and then for every new service I save the account in 1Password using service@service.mydomain.com It's a bit extreme, but surprisingly little extra effort. That said, most of the accounts I create are throwaway. For phone numbers I have an old, unused Google voice number I give out. It's a real number, but never checked, except for once every 90? days, to keep it... - Source: Hacker News / 2 months ago

Import axios from 'axios'; Import { FC, useState } from 'react'; Import { AppProps, Users } from './App.types'; Import User from './components/User'; Const App: FC = ({ title }) => { const [users, setUsers] = useState([]); const [isLoading, setIsLoading] = useState(false); // useEffect(() => { // const getUsers = async () => { // try { // setIsLoading(true); ... - Source: dev.to / 5 months ago

Fetch("https://randomuser.me/api/") .then(response=>{ if(!response.ok){ throw new Error("Failed") } return response.json() }) .then(data => console.log(data)) .catch(error => alert(error)). - Source: dev.to / 9 months ago

I just released the first version of random_user, a convenient generator of random user. It simply use the great api from https://randomuser.me/, with reqwest. Source: 9 months ago

Hello, I'd like to make a React Native application using the RandomUser API. I want to make a simple app that takes the data from RandomUser and displays it as a list of people to hire for different jobs. On top of the current API, I want to add a property for categories each person will work in. Something like:. Source: over 1 year ago