Posts tagged with :bank-hackclub:
"^[A-Za-z0-9_]+[a-zA-Z0-9._%+-]+@[a-zA-Z0-9._-]+\.[a-zA-Z0-9]{2,3}$". notice that last part, which allows for 2 or 3 alphanumeric characters following the last .. you can imagine how that might clash with someone's email.
now, you might be thinking, ced, i know it's tempting to just sidestep their clientside verification, but that's technically circumventing access protocols. that sounds really illegal! and you're totally right, which is why whoever did this probably has HORRIBLE impulse control ...
the second image demonstrates someone putting a break point on the line that actually sends the request and at that point, n in the watch window should be the variable on the left, so that someone will be able to modify the new email to the unvalidated one ...
whoever did this probably discovered a couple useful things about chrome devtools in the process that they weren't already aware of ...
query Users {
users(options:{
sort:{
field:"balance",
order:"DESC"
},
take:5
}) {
id
balance
outgoingTransactions(options:{
sort:{
order:"DESC",
field:"balance"
},
take:2
}) {
id
balance
from {
id
}
to {
id
}
}
}
}
I’m soooooo excited for what all of yall are going to be doing with this—as always, if you’re interested in making a bot, feel free to DM me with the bot’s username to get your very own token! You can find the source for HN over at: :githubparrot: 🌟 z.rishi.cx/g/hn, and the Teller over at z.rishi.cx/g/teller :D
P.S. The next ship will be V1 of HN—the production-ready, stable version of the API with documentation!
