←
Cryptosailor32,986 posts
Cryptosailor avatar

Cryptosailor

@robertdavid010

Engineer (Web3), entrepreneur, organizer @500GlobalVC alum #blockchain #occupy since 2011 Tech Alpha stream No investment advice, DYOR

◷ Joined June 2012▧ 2,785 Photos and videos
Cryptosailor avatar
Cryptosailor@robertdavid010·21 Dec 2024

🚨 PRO TIP 🚨 When it comes to blockchain tech there is nothing new about: Open Source Accounting Business Finance Public Orgs Sales & Marketing Thats the irony of the disruption for people in the 'west'. So what IS the disruption!? No more `root user` problem (iykyk)😉

Cryptosailor avatar
Cryptosailor@robertdavid010·Nov 14

The verdict is in: WoW Forever sucks! It all boils down to @Blizzard_Ent nerfing dungeon xp & there is no dungeon grinding for guilds/groups, so they all just are in the open world spawn camping quest NPCs. Levelling is slower than original vanilla. #WoWForever never

Cryptosailor avatar
Cryptosailor@robertdavid010·Nov 12

all is better than trisfal glades, and thats where I had to start as undead pally for horde. experience my pain live on stream! twitch.tv/cyberscholar #WoWForever

mulgore is alright

Cryptosailor avatar
Cryptosailor@robertdavid010·Nov 4

Very interesting conversation with relevance for the whole industry.

Even though I'm clearly biased in favor of freedom, I still asked @CBarraford some hard thorough questions on whether or not THORChain could feasibly block stolen funds. And whether or not it should. Turned into a deep discussion of "why are we even here to begin with?"

1:19:16
Cryptosailor avatar
Cryptosailor@robertdavid010·Nov 4

Oh, and I also did a personal side project for fun (instead of doom scrolling tiktok)? project-edin.lovable.app/ Where are the vibers at? How many hundreds of hours have you spent on your trello clone? Will the next model make it better? Just another 2 more weeks?

Here's what happens when I get serious about building. (And every line is fully reviewed? And I'm a solo founder?) Not bad for ~10 days...

Post attachment
Cryptosailor avatar
Cryptosailor@robertdavid010·Nov 4

Here's what happens when I get serious about building. (And every line is fully reviewed? And I'm a solo founder?) Not bad for ~10 days...

Post attachment
Cryptosailor avatar
Cryptosailor@robertdavid010·Nov 1

Pitch me your VC fund in 3 words. (3rd time founder/operator, traction in B2E, (SoR) startup, with long tail unicorn horizon).

Maya Protocol avatar
⟳ Cryptosailor retweeted
Maya Protocol@Maya_Protocol·Oct 30

🚨 Huuuuge news, tribe!! 🍥🤝🍫 Moca x Maya Protocol: Merchant Settlement is LIVE! What this means for: Businesses ➡️ Settle payments directly into native $DASH, $ZEC, $ARB, and more. Maya provides extra routes for every payment, adding critical redundancy and resilience to the network. Maya Ecosystem ➡️ Real-world retail payments now route through Maya's liquidity pools, driving consistent, continuous transaction volume and fee revenue for Liquidity Providers. Sweet settlement, fully native!

🍫 @Maya_Protocol settlement for merchants is out of beta. Every Moca business can now settle in native $DASH, $ZEC, $ARB and more. Added redundancy and resilience, with extra routes for every payment, powered by Maya. Sweet settlement, fully native 🍥

Cryptosailor avatar
Cryptosailor@robertdavid010·Oct 30

At least as an engineer I have proper concern for application security, which can extend into OPs, but its still not my wheelhouse. And yet even I can see how poor Binance (and many others) security posture is (and have witnessed first hand). CEXs are the bane of crypto.

As a 30-year sysadmin, this is why I hate the "DevOps" term and why, despite ending up in those roles, I still hate working in them. Here's the takeaway -- lengthy post: * Developers are not sysadmins. They are not thinking about operations, security, and good IT practises (i.e. default mindset of "trust nothing"). They are thinking about code and frameworks, they are thinking about CI/CD, they are thinking about getting releases out the door, they are thinking about bugs, they are sometimes are thinking about infrastructure, they might be thinking about the database (but if there are dedicated DBAs then probably not). In my experience it's very rare to find a developer who can adopt an operations mindset (they do exist, but they are rare). * Inversely, sysadmins are not developers. We ARE thinking about operations, security, infrastructure, and good IT practises. We are not thinking about a developer's buggy code (but will likely be called at 0300 to investigate a problem with it and track down its erroneous behaviour; and if not us, an SRE for sure; then proceed to have to meet with the developer to explain to them why their code is poor), we are not thinking about CI/CD, we are not thinking about releases or bugs, and we are not thinking about the database. We are thinking about the site/service/platform and the systems/hosts/VMs as a whole, we are thinking about DNS, we are thinking about the network (I do, and often act as a communication liason between operations and network engineering). We can (and usually do) learn to code, but more at the "convenience" level than at the same depth a developer does. Good developers should work with sysadmins to learn basic concepts like, for example: why overcommit is a bad idea, why ulimits are important (i.e. don't just blindly raise them), why it's important to close your file descriptors, why read(fd, &buf, 1) or write(fd, &buf, 1) is a bad idea, the performance hit of fork(2), why that "find /" is a real bad idea, why EFS (NFS) is useful yet dangerous, what it means when sk_buffs are exhausted and how/why, etc... We do not have time to reverse engineer your home-grown framework and stack, but we WILL know damn well if it's misbehaving. We expect devs to know their piece as well as we know our piece, and devs should expect the same of us. In short: software devs going into DevOps means you lose the "Ops", while sysadmins going into DevOps means you lose the "Dev". This is why BOTH roles should remain independent and both team(s) should work together. Likewise, there is a proportional relationship between the quality of work (in a subject area) and the number of hats the employee (or team) wears. More hats = worse quality results on a per-hat basis. Fewer hats = higher quality results on a per-hat basis. Think I'm wrong? Think of an actual full-time DBA. They are masters of their domain, and they are who any team goes to for any DB-related issues, query performance problems, or table schema design. They generally are not expected to wear multiple hats; there are no "DBAOps" or "DevDBA" roles, for example. You go to DBAs because you know they are focused on that one thing they do best. Yet, for some reason, some MBA-wielding idiots in the 2000s started merge operations and software developers -- mainly because someone thought "coders can install Linux, so that means they're sysadmins!" No. It was a stupid idea then, and it's still a stupid idea 25 years later. Hire people to be masters of their domain, not all the domains. Remember: even Lucifer cannot maintain all 9 layers of Hell.

Cryptosailor avatar
Cryptosailor@robertdavid010·Oct 30

CEX's are the bane of the blockchain industry. @cz_binance and @binance NEED to be doing more for proper risk management. Even Web 2.5 would be better (but they won't listen to an OG like me?). We were both there 'back in the day' CZ. You should have known better.

Post attachment
Cryptosailor avatar
Cryptosailor@robertdavid010·Oct 28

This is just the beginning. Full mainstream mass adoption was always inevitable.

BREAKING: 🇺🇸 Google just unveiled new security system to help banks store and transfer cryptocurrencies. This is MASSIVE!

Post attachmentPost attachment