Peeps by @jm9k
Showing page 36 of 37 (1,817 peeps total)
Replying to @Plumber86 (0xd1a4d5a1c50b3a089ce55745e7778b668c53058e)
@Peepeth community, Haven’t had a chance earlier. Just checking in on the fellow peeps. Been playing in the dirt and concrete today! #plumberlife
I see you made it through the concrete. Were the pipes exposed like that, or did you have to dig?
@bevan #suggestion Cut out the middle man apps, and give us the ability to schedule the posting of future Peeps/Tweets.
This isn't exactly new news, but you need to know about this pig.
Replying to @alexfisher (0xe6dc7254dc531a1dc098282071988f0f6b0b678f)
This is my first peep. Awesome! #ethereum #blockchain
👍
@bevan #suggestion A checkbox to automatically show new peeps without having to click the button if the window has focus.
Replying to @jvck (0x49f7729c66b66cbf0a2e174ff4487be22027177c)
Do you even peep?
I'm peeping so hard right now
Replying to @jm9k (0xa7bd09daab3eb5ec96f04914d94c47681489d604)
The issue I have with IOTA is that their tech is deeply flawed, and they refuse to acknowledge it. Instead they go around blasting everyone who brings up concern, and endlessly tout their tech as being something it clearly is not.
Alternative approaches are a good thing that should be investigated. However, there are better ways to do this. Nano is an example of a much better approach and attitude towards improvement.
Replying to @dean (0xddf4da877d64c694ac69175feedb19a2591f7d7f)
I appreciate it the alternative approach to building a blockchain with a focus on (eventual throughput), but it does make for a short term poor experience. Having said that, I'm still glad the IOTA team is taking on the challenge because if they succeed, we all win.
The issue I have with IOTA is that their tech is deeply flawed, and they refuse to acknowledge it. Instead they go around blasting everyone who brings up concern, and endlessly tout their tech as being something it clearly is not.
Replying to @409h (0x11b6a5fe2906f3354145613db0d99ceb51f604c9)
%3Cscript%3Ealert(1)%3C%2Fscript%3E
Let's check for vulnerabilities with nonstandard whitespace.
http://kb4images.com/images/image/37185176-image.jpg onload="alert(1)"
Replying to @Jeepers_Peepers (0x8f2ea6f530bf4523fdd2bf931d4e4d07b550841e)
You could say their consensus model is all tangled.
Replying to @Alec (0x23677376bc1b7f48970b83a7ce0d0367395eac9e)
IOTAs current consensus model is a mess. The very first IOTA transaction I made was confirmed on the node my desktop wallet was using, then showed up like a day later as unconfirmed when that node eventually went down. Not to mention you have to rebroadcasts TXs manually often.
It's definitely a disaster of a project. However, they raised so much money they might be able to hire competent people build an entirely new product.
Replying to @Alec (0x23677376bc1b7f48970b83a7ce0d0367395eac9e)
My source: https://www.google.com/amp/s/amp.reddit.com/r/Iota/comments/7ngn7k/coordinator_is_currently_turned_off_tangle/
The coordinator is never going to be turned off until they radically change their entire consensus model. I did a write up on some of the issues with IOTA last year, and this topic is mentioned:
@bevan Minor #bug: After inputting a high price and then changing it to a lower one, the warning doesn't disappear.
Replying to @balibebas (0x1f1c2bcae0505db4fb9c51305af8baa976c26af4)
wish you were here https://coub.com/view/rxcx3
Yeah, pretty much.
Replying to @jm9k (0xa7bd09daab3eb5ec96f04914d94c47681489d604)
Dang, the cross post to Twitter didn't seem to work. #bug
Actually, the post went through but not the image.
Replying to @jm9k (0xa7bd09daab3eb5ec96f04914d94c47681489d604)
@rogerver If you're looking for a more censorship resistant version of Twitter, perhaps you should give Peepeth a try. @peepethapp https://peepeth.com/
Dang, the cross post to Twitter didn't seem to work. #bug
@rogerver If you're looking for a more censorship resistant version of Twitter, perhaps you should give Peepeth a try. @peepethapp https://peepeth.com/
@Bevan #suggestion I'd really like to see a summary in the notification feed, or some kind of expand/collapse functionality.
Replying to @Peanut (0x1633d82e406f76af23bd52d8c7e5d8c78bfc6597)
Hey folks, just joined :) Gotta run to bed here now but thought would say a quick hello :)
👋
Replying to @NateStipe (0xd5d560b2e9faddd6796ac777963dd59c42babae2)
#suggestion Create a "bug badge" for Peepers to be awarded when they identify a pre-determined number of bugs.
👍
@Bevan #bug Z-index problem here. When I click the "Show new Peeps" button it clicks the post below it instead.
Replying to @Chris (0xa64fc17b157aaa50ac9a8341bab72d4647d0f1a7)
Today I left my job at a Fortune 500 to work on #Blockchain full time. Here we go!
🙌
Replying to @jm9k (0xa7bd09daab3eb5ec96f04914d94c47681489d604)
Let's try lowercase #nsfw tag.
Yep, lower case nsfw hashtag works. It's just not case sensitive.
Replying to @abcoathup (0x13ebd3443fa5575f0eb173e323d8419f7452cfb1)
@bevan #suggestion NSFW flag. (This has changed)
Let's try lowercase #nsfw tag.
Replying to @abcoathup (0x13ebd3443fa5575f0eb173e323d8419f7452cfb1)
NSFW flag
That says it's to report "unlawful" posts. That shouldn't be treated the same as NSFW.
Replying to @abcoathup (0x13ebd3443fa5575f0eb173e323d8419f7452cfb1)
The hashtag doesn’t set a peep to NSFW (that I am aware of anymore). You can flag a peep to admins as NSFW using the flags. Select a peep and you will see a flag.
I don't have an NSFW flag button. The flag I have is for "unlawful" posts. It doesn't say anything about NSFW.
Replying to @thecrazygm (0x47bd1b5dd86fdec100fa8f899a43f5e04fbfa824)
Got paid! Topped up my ETH so that I may keep on #peepin.
I'll be adding more ETH to mine soon also. As soon as I can send small tips I'll do it much more often.
@bevan Got another weird one. The feed says @Steve followed me four times. He assures me I'm not nearly cool enough to follow more than once. 😎 #bug
Replying to @Plumber86 (0xd1a4d5a1c50b3a089ce55745e7778b668c53058e)
What does this machine do exactly?
Replying to @abcoathup (0x13ebd3443fa5575f0eb173e323d8419f7452cfb1)
NSFW flag exists already. Select a peep and you will see the flag.
It appears that it supports lower case only.
@Bevan The #NSFW flag is not case insensitive and doesn't trigger if it's in caps. 🐛 #bug
Replying to @abcoathup (0x13ebd3443fa5575f0eb173e323d8419f7452cfb1)
Your peeps are in IPFS but only the peepeth front end has a link to them. (So other clients couldn’t see your peeps). Though the front end enforces a 15 peep batch limit so you wouldn’t be able to peep after that.
But the Peepeth backend server reflects new peeps immediately, even if they haven't been committed yet.
Replying to @jm9k (0xa7bd09daab3eb5ec96f04914d94c47681489d604)
Some features I'd like to see on Peepeth: - Smaller tip amounts! Custom amounts would be great too. - Ability to search recent peeps by keywords and #hashtags. - Auto-save of peeps being written but not yet posed so you don't accidentally lose them. (Second time writing this.)
A way to flag posts that are #NSFW.
Replying to @khay (0xd43afa0c3184635fa1a5fd7e9727731c5df6dcde)
Very first #peep right here ! #403, proud to be part of a revolution at this very early stage ! #Peepeth #revolution #blockchain
👍
@bevan What happens if you make a peep but never commit it to the blockchain?
Replying to @CallMeGwei (0x285bc660aa42b8effc6c60357cd4d8ca072be625)
@Bevan #suggestion When you click to save a batch... have an option to see what exactly you're saving... like a summary. This would be especially beneficial when pre-save editing is available. You get one last chance to double-check things before you commit them.
👍👍👍
Replying to @CallMeGwei (0x285bc660aa42b8effc6c60357cd4d8ca072be625)
I'm a desktop lover myself, but mobile is absolutely critical to success - no doubt. For a majority of the world mobile is the only readily available internet connected device. Truly appreciate your passion!
I'm primarily a desktop user as well, but I have to admit that having Twitter on my iPad has occasionally been very convenient.
I've known a few people who don't even own a computer now. They live exclusively off their smartphone.
Replying to @CallMeGwei (0x285bc660aa42b8effc6c60357cd4d8ca072be625)
I mined bitcoin back in late 2000s for a few months - and proceeded to wipe and reuse the harddrive until it died some years later. I'm so thankful that I cannot remember the quantity of coins mined.
Here is a screenshot of my old slushpool account. It's all long gone. 😢
Replying to @CallMeGwei (0x285bc660aa42b8effc6c60357cd4d8ca072be625)
Haha, thank you. Will absolutely do so. Honestly, @Bevan has a great chance here to dominate the blockchain micro-blogging space. I've already submitted my application to help him manage his empire. I'll be sure to suggest a pizza party for the first 500 Peepers. ;-)
Anything with pizza gets my vote. 🍕🍕🍕
Replying to @jm9k (0xa7bd09daab3eb5ec96f04914d94c47681489d604)
I imported my MetaMask key to Trust, and it seemed to functional, except for some minor cosmetic defects. The first batch I saved worked fine, and fully confirmed. The second attempt to save the batch gave me this error. Didn't do anything with any other dapps.
I force quit and restarted Trust and then it worked fine.
Replying to @CallMeGwei (0x285bc660aa42b8effc6c60357cd4d8ca072be625)
Did you just save a batch? Did you just switch devices / wallets? Did you tx with to any other dApps using the same address? Brain dump! go go go...
I imported my MetaMask key to Trust, and it seemed to functional, except for some minor cosmetic defects. The first batch I saved worked fine, and fully confirmed. The second attempt to save the batch gave me this error. Didn't do anything with any other dapps.
Having a bit of a problem with the Trust browser on iOS. Is this a problem with Trust or Peepeth? #bug?
Replying to @CallMeGwei (0x285bc660aa42b8effc6c60357cd4d8ca072be625)
Remember the Bitcoin pizza story? ... I'm not a "price guy" myself, but we may be having some thousand dollar conversations around here. What a great crowd to pioneer this space with.
I once paid someone .5 BTC to draw a meme. I checked a while ago and it’s still sitting in that address.
Replying to @CallMeGwei (0x285bc660aa42b8effc6c60357cd4d8ca072be625)
What if the master key is compromised? I do think this would add convenience... but it also introduces... "No... I didn't say that - I was hacked and then revoked that key"... The master key should not be replaceable, imho, or you will have a name squatting/market activity.
The master key would not be replaceable, only the subkeys. That way you can use subkeys for day to day, but the master key is stored in a vault or hardware wallet with the other important stuff.
Replying to @CallMeGwei (0x285bc660aa42b8effc6c60357cd4d8ca072be625)
May I ask why you'd like this? Right now we can cross check digital identities between dApps. Those who would like privacy can spin up another address, but those who want to build a digital identity can do so with the same public address everywhere. The address is on the chain...
There is definitely an issue here with privacy. Maybe it should be obvious, but it's not since this tech is still so unfamiliar to most. At the bare minimum, it should be made very clear that the associated address will be linked to the account and made public.
Replying to @jm9k (0xa7bd09daab3eb5ec96f04914d94c47681489d604)
To an influencer, the identities are the most valuable item, and having them on a mobile device could be essential. OS level support for keys may be the future, but that's a long way away.
What if an account could be associated with multiple private keys. This allows different devices with different keys to all post to the same account. A single master key could be used to add or revoke access in case of a device compromise.
Replying to @abcoathup (0x13ebd3443fa5575f0eb173e323d8419f7452cfb1)
Eventually key management will be part of the OS. In software wallets only keep a small amount of funds/tokens. There is risk with each app, only use ones you trust and have triple checked. The most valuable item in my software wallet is my peepeth and Toshi identities.
To an influencer, the identities are the most valuable item, and having them on a mobile device could be essential. OS level support for keys may be the future, but that's a long way away.
Replying to @CallMeGwei (0x285bc660aa42b8effc6c60357cd4d8ca072be625)
since you are on a #suggestion role... I'll add one too. I've already mentioned it to @Bevan, but would be interested in community feedback. The action counter should go higher based on some conditions, but there should also be a time limit. You must save to chain every 24hrs.
The only issue I see is if someone forgets to commit for over 24 hours, then they could be out of luck. Perhaps more frequent commits should be incentivized with priority in the feed, but late commits are not restricted in any way.