Currently I use Fastmail to host my own domain, and then for every new service I save the account in 1Password using [email protected]

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 active.

I'd love it if OnePassword integrated with something like https://randomuser.me to generate a new profile for every awful service that needs an account to work.

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); // const { data } = await axios.get( // 'https://randomuser.me/api/?results=10' // ); // console.log(data); // setUsers(data.results); // } catch (error) { // console.log(error); // } finally { // setIsLoading(false); // } // }; // getUsers(); // }, []); const handleClick = async () => { try { setIsLoading(true); const { data } = await axios.get('https://randomuser.me/api/?results=10'); console.log(data); setUsers(data.results); } catch (error) { console.log(error); } finally { setIsLoading(false); } }; return (

{title}

Show Users {isLoading &&

Loading...

}

{users.map(({ login, name, email }) => { return ; })}

); }; export default App;

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))

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

randomuser.me

Random User Generator

💥 𝐑𝐚𝐧𝐝𝐨𝐦 𝐔𝐬𝐞𝐫 𝐃𝐚𝐭𝐚 🔗 https://randomuser.me/

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:

export default function ChannelListBottomBar(): JSX.Element { const { client } = useChatContext(); const [micActive, setMicActive] = useState(false); const [audioActive, setAudioActive] = useState(false); return (

{client.user?.image && (

div> )}

{client.user?.name} span> {client.user?.online ? 'Online' : 'Offline'} span> p> button>

setMicActive((currentValue) => !currentValue)} > button> setAudioActive((currentValue) => !currentValue)} > button> button> div> ); }

I wonder if we will ever get a realism model which can produce normal faces like https://thispersondoesnotexist.com instead of like super symmetrical faces of models

this has been in circulation since a while AI images took off, and they certainly weren't convincing before they did. You know the old "try to name one thing in this image" macro? Pretty sure that was AI generated, there was also thispersondoesnotexist.com which was always pretty good but of course it is

Not the workflow for these images, but if you easily want to spice up your gens with a bit more natural look, try using images from thispersondoesnotexist.com with IPAdapter face model.

...then they just use the app on generated images of not real people (potentially based on specific inputs to remind you of a real person).

Also we can generate very realistic faces with AI, https://thispersondoesnotexist.com/ (old example), fully 3D faces are doable at this point. So in another 5-10 years a low profile model like him wouldn't even be hired for this, they would just generate a digital face model. Unionizing will only speed up studios adoption of digital replacements.

It looks like they all use a profile picture made with https://thispersondoesnotexist.com/