Last week I spent every waking moment coding Myrme. I haven’t been this consumed by flow in years. I even thought I permanently lost that ability. But, *does prayer dance*, that turned out to be false. I could never order myself to get into the state of flow. Like falling in love or falling in general, it’s something that happens to you rather than something you decide to do. A mysterious force either takes you or doesn’t. Last week it did.
When you get around to messing with smart contracts, I highly recommend checking out the Pact smart contract language (https://github.com/kadena-io/pact). It's based on lisp, is more expressive than solidity, and is maintained by an incredible engineering team (I have no affiliation with them btw). I've messed around with a few other "smart contract languages" as well, and Pact has been by far my best experience. That being said, if the primary goal in learning solidity is just to get a feel for smart contracts, then its probably not a terrible place to start due to the massive amounts of documentation
The approach to not care about decentralisation at first is the right one, imo. Who cares if it's decentralised if you can't use it in the first place?
Please don't waste time with Solidity, "smart contracts" and other hocus-pocus that doesn't work. Unless you are looking to raise money - then sure, VCs love the jargon.
For decentralization I would advise you to look into https://github.com/fiatjaf/nostr - very simple approach that should scale without any problems.
Shouldn't the decentralized infrastructure be built in parallel with the UX? First, "decentralized" itself is a big magnet for new users these days. Second, if The Cloud wants to ban you, it'll be a race against them.
Myrmecology is the study of ants which I think is coincidentally fitting for a social network
When you get around to messing with smart contracts, I highly recommend checking out the Pact smart contract language (https://github.com/kadena-io/pact). It's based on lisp, is more expressive than solidity, and is maintained by an incredible engineering team (I have no affiliation with them btw). I've messed around with a few other "smart contract languages" as well, and Pact has been by far my best experience. That being said, if the primary goal in learning solidity is just to get a feel for smart contracts, then its probably not a terrible place to start due to the massive amounts of documentation
The approach to not care about decentralisation at first is the right one, imo. Who cares if it's decentralised if you can't use it in the first place?
Can I be a part of the app's early-user group?
Do you have any plans to use handshake (handshake.org) in conjunction with IPFS? Have you considered sia.tech instead of IPFS?
Please don't waste time with Solidity, "smart contracts" and other hocus-pocus that doesn't work. Unless you are looking to raise money - then sure, VCs love the jargon.
For decentralization I would advise you to look into https://github.com/fiatjaf/nostr - very simple approach that should scale without any problems.
Shouldn't the decentralized infrastructure be built in parallel with the UX? First, "decentralized" itself is a big magnet for new users these days. Second, if The Cloud wants to ban you, it'll be a race against them.