4,820 karma · joined September 7, 2008
> .7 and older nodes use BDB for storing the blockchain databases. It seems this database has a limit on the size of the modification it can make atomically to the database. With the larger blocks of the past days, it seems to have triggered the limit. The result is that 0.7 (by default, it can be tweaked manually) will not accept "too large" blocks (we don't yet know what exactly causes it, but it is very likely caused by many transactions in the block). Specifically, block 000000000000015c50b165fcdd33556f8b44800c5298943ac70b112df480c023 (height=225430) with >1700 transactions.
> However. 0.8 (which uses a different database system) has no such limit, and happily accepts the block. As the majority of the hash power was on 0.8, the longest chain ended up using this block, which is not accepted by older nodes.
[1] https://bitcointalk.org/index.php?topic=152030.msg1613200#ms...
I hope Facebook ends up open sourcing McDipper in the future.
Tent is actually a protocol, so anyone can implement their own server. We don't use Rails, but we do have reference server implementation called tentd that is written in Ruby: https://github.com/tent/tentd
Locally I already have Postgres installed for development, and Travis does as well. I guess this might be useful for Jenkins on EC2 in the same AZ as Heroku Postgres, but the latency is still going to be painful.
tentd git:(master) $ time bundle exec rake
#...
Finished in 14.6 seconds
818 examples, 0 failures
real 19.10s
user 11.59s
sys 1.22s
tentd git:(master) $ time bundle exec rake TEST_DATABASE_URL=$(curl http://api.postgression.com)
#...
Finished in 15 minutes 0.49244 seconds
818 examples, 0 failures
real 905.67s
user 23.37s
sys 3.12s
$ time brew install postgresql
==> Downloading http://ftp.postgresql.org/pub/source/v9.2.2/postgresql-9.2.2.tar.bz2
######################################################################## 100.0%
#...
==> Summary
🍺 /usr/local/Cellar/postgresql/9.2.2: 2819 files, 39M, built in 3.2 minutes
real 190.33s
user 338.87s
sys 60.70s1) Sue the US government to fight the order.
2) Use technical workarounds to inform your users without breaking the law. For example, rsync.net has a signed notice that they haven't been served a warrant: http://www.rsync.net/resources/notices/canary.txt
1: Your Entity (this is the url you're referring to. I could be https://jonathan.tent.is and then change to https://titanous.com). Think of entities like a name. You can change it but you really want to think carefully first. Other Tent servers know you by your entity. If all you told someone was your entity (https://spindritf.net) their Tent server would contact the URL where you have saved information about your Tent server. It's all you need to find out someone's Tent information or start following them, like a username. When you change your entity, your server sends out a post to all your followers and lets them know about a profile update with a new entity URL so they can update their records.
2: Your "canonical tent URLs" (the addresses of the servers where you can be reached). These are literally like your address. You can have multiple addresses and move any time you want. Again, your server will simply send a post to your friends letting them know you're moving and where to reach you. In both of these cases you probably want to give other servers some time to update their records before moving just in case.
There are a few edge cases worth mentioning. This system does not actually depend on DNS, but most users will. For example, instead of https://titanous.com I could theoretically list an IP address instead or a tor hidden service.
2) Every piece of data in the system will be available via the API including negotiated app and follow credentials, moving will consist of authorizing an importer app to have read access to everything, and then pushing a post that tells all the servers to check the profile again for updated entity and server details. It should be a very simple process.
[1] http://liberationtech.tumblr.com/post/13377461578/how-the-ne...
Posts have 'views', so a video or photo post would be pushed out with the 'meta' view which would include a URL to the content instead of the content inline.
Developers may implement other protocols in the future, but we are targeting HTTP as an accessible starting point.
We are definitely anticipating heavy mobile use, both through mobile web apps as well as native. There will eventually be iOS and Android frameworks to handle all of the communication with Tent servers.
The same goes with user switching, you can just use Ruby to do it (example at the bottom of https://gist.github.com/206253).
Unicorn also already has "error resistance" in that it won't switch to a master/workers that aren't booting properly during a restart.