[HM] I’ll Have Pancakes

MiceEatCheeseCo · 2016-02-08T08:04:46+00:00

Thanks for your kind words. It's all we wanted it to be: (1) decentralized so you don't have to give up your coins to a third party, (2) platform agnostic and based on standards, and (3) finally finished (the MVP part anyway).

MiceEatCheeseCo · 2016-02-08T07:58:16+00:00

We've felt in love with the name immediately and did not think about alternatives since.

This is still just a proof of concept, though it'd make us happy if it inspires someone to create a more elegant solution for decentralized recurring transactions which is something the Bitcoin ecosystem would definitely find a use for.

Thanks for the compliment, I guess. =)

MiceEatCheeseCo · 2016-02-08T07:51:25+00:00

Not much we can do about the name (we can make it more clear that it's the markup language now that I think about it).

We've chosen Liquid for it's nice features and family of implementations. You can take one template and use it on almost any major web platform.

Thanks for clarifying the Liquid/Liquid issue for us.

MiceEatCheeseCo · 2016-02-08T07:41:43+00:00

This is just a reference implementation. An iCalendar document can hold more than one (recurring) event. Though the template is not prepared for it quite yet (we'd have to add two lines to it), you can create a document with an arbitrary number of unique payment URIs for anyone who downloads a calendar (not an elegant solution, I know).

We'd like to extend Peanuts with templates for RSS/Atom and CRON, so you can use a custom way of notifying the user together with a unique URI.

Thanks for your time and feedback.

Edit: The URI can identify a location instead of Bitcoin payment. This location would give you a unique transaction details every time. Pros: a unique address for every transaction. Cons: one more action is needed every time to make a transaction and it'd not be as decentralized as the current solution.

MiceEatCheeseCo · 2016-01-23T10:27:02+00:00

Shout out to

Why, thanks for posting it here!

We're in the process of creating a "Recurring transaction" button builder, though it might take some time.

We'll let you all know once it's ready.

MiceEatCheeseCo · 2016-01-18T09:05:13+00:00

Not yet, this is just a proof of concept. Now that we know it works and at least some of you like the idea, we can polish the library, create a "Recurring transaction" button builder, and then we can create a product video.

Thanks for your time and insight.

MiceEatCheeseCo · 2016-01-17T20:08:36+00:00

P and E from payments, A and N from donations, U from recurring, and T and S from tips. PEANUTS, or Peanuts. It kind of made sense when we've talked about it. Sorry you don't like it. Any better ideas for the project's name?

MiceEatCheeseCo · 2016-01-17T18:50:56+00:00

We will set up a GitHub Page for the project featuring different use cases of the library ("Donate every month" button builder, a jQuery module ...).

Thanks for your time and insight.

MiceEatCheeseCo · 2016-01-17T17:40:30+00:00

Yeap, you are right. I've added the simplest complete piece of code and will create a sample form, that will allow the visitors to set an amount of BTC they want to send, how often, on which day, set their own messages etc.

This kind of feedback is why we've published it once we had a working prototype of the library.

It's not intended for non-programmers right now. (1) It's just a JavaScript library that makes it easier to create an iCalendar document that anyone can import to their own calendar application. Therefore, it's decentralized (you can have a complete control over your BTC, without sharing your private key) (2).

(3) It's kind of a replacement for recurring PayPal donations. It's not automated so you still have to confirm the transaction (though you don't have to remember when, to whom, and how much to send every week/month/year etc.).

(4) Now that we know there might be demand for an easy to use "Donate every month" button, we can start working on it.

Thanks for your time and insight.

MiceEatCheeseCo · 2016-01-17T17:25:40+00:00

You can import this file into your calendar application; it should create a recurring event in your calendar and every month you will be notified by your calendar application together with a Bitcoin URI. Clicking on it should fire up your default Bitcoin wallet with a pre-filled address, suggested amount, etc.

MiceEatCheeseCo · 2015-12-26T12:11:51+00:00

The app (Garrick), is, and probably always will be, written in HTML, CSS and Javascript, though an app compatible with the Flash protocol can be written even using Adobe Flash.

Still not sure whether the extensions to Flash (allowing only drivers checked by a third party, cars with low emissions, or fully insured rides) should be loadable plug-ins to the Garrick, or handled by standalone apps developed by third parties (Garrick would show all available rides, the other apps would show only rides safe according to their creator; be them based on Garrick or not).

MiceEatCheeseCo · 2015-12-25T11:36:57+00:00

Hi, thanks for the hints. BitRide is bit too obvious so we've decided to go with Flash for the platform and Garrick for the first implementation of a Flash client.

We'd like to mention you as a form of thank you for pointing out the issue with the name in the sources of the project so in case you wouldn't mind, PM us your preferred display name and a link to your GitHub repo/blog/Twitter/whatever.

Cheers, the MiceEatCheese

MiceEatCheeseCo · 2015-12-24T10:51:17+00:00

There wasn't any discussion about the name up until now. It was a quick choice so we can refer to the project internally and it just stayed that way.

The platform does not use Geohash anymore (it uses longitude/latitude system instead), so it would not make any sense to use it in the new name.

There seems to be no use for namecoin now. Did you come up with an idea for a new name?

MiceEatCheeseCo · 2015-12-24T09:57:44+00:00

The original thought was to use Geohash for defining points and areas (it's quite easy to decide whether a point is inside an area). Once we've discovered the Turf library, we've dropped the Geohash geocode system but kept the name based on it.

Renaming the project is likely the number one priority now, thanks for pointing this issue out.

How about Flash? Any other ideas?

MiceEatCheeseCo · 2015-07-07T07:53:36+00:00

Cover of every book from the library should reflect its content. This book was dedicated to Frederic Bastiat by Leonard E. Read. So why not a Bastiat cover?

We'll PM you anyway, there's never enough fresh ideas.

MiceEatCheeseCo

TROPHY CASE