💡 These steps will become easier, less technical, and more accessible as more open tools begin to emerge around Hicetnunc pinning. The steps below assume macOS but should work similarly across other platforms. This gist can be seen as a working draft toward more polished documentation; if you see any issues please post a comment below.
Hicetnunc.xyz aims to be "decentralized" which means the OBJKTs are owned by the users, not the platform. So, in theory, if hicetnunc disappears, another marketplace could emerge on the same (user-owned) assets. But, this paradigm of decentralization means that you own the assets; so the responsibility to maintain them lies on the users, not the platform.
Of course, hicetnunc and some of its users will probably also make an effort to help maintain all the assets on its platform; but you should not rely purely on that, as it goes against the core ethos of dec
| #include <codecvt> | |
| #include <cstdlib> | |
| #include <iomanip> | |
| #include <iostream> | |
| #include <locale> | |
| #include <string> | |
| #include <system_error> | |
| #include <vector> | |
| #include <Windows.h> |
以下転載:
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
| source 'http://rubygems.org' | |
| gem 'sinatra' | |
| gem 'sinatra-activerecord' | |
| gem 'sqlite3' | |
| gem 'require_all' |
