Pappa Pug

2K posts

Pappa Pug banner
Pappa Pug

Pappa Pug

@PappaPug

Security Researcher Friend, Advocate & Community Activator Host of The Island 🌺 🏝️ 🕹️ also working on web3 auditing indie game! prev @immunefi

Death City Katılım Temmuz 2023
1.2K Takip Edilen1.2K Takipçiler
Sabitlenmiş Tweet
Pappa Pug
Pappa Pug@PappaPug·
it took way too much effort to do but - it's done. The Class Photo. I just wanted to say thanks to all 106 of you who participated. Even the ones not in this photo or got eliminated in week 1. You were fully a part of the event whether in spirit or in action. Even if you're not seen in this photo, just know that you are still in it. I had such a great time hosting this and just unleashing full creativity with all the random things we were doing. It was absolutely unspeakable the level of improv and back and forth you guys did with me and the things I made. It's been an incredible 8 weeks. I certainly hope we can see all of you back for the next one, but in the meantime, I really hope you all had a great time and that you can look back with fond memories. That's what I wanted to do with the yearbook - leave everyone with fond memories (though I'm sorry I couldn't make a profile page for every single player, I really wished I could. I love you all.) Thank you for playing #ImmunefiIsland Season 2 ❤️ - Pappa Pug 🐶
Pappa Pug tweet media
English
2
10
49
5.5K
Pappa Pug
Pappa Pug@PappaPug·
Dear whitehat frens.. I miss you guys! If you're free, do drop me a DM or a reply. Thanks again for always being here for this pup.🐶 You are some of the kindest and most generous people on the planet. 🌍❤️
English
2
0
26
638
Pappa Pug
Pappa Pug@PappaPug·
Looking for solo-dev projects that need a one week trial of growth + distribution. Let me work my magic paws for a week! 🐾 If you like working with me, we can do a fixed monthly rate!
English
0
0
5
313
Pappa Pug
Pappa Pug@PappaPug·
@arjunnchand @jumperapp I've put my hat in the ring! 🐾 Looking for the next opportunity to run another kickass community... And another virtual survivor gameshow 😉
English
0
0
0
137
Arjun Chand
Arjun Chand@arjunnchand·
We’re hiring for marketing at @jumperapp. Jumper is heading into one of the biggest periods in its history, with major launches and community initiatives over the coming quarters. We’re looking for high agency individual to join the core marketing team. You'd be owning the voice of Jumper on socials, so you must know the ins and outs of what makes the X algoritm tick. Overall, you'd work across comms, GTM, launches, and whatever else it takes to get great products into the hands of users. If you’re someone who wants to work on high impact things, in a remote-first team that merits people who can take ownership, work autonomously and add to the overall output and quality of the work we do - this is the perfect opportunity. DMs are open. Just send me a message with your best work (could be a single post or an entire campaign) and go into as much detail as possible to explain would you did to bring it to life. The next chapter of Jumper is going to be a big one, and you’d be helping write it.
English
112
20
481
51K
Pappa Pug retweetledi
100proof.org
100proof.org@1_00_proof·
A two-part story (in images).
100proof.org tweet media100proof.org tweet media
English
9
12
98
13.5K
Pappa Pug retweetledi
angel
angel@angeldot_·
> El CEO de OpenAI admite que la IA no causará el apocalipsis de empleo que predijo > Uber no encuentra un retorno que justifique sustituir humanos por IA > Starbucks elimina la IA de su sistema por fallos constantes > Microsoft retira Claude Code a sus ingenieros por no ver mejora en costes NATURE IS HEALING
Polymarket@Polymarket

JUST IN: Sam Altman says AI probably won’t trigger the “jobs apocalypse” he once predicted.

Español
142
869
7.7K
691.7K
Pappa Pug retweetledi
Matt Popovich
Matt Popovich@mpopv·
the top right corner of vscode is starting to resemble an iq test
Matt Popovich tweet media
English
162
1.3K
26.9K
564.4K
Pappa Pug retweetledi
bartek.eth
bartek.eth@bkiepuszewski·
The original MakerDAO code written in "daiwanese" is still one of the most underappreciated SE feasts in Web3. It's the opposite of current code slop with hundreds of unnecessary libraries and object hierarchies. Complicated code = more surface to exploit Study daiwanese. Minimize your code. Learn FV. The future is opposite to current slop practices
English
5
7
96
6.5K
Pappa Pug
Pappa Pug@PappaPug·
SR Life Simulator is still in development... I just had to find a way to pay the bills in the meantime. My dream of becoming an indie dev is still in progress, but at least I'll be able to take care of my family for now.
English
1
0
7
323
Pappa Pug
Pappa Pug@PappaPug·
LIFE UPDATE! I've been praying and looking for the right opportunity these last 6 months... And almost miraculously it appeared just two days ago, when I was invited to join a walk-in interview. It was a two-stage interview, and there were loads of people overflowing the lobby of the office. Out of the hundreds of nervous people there, I somehow felt strangely calm. And before long my name was called. Instead of going through the stages, I was brought straight to the final interview room to face the hiring manager. And praise God, I was accepted within that same interview. I was able to go home immediately. "See you Monday", they said. My name wasn't even on the list at first... I didn't know anything about the position or project when I walked in. But when I heard the hiring manager speak I knew it was the right project for me. Reconnecting with my hospitality roots with white glove service. I'm sure these next three months will be extremely interesting. Thank you Lord Jesus. 🕊️ Hallelujah.
English
11
2
62
3.2K
Pappa Pug retweetledi
brainiac5
brainiac5@shealtielanzz·
Notice how hacks increased as contests died off. You can say AI but there’s a bunch of Whitehats involved in these hacks. You onboard lots of them then you take their jobs away.
English
10
9
131
13.7K
Pappa Pug retweetledi
Adrian ⛩️ Hetman 🐺 | 📓+🖋️+☕️
There's a legitimate frustration buried in that take, but it rests on a misread of why BBP platforms exist. A bug bounty program is not a contact form. It's a contract. The platform is what makes that contract enforceable on both sides. Projects get filtered signal and predictable triage. Researchers get clear rules, payout SLAs, dispute resolution, and a record of work that compounds into reputation. Other responsible disclosure routes exist for the urgent stuff, SEAL 911 being the obvious one, but the premise sits in the same place. Structure exists so serious work can get through. The "just send details over email" model sounds lightweight until you sit on the receiving side. I triaged thousands of reports running MTS at Immunefi. The cost asymmetry is brutal. A researcher can write a scary-sounding critical report in 15 minutes. Invalidating it takes a senior engineer 1 to 2 hours on average. Sometimes more. Small and medium teams don't have that headcount. The big ones already outsource it. With hacks happening almost daily, projects should be taking security more seriously, and many are. But it remains a genuinely hard problem. BBPs catch what a researcher can find externally on the same surface as an attacker. They don't and can't cover everything. A lot of recent damage has been infrastructure failure rather than code bugs, and that surface is hard to fold into a BBP without monthly or quarterly pentests on top. The platform requirement does one more thing that gets missed in these threads. It self-selects for researchers willing to engage with the process. That friction is a feature, not a bug. If signing up for a platform a project explicitly named in their program rules is the dealbreaker, the report was probably not going to clear the bar anyway. Serious researchers maintain accounts on the major platforms because that's where the work is. The AI era raises the floor of all of this. Anyone can prompt a model to produce a coherent-looking critical report with fabricated impact and confident language. Valid work gets buried under that slop, which is precisely what feeds the scepticism. Structured intake, enforceable rules, and reputation on a platform are the only things that hold up at scale. At least for now. So the real question is what intake model actually gets bugs fixed at scale, not whether platforms add friction. The honest answer is managed triage on a platform, with SEAL 911 and similar channels for the cases that can't wait. Teams that skip this either drown in noise or quietly hire someone to handle it.
Essential@only01Essential

Why provide an email for disclosures on github. I report the bug, then reach out to alert you about the severity of the bug, then you send me a link to resubmit the bug via another channel? If you don't have an account with that platform, you'll have to create one, and if maybe you can't due to some restrictions, you're blocked. Seems like too much overhead. Why not just request details? That's what most teams do. When the bug has been confirmed and fixed then we can go that route. Fixing the bug should have been the priority. What if the researcher can't send the report over the platform, they are literally saying if you can't for some reasons, then sorry we are not interested. I don't know if you get my point

English
2
1
8
1.5K
Pappa Pug retweetledi
0K
0K@ZeroK_____·
I never realized how much of this space revolves around marketing companies and AI agents until I learned more about them. Some companies and most “AI agent” guys are just doing pure marketing nonsense, nothing more and nothing less. Meanwhile, blackhats keep showing us what real work looks like by hacking a new project almost every day. So ignore all this nonsense, focus on securing people’s money, improving your skills, and earning good rewards for yourself.
English
6
1
44
1.6K
Pappa Pug retweetledi
Dacian
Dacian@DevDacian·
Future of web3sec: Arms Race - Defensive AIs vs Offensive AIs, with teams of elite humans continually improving them. Protocols that aren't monthly scanning their existing code using continually improving Defensive AIs will fall behind the curve & more likely to be exploited.
English
6
4
76
5.4K