windows
zip: https://github.com/hydrusnetwork/hydrus/releases/download/v191/Hydrus.Network.191.-.Windows.-.Extract.only.zip
exe: https://github.com/hydrusnetwork/hydrus/releases/download/v191/Hydrus.Network.191.-.Windows.-.Installer.exe
os x
app: https://github.com/hydrusnetwork/hydrus/releases/download/v191/Hydrus.Network.191.-.OS.X.-.App.dmg
tar.gz: https://github.com/hydrusnetwork/hydrus/releases/download/v191/Hydrus.Network.191.-.OS.X.-.Extract.only.tar.gz
linux
tar.gz: https://github.com/hydrusnetwork/hydrus/releases/download/v191/Hydrus.Network.191.-.Linux.-.Executable.tar.gz
source
tar.gz: https://github.com/hydrusnetwork/hydrus/archive/v191.tar.gz
I had a good week, but I was a bit short on time and my current dev situation is slightly up in the air. As well as some IRL stuff, I am currently upgrading to new computers and network and generally playing musical chairs with hard drives. I did however write a simple bridge to IPFS and fixed some bugs.
I will not be working much on hydrus next week as I finish moving my network stuff around and set up my new machines. As a result, I do not think there will be a release on the 27th Jan. I will be moving to a new Win 10 development machine, and assuming that all goes well, I will be looking into the Win 10 BSOD that recently appeared, so there might be a simple release that fixes that. Or, if there is anything critically wrong with today's release, I will put out a hotfix.
As a result, the next regular release should be on the 3rd Feb.
After that, I'm travelling for a week. I doubt I will have much online time, and I won't be able to dev at all, so there also will not be a release on the 10th.
Beyond that, everything should get back to normal.
ipfs
I have added a new IPFS service type, which you can add under services->manage services. You put in the IP and port of your IPFS daemon, and there's a little button to test the connection. Once you have that set up, you can go pages->new download page->an ipfs file, which will let you put in a multihash. While developing, I used QmUuNBmjSnDt191j3ZJTt1H3QQUa2mrRco2zf563RPYQeh, which is an image of a keyboard an anon posted in a /tech/ IPFS thread.
If you don't have IPFS and want to try this out, especially if you run Windows, I recommend you just go straight here:
https://gobuilder.me/github.com/ipfs/go-ipfs/cmd/ipfs?branch=release
I used:
https://gobuilder.me/get/github.com/ipfs/go-ipfs/cmd/ipfs/ipfs_release_windows-amd64.zip
Apparently the 0.3.x branch has been buggy for Windows, but it worked fine for me. It's a nice big ipfs.exe that you can just go–
ipfs daemon
–to and you are up and running.
The code on my end is rough and prototype. The error handling is bad, and the services->review services ipfs panel is placeholder, but I hope you can get it to work for one file or another. In future, I would like to add IPFS file upload and multihash->clipboard from a thumbnail's right-click menu so you should be able to effect very basic P2P between hydrus clients.
full list
- added ipfs service type
- added simple ipfs service gui to manage and review services windows
- added simple ipfs download and import to pages menu
- split confused service data object into a bunch of more flexible and readable subclasses
- raw url downloads are now powered by 'requests' rather than my hacked http engine, and work a hell of a lot better. more to follow
- raw url downloads now pause and cancel correctly
- optimised some a/c cache clearing in mapping update processing
- optimised content update object -> db yield logistics
- added no-daemons command line switch to disable all daemons
- added no-wal command line switch to disable WAL journalling for the db
- if the db fails to read a new WAL-journalled db file it has just created, it will delete the file and attempt to recreate the db, never trying WAL again
- changed the way the db writes big repo syncs to disk so that the job can be abandoned much more quickly
- improved local file not found error to state the directory or exact path that was the problem
- fixed some socket-level error reporting (I think timeout was part of this)
- the petition approval and denial client-to-server network commit is broken up into smaller steps to reduce server lag and the overall likelihood of timeouts
- subscriptions will no longer add files to their 'successful files' button when the file's url seemed new but it actually was previously deleted
- subscriptions will now identify themselves with an additional popup message when they encounter critical errors during sync
- editing a clientside service will force a reset of the appropriate session cache, so if you change access key, the account changes will be reflected immediately
- the import files dialog will no longer spam error popups on uninteresting or empty files–its 'parsing complete' statement is more verbose instead
- the 1.5s gap between parsing complete and the buttons being enabled is also removed. this was supposed to be helpful, to give you a moment to check the files were as expected, but in the end it was just annoying
- fixed a typo in some thumbnail error catching and regeneration
- improved my network code syncing, so linux and os x releases are cleared out of many old files
- misc code cleanup
next week
Again, there will probably not be anything more than a very simple bugfix release next week. I'll be mostly doing IRL stuff, and if I finish that early, I'll be taking a little time off. I will make a reminder and general update on what's going on post on the 26th.