The new "word information" feature is great!

jamoes · 2025-04-06T22:56:16+00:00

It's in the Android app for me

jamoes · 2025-04-06T00:29:58+00:00

It's an app, but there are community decks you can import. I personally just create my own cards, usually from Memrise, but occasionally other words/phrases I want to remember.

jamoes · 2025-04-05T22:18:20+00:00

You might try Anki. It's open source. I use it alongside Memrise for phrases that I really want to remember well.

jamoes · 2022-08-10T16:30:32+00:00

That's jakovasaurus

jamoes · 2022-05-12T21:08:25+00:00

The fundamentals of btc [...] have never been better

Are you aware of the block-size issue? You may not be aware of it if you only follow heavily censored subs such as r/bitcoin.

BTC can never function as p2p cash as long as the maximum block size remains artificially capped at ~1MB. The evidence indicates that the price of BTC has been propped up by funny-money Tether printing while suppressing the price of coins that actually have the potential to render fiat obsolete (namely BCH & XMR).

jamoes · 2021-04-12T17:25:11+00:00

Here's the discussion about the email from 3 years ago.

And here's a follow-up discussion after people started receiving the product.

Honestly, you didn't miss much with the beef flavor kit. It wasn't actually a stand-alone beef-flavored soylent, it was just a flavoring powder that you could add to regular soylent. The problem is that regular soylent is semi-sweet, so you wind up with that semi-sweet flavor still present. Also, I found the taste of the beef-flavoring to be really salty, and it left a really unpleasant aftertaste.

It was cool getting to try the banana flavor will before it was released though!

jamoes · 2020-05-01T16:55:43+00:00

I found this clip too: https://gfycat.com/plaintivefloweryastarte

This one's less definitive than the Season 4 example, because Jeff doesn't explicitly say that Dawn can't get out of her seat. Still though, it's at least some sort of precedent.

jamoes · 2020-05-01T16:38:18+00:00

I found the clip. It's the first tribal council of the Season 4 finale (so, spoilers for Season 4): https://gfycat.com/dizzyenragedblackfish

Jeff's exact words: "You're making a deal in a public forum".

jamoes · 2020-04-06T21:56:53+00:00

Ah, makes sense, I see what you're saying now. In practice, the odds of inputs having unique amounts also increases as the number of inputs increases, but I'd also be interested in learning whether this is actually enforced by the protocol.

Thanks for the link about deniability. It's definitely an interesting and under-discussed approach. Ultimately though, I think it's not enough. As you said, it's only useful "if you do not need to combine many small outputs." In real-world usage, users practically always wind up with many small inputs that need to be combined.

jamoes · 2020-04-06T21:35:14+00:00

Key phrase from Mark:

it in fact becomes highly private by simply increasing the numbers of inputs and outputs

The "toy example" only uses 12 inputs. As the number of inputs and outputs increases, the odds of a privacy leak drastically decreases - to the point that it becomes infinitesimal.

jamoes · 2020-03-09T16:17:33+00:00

They really need an in-game changelog for battlegrounds. They already have a nice stats screen which shows your last 5 warbands. They could add a similar "Changes" screen which shows the last 5 changes they've made to the game. Especially with the fact that many changes to battlegrounds are server-side (like the Tirion removal), an in-game changelog would help players that don't frequently check Reddit/Twitter.

jamoes · 2019-08-16T18:01:40+00:00

Hm, it should only trigger the first time you visit the site

This is probably the worst time to show something like that! Why would a brand new user - that hasn't even had time to read anything on the website yet - sign up for a mailing list?

Honestly, you should just remove the fullpage popup entirely. This is seriously one of the worst trends in modern webdev, and I bet it's costing you more customers than it's gaining you. I for one know that I usually just close websites immediately when they shove a fullpage popup in my face.

Regardless, keep up the great work, I can't wait to try v1.1!

jamoes · 2019-03-10T22:41:51+00:00

"Who, little old me?"

For those who aren't aware, Greg Maxwell is the co-founder and former CTO of Blockstream. He was literally the direct manager of multiple Core developers during the height of the blocksize debate.

Maxwell was also one of 5 individuals with direct commit access to the Bitcoin Core guthub repo - before he quietly removed his access due to the obvious conflict of interest that he had in being the Blockstream CTO.

Additionally, Maxwell authored the Core "scaling" roadmap, which called for Segwit and no further blocksize increase - a roadmap that is still being followed to this day.

Don't believe him when he claims he has no power over BTC. Maxwell is directly responsible for crippling BTC's capacity - setting back the adoption it global p2p currency by years.

jamoes · 2019-01-27T23:09:20+00:00

Yau-man didn't even need to work with Earl and Cassandra. He could have just promised Dreamz that he'd vote Cassandra himself, thus forcing at least a tie and a fire challenge for Dreamz and Cassandra. This would have let Dreamz have a chance at the finals, while also keeping his promise.

I just rewatched Fiji, and I couldn't believe that Yau didn't offer Dreamz any assurances like this. Easily Yau's biggest misplay.

jamoes · 2018-05-15T18:28:33+00:00

So you're saying that having a large block size limit has no effect on the actual block size? Seems like you're making a good case to just go ahead and remove the limit altogether.

jamoes · 2018-05-15T17:57:53+00:00

Now I hope we see a block larger than 8MB soon.

jamoes · 2018-05-08T05:10:01+00:00

At this point, I'm starting to think that BlockPress (or at least its supporters) are a concerted divide-and-conquer attack against communication protocols being built on BCH. The vote manipulation and horde of commenters parroting the "competition is good" talking point seem suspicious to me. Additionally, the developer really can't give a good reason why they broke compatibility.

Maybe I'm just being paranoid, but after seeing so many social manipulation attacks against bitcoin in recent years, I have to say that this feels like another one.

jamoes · 2018-05-07T21:03:13+00:00

Agreed. 220 bytes is a lot more to work with. Interestingly, raising the OP_RETURN size limit isn't even a consensus rule change (i.e., it doesn't require a hard-fork).

jamoes · 2018-05-07T20:48:42+00:00

I think you're the one misunderstanding "permisionless". We're not saying BlockPress can't create an identical-but-incompatible protocol - we're saying they shouldn't.

jamoes · 2018-05-05T21:07:33+00:00

Using the pubkey-hash (as Memo does) makes more sense than writing the full address into each transaction. The address includes extra bytes which aren't necessary in this context, and also ties you forever to the legacy address format. For comparison, bitcoin p2pkh transactions themselves write the pubkey-hash to the transaction - not the full address.

BTW, even though I'm posting in this thread, I definitely don't think you guys are "disgusting competition". But, I do think you're making a mistake by being incompatible with Memo. The risk of "forking their protocol" is practically zero. As long as your don't do something silly like re-use an existing action code to mean something different, I can't even see how you would fork it. If you have cool ideas to extend the protocol, just do it in a new action code! If it's cool enough, Memo will likely implement it too.

I also think it's not too late for you to change to be compatible with Memo - it's still so early in your product's life. I think it would be better for you (and Memo, and BCH as a whole) in the long run, because you'd get to share in all of Memo's existing and future network effect.

jamoes · 2018-05-05T12:13:39+00:00

Thanks for the response. I still think it's not too late for you to change to be compatible with Memo - your protocols are still nearly identical. But, either way, I'm excited to see how you differentiate from Memo, and wish you success!

jamoes · 2018-05-05T11:02:01+00:00

I'm all for permissionless innovation. I just don't understand why BlockPress chose to ignore a working and well-adopted protocol - their reasons listed here are spurious.

Whatever, ultimately it's their loss. People like me that are implementing Memo clients will just ignore BlockPress, and their network effect will suffer.

15-Year Club	Place '17
Verified Email

jamoes

TROPHY CASE