Peeps by @sponnet
Showing page 1 of 1 (38 peeps total)
Replying to @pluma (0xd9fb1d684627a890347a4f6a7fe32e993617b6d8)
awesome! great shirt, @sponnet! 😄
Thanks @pluma
We're fiddling with @DAppNode in the restaurant downstairs @ETHBerlin - Come have a chat if you want to know more about it. https://dappnode.io/ - The Infrastructure for the Decentralized World @eduadiez #ethberlin #web3 #ipfs

Replying to @tnotm (0xeac76c5ad6de18749700306df11b09c261346be1)
@sponnet still only getting a hash and spinning wheel for me. Chrome and FF tested on same machine.
If you'd be so kind to check for errors in your debug console in chrome and post it as an issue, then I can take a look at it &
fix it. https://github.com/sponnet/peepfeed/issues - thanks for trying it out!
Replying to @satsearcher (0x6348dbea8987c27f8462755e493f64d99c28dd05)
I see it as a complement - an evolved version of Twitter that is better designed and more efficient. And long lasting. You can literally post whatever you want, but you can't take posts back. Remember, Peepeth.com is not the only frontend. If you can code, you can build your own.
Here's a hack of the day attempt : https://peepfeed.netlify.com :) beware b/c #nofilter and just a quick experiment thrown together..
Replying to @sponnet (0x447877f5d22bb91f87a71c71d0270d5ba2ac2040)
https://github.com/sponnet/peeping - go make it as accessible as you want!
https://github.com/sponnet/peepin now without autocorrect

Replying to @landfish (0xbf85b11c6928388d38e2b2b112b6305880f3bd42)
Not all immutability is created equal. Different ways of indexing data make for very different levels of accessibility. I want to know not just that my Peeps are immortal, but how easily discoverable they will be in the future.
https://github.com/sponnet/peeping - go make it as accessible as you want!
Replying to @ligi (0x0402c3407dcbd476c3d2bbd80d1b375144baf4a2)
Wonder if you gave @walleth a try and what made you choose a closed source wallet over a libre one?
Of course I have walleth installed too, but does it have an embedded browser?
Replying to @ligi (0x0402c3407dcbd476c3d2bbd80d1b375144baf4a2)
Android or iOS?
Android of course #politics :)
Replying to @ligi (0x0402c3407dcbd476c3d2bbd80d1b375144baf4a2)
Who here will be at @ethberlin ?
I'll be there too, let's meet there!
After installing months ago,
I now added @trustwalletapp to my home screen, for easy access to the Web 3.0 #ethereum #adoption
Replying to @sevvie (0xb9a7922eec475605498ba3c1f7f0aca98585f30a)
It'll have to be in a few hours; I have yet to sleep. But gladly! If we talk, we make a thread I can use for testing purposes ^.^
https://github.com/sponnet/peepin/tree/fixparser In this branch the peep scanner/iterator already works + I have started to document the IPFS format. Next up: implement the remaining JSON parsers for linking threaded peeps.
Replying to @sevvie (0xb9a7922eec475605498ba3c1f7f0aca98585f30a)
It'll have to be in a few hours; I have yet to sleep. But gladly! If we talk, we make a thread I can use for testing purposes ^.^
Well to thread along - check this initial processor I've made : https://github.com/sponnet/peepin
The good stuff is here : https://github.com/sponnet/peepin/blob/master/src/peepin.js - still a WIP but already walks & interprets all events of the contract. Feel free to fork/PR.
Replying to @sevvie (0xb9a7922eec475605498ba3c1f7f0aca98585f30a)
Not so much a front-end as an interface for displaying and archiving threads. I want to be able to capture and display long conversations for posterity's sake.
Let's talk.
Replying to @vbuterin (0x1db3439a222c519ab44bb1144fc28167b4fa6ee6)
On this note: is there a guide on how to pull peeps from IPFS without going through peepeth?
3rd party JS code that does exactly that: https://github.com/ipfsconsortium/IPFSConsortiumProxy/blob/1be68698d017f951ee094e929675b46550a4d301/src/plugins/peepeth/index.js & an example 'Peepeth Gallery' mashup: http://peepethgallery.web3.party - it's permissionless open data
Go ahead and show some love to the creators of Peepeth !
Just updated the Ropsten testnet ETH faucet with a new #react frontend. If you need some crispy fresh Ropsten ETH , get it here https://faucet.ropsten.be/

If you happen to be in Zurich on August 2nd, make sure to attend this Meetup
https://www.meetup.com/web3hacklab/events/253040360/
@jbaylina @eduadiez @thegrifft
Replying to @sponnet (0x447877f5d22bb91f87a71c71d0270d5ba2ac2040)
Well hello my little friend :)
Found it in the grass in Montenegro... so it's not a pet, just a new friend..
Replying to @Bevan (0x30755d3e65c0cf46c35b72d11e52d941c5fc3a3e)
Haha, is this wild or a pet? #grasshoppersofpeepeth
It's not a pet, just found it in the grass in Montenegro 🇲🇪
Well hello my little friend :)
News from the IoT dept: How to measure fine dust in the air and share that data with the world. https://hackmd.io/s/HytW4o-M7 @sensebox_de @okfde @particle #citizenscience

Replying to @doodlemania (0xa3ffa423140b730c0c2e1cc412a80cc49f125c01)
Why is that valuable? I thought the idea of IPFS was that data could be wherever and shouldn't care where. Or is my idea wrong? :)
You are now certain that the data will be persistent even when your nodes go / get taken down. It just helps to resolve data faster, but your basic assumption is right ofcourse...
Replying to @doodlemania (0xa3ffa423140b730c0c2e1cc412a80cc49f125c01)
Confused by the benefit of ipfs pinning. Easy explainer handy?
Pinning an IPFS hash makes the data it refers to persistent in your node's storage, so it will stay there forever until you unpin it, remaining available for others to find on the network. A 'pinning consortium' is a group of people/projects that pin each others hashes.
DappNode: https://github.com/dappnode/DAppNode#dappnode ; the IPFS Pinning consortium DappNode app : https://github.com/ipfsconsortium/DAppNodeConsortium ; Give it a spin - this might just be the future of DApp hosting. Kudos to @jbaylina @eduadiez @dapplion @YalorMewn

So there is this great team working on a decentralized app helper node ( DappNode ) that allows you to connect to the Web 3.0 - has support for .eth domains etc. So I decided to implement the IFPS pinning consortium as a DappNode App too ! #web3 #ipfs #ethereum
Replying to @abcoathup (0x13ebd3443fa5575f0eb173e323d8419f7452cfb1)
It does. Projects will need a backup for Ethereum and IPFS nodes. Though for now I assume many projects will keep depending on the fantastic work that Infura does.
I did a humble attempt to remedy this : https://medium.com/@sponnet/peepeth-now-always-available-b1a43f382058 , also check this repo https://github.com/dappnode/DAppNode a home solution that can host an Ethereum / IPFS / VPN node.
Replying to @bob (0xed3c6bcaaee02ed5ed572f87d36c4cc7d2f2bdef)
I just found out about OpenAPI (Swagger) and YAML... I have been working on developing an HTTP API for the embedded devices my company makes and have been dreading the documentation phase.. A massive weight was lifted from my shoulders today. #lazycoder #badcoder #rtfm #README
Next thing you know you are writing JSON schemas. Pro-tip : check https://jsonschema.net/ they have a neat generator to get you started. Hope it helps. Cheers!
Replying to @veox (0xf75b78571f6563e8acf1899f682fb10a9248cce8)
Peep images are loading faster for me through #IPFS (via Peepeth Reader) than from #AWS (via peepeth.com).
Probably because their cache is picking up steam by all these IPFS pinning consortium nodes around the globe, wildly pinning this content :) https://github.com/ipfsconsortium/IPFSConsortiumProxy
This Swiss doge. such lazy. so Wow.
Replying to @jvck (0x49f7729c66b66cbf0a2e174ff4487be22027177c)
AFAIK nodes delete/wipe data that has not been accessed for some time (which can be configured for each node). So it would be as you say, Peepeth would need some nodes to guarantee that no data is ever deleted. (I may be wrong.)
You can help pinning data for peepeth since a few days already : https://medium.com/@sponnet/peepeth-now-always-available-b1a43f382058

Anyone can support peepeth data persistence : https://medium.com/@sponnet/peepeth-now-always-available-b1a43f382058

Our Ropsten Ethereum Faucet now automagically fills in your metamask or wallet address when you visit it. Go to http://faucet.ropsten.be/ for some crispy fresh ropsten testnet ETH.

Replying to @veox (0xf75b78571f6563e8acf1899f682fb10a9248cce8)
The use of `ipfs.io` hard-coded into JS breaks display on #Firefox with IPFS Companion (and local #IPFS node). Error message has: "(Reason: CORS header ‘Access-Control-Allow-Origin’ missing)", among other things.
If you can fix it - I'll update the link - here's the repo : https://github.com/sponnet/peepethgallery
Just take a peep into the Gallery Of Peepeth :
https://ipfs.io/ipfs/QmfUuicg7kp2ArpixHL55rHzZ45RZTyHYhSdceAdtG3UHs/ - No need to scrape #opendata - no need to rely on a single site/provider to access #decentralized data - no need to ask for permission (ask for forgiveness)
Peepeth, now always available! https://medium.com/@sponnet/peepeth-now-always-available-b1a43f382058 - We've built a tool on top of Peepeth that creates a persistance layer for all posts and images on #IPFS. Increasing decentralization and the availability of your data. #Ethereum

Replying to @jvck (0x49f7729c66b66cbf0a2e174ff4487be22027177c)
Hum?
Well, the pun was 80% intended in that quote..

The first 20% of the project takes the first 80% of the effort, the last 20% of the project takes the last 80% of effort.
Preliminary documentation for the Ethereum Gasstation concept : http://ethereumgasstation.readthedocs.io/en/latest/index.html - exchange ERC20 tokens for gas. #ethereum