Mait mait

Thinking about 'meta' torrent file format.

Let's say I've downloaded big file using torrent. Then add very small file and recreate new torrent file. Like subtitle.

Now two torrent files are totally different file to machine. Tracker and torrent client would treat them different torrent. Of course we don't need duplicate original data file for multi seeding. But seeders and leechers split by two torrent file. They don't know about they have exact same file. Torrent client and tracker cannot connect people for exact same data. We have split share pool for exact same file. It's not efficient. More seeders, more speed.

Let's say original torrent file is 1.torrent.

[ file1 ]

systemd의 장단점에 대해서 논의하는 격렬한 글타래는 여기저기서 많이 봤는데 이 두 군데만 보시면 웬만한 의견은 다 담겨 있는 것 같습니다.

다음은 systemd 공식 프로젝트 페이지와 systemd에 빈번하게 제기되는 비판 중 오해라고 생각하는 부분에 대해서 개발자 자신이 직접 해명한 글입니다.

Blogtrottr - Delicious news, fed to your inbox

http://blogtrottr.com

Blogtrottr delivers updates from all of your favourite news, feeds, and blogs directly to your email inbox, giving you the flexibility to stay updated whilst on the go. Yummy!

	# server side. service-journal-gatewayd.socket listening on [::1]:19531, curl localhost:19531 OK.
	sudo socat -d -d \
	TCP6:[::1]:19531 \
	OPENSSL-LISTEN:10000,cert=/etc/cert.pem,cafile=/etc/cert.pem,key=/etc/key.pem,reuseaddr,fork

	# client side. first curl 'localhost:10000/entries?follow&boot' OK. second attempt hangup.
	socat \
	tcp-listen:10000,reuseaddr,fork \
	OPENSSL:do0:10000,cert=/home/user/.ssh/cert.pem,cafile=/home/user/.ssh/cert.pem,key=/home/user/.ssh/key.pem