jb
jb@waf.moe
<p>A Wafrn dev. 17 (please act accordingly), Filipino, he/him/they.</p> <p>Feel free to follow! I don't bite! Note that some people might get a vibe check.</p> <p>I run WAF.moe and sk.WAF.moe! But moderation requests should not be sent here, go to @wafmin@waf.moe for that. Also don't ping me for Wafrn issues (unless needed), go to Wafrn's Codeberg for that.</p> <p>Avatar by <a href="https://waf.moe/fediverse/blog/mups">@mups@waf.moe</a></p> <p> <small>Testimonials:</small><br/> @houl@wetdry.world: who is this jetbrains guy<br/> @kemona_halftau@sharkey.skydevs.me: :neofox_floof:<br/> @gwenbnuuy@waf.moe: bnuuy certified aw yeah!!!!!!!!!!!!!!!!<br/> @crystallinefire@app.wafrn.net: waf ???<br /> @ducky@app.wafrn.net: skeets? no, waffs.<br /> @anubiarts@waf.moe: "waf moe"? what did moe do?<br /
Posts
-
Post #1466981
@days.since.last.npm.supply.chain.attack.by.jbc.lol @dclnpmsca@waf.moe Introducing… Days Since Last NPM Supply Chain Attack! Now posting on @dclnpmsca (ssh about the typo) on fedi and @days.since.last.npm.supply.chain.attack.by.jbc.lol on bsky! now why not bridged using wafrn? I'm glad you asked! it's because on fedi it posts on unlisted rather than public on bsky.
-
Post #1421014
@kestrelcrow@waf.moe Hey wafflers! Me and the rest of the team has decided that due to the stress, internal issues, and other issues, the WAF.moe project is officially shutting down on June 2, 2026 at 12:00 AM (GMT+8). This is not a April fool's joke, nor is it a everyday joke. Even the team doesn't want to do this. We have loved the community and the things we did as a community, from the countless bite wars on early inception of the instance, to the planned debut of Huli, our mascot...