Peeps by @udiWertheimer
Showing page 1 of 1 (14 peeps total)
Replying to @bob (0xed3c6bcaaee02ed5ed572f87d36c4cc7d2f2bdef)
I did, indeed. What I mean is that the "overkill" is part of a long term vision for more cross EVM integration. So while it may be overkill for what it currently does (hashing and proof-of-publication), it lays the foundation for other dApp integration based on the EVM. ;)
+1 Gotcha. Looking forward to it! Are you on the team?
Replying to @bob (0xed3c6bcaaee02ed5ed572f87d36c4cc7d2f2bdef)
One of the long term visions is to see multiple front ends developed based on the peepeth backend, and Ethereum is currently the most widely supported dApp engine. I also see potential for embedding other dApp widgets on Peepeth.com (a polling dApp for instance). #DevFriendly :)
Did you see the rest of the thread? My point is that a "dapp" is potentially overkill for what peepeth does
Replying to @jam (0x2589b11029bd58ca8d917e2ba9f062dec946b463)
Overkill but already standard. It'd be overkill to stick decentralized apps on Bitcoin or Ethereum unless you want interoperability with the rest of its ecosystem ie, Peepeth tips, which are verifiable, shared on the blockchain, and something you might need metamask for.
Well for tips all you really need is a "bitcoin:" link (or some other coin) that is universally understandable by wallets. It eases key management too (can pay from any account) and automatically supports mobile etc.
Replying to @udiWertheimer (0xa1c25a98427c88806f76317a731c0a621390e744)
Haha hi there. Even when I'm trolling I try to create value ;) See this thread: https://peepeth.com/udiWertheimer/peeps/QmVRVJLERdBiWE8ukzFRzkoXFkyf8S5YZxMUqN5jrkEkaz (btw @bovan it's difficult to read threads right now, have to click through replies to find out if there's more)
whoos, mispelled @Bevan
Replying to @benk (0xc16c8702a1d50a92669ed0f970d6e1f7dae74c44)
@udiwertheimer can’t believe you’re here. Welcome! I guess you are here for trolling (are you here for some open serious discussions as well?) but at least now we know you do own some ETH ;)
Haha hi there. Even when I'm trolling I try to create value ;) See this thread: https://peepeth.com/udiWertheimer/peeps/QmVRVJLERdBiWE8ukzFRzkoXFkyf8S5YZxMUqN5jrkEkaz
(btw @bovan it's difficult to read threads right now, have to click through replies to find out if there's more)
Replying to @udiWertheimer (0xa1c25a98427c88806f76317a731c0a621390e744)
It is a good reason. But since the contract is stateless, metamask isn't able to verify anything, it can only submit. If you only care about submitting, you only need to manage a key to prove it's you. peepeth-dot-com could aggregate all posts and timestamp them once an hour.
So the metamask functionality is overkill IMO. All you need is some form of key management. Doesn't need to be blockchain related at all.
Replying to @jam (0x2589b11029bd58ca8d917e2ba9f062dec946b463)
Well.. isn't this a very good reason? Afaik, there's no standard protocol between browser-based bitcoin (or bitcoin based coin) clients for creating rich transactions. Ethereum was intended to create apps, so there is. Will concede that it likely will eventually exist.
It is a good reason. But since the contract is stateless, metamask isn't able to verify anything, it can only submit.
If you only care about submitting, you only need to manage a key to prove it's you. peepeth-dot-com could aggregate all posts and timestamp them once an hour.
Replying to @jam (0x2589b11029bd58ca8d917e2ba9f062dec946b463)
Multi-chain peeping anyone? 🤔
The main reason I can see to use ETH here, is that Metamask already exists and is easy to use. Otherwise using something like BTC (and definitely smaller alts like LTC/BCH/DOGE) might actually end up being cheaper
Replying to @jam (0x2589b11029bd58ca8d917e2ba9f062dec946b463)
I'm not working on an Ethereum based project. (I'm building something with Beaker Browser and Dat). You're clearly the target audience for my talk haha :), it was titled "Distributed state machines, why do we need them?"
Maybe I'll watch it if you'll link to it someday :)
Replying to @udiWertheimer (0xa1c25a98427c88806f76317a731c0a621390e744)
Also, since "peeps" aren't stored on-chain (another great design choice) but only committed to with a hash, it seems like they only provide a proof-of-publication (see https://petertodd.org/2014/setting-the-record-proof-of-publication).
In fact, the Peepeth backend feels a lot like "OtsProofBot" (https://twitter.com/otsproofbot) which uses the open timestamp protocol to prove publication of tweets. It also automatically batches proofs together.
Are any of you people familiar with that?
Replying to @udiWertheimer (0xa1c25a98427c88806f76317a731c0a621390e744)
First thing I learned since joining Peepeth is that its smart contract is "stateless". I think it's a very good design choice. But note that it could be easily implemented in *any* blockchain that supports arbitrary data (BTC/BCH/LTC/DOGE etc).
Also, since "peeps" aren't stored on-chain (another great design choice) but only committed to with a hash, it seems like they only provide a proof-of-publication (see https://petertodd.org/2014/setting-the-record-proof-of-publication).
First thing I learned since joining Peepeth is that its smart contract is "stateless". I think it's a very good design choice.
But note that it could be easily implemented in *any* blockchain that supports arbitrary data (BTC/BCH/LTC/DOGE etc).
Replying to @jam (0x2589b11029bd58ca8d917e2ba9f062dec946b463)
A guess: My university has some degree of academic focus on Robotics, Bioinformatics, and Computer Vision. My talk was very focused on "Theory" as Distributed Tech tends to. If I had gone up with a game or something immediately "useful", I likely would have seen more interest.
You mean like cryptokitties? I'm still not sure myself why cryptokitties need a "distributed web" :/
Replying to @jam (0x2589b11029bd58ca8d917e2ba9f062dec946b463)
*Obviously, you peeps do, and a few of my IRL friends are very receptive, but I'd say out of a lecture hall of ~100, 3 people engaged with what I shared. Presentation problems, perhaps. Great way to gauge how early we still are, especially since everyone there was technical.
What are your thoughts on why they're not interested?
What do you think would they should be, and/or change their minds over time?