Bittorrent is as far as I know, currently the most efficient way to -distribute content on the Internet. It is used all by all sorts of -content providers, from national TV stations like -NRK, Linux distributors like -Debian and -Ubuntu, and of course the -Internet archive. - -
Almost a month ago -a new -package adding Bittorrent support to VLC became available in -Debian testing and unstable. To test it, simply install it like -this:
- --apt install vlc-plugin-bittorrent -- -
Since the plugin was made available for the first time in Debian, -several improvements have been made to it. In version 2.2-4, now -available in both testing and unstable, a desktop file is provided to -teach browsers to start VLC when the user click on torrent files or -magnet links. The last part is thanks to me finally understanding -what the strange x-scheme-handler style MIME types in desktop files -are used for. By adding x-scheme-handler/magnet to the MimeType entry -in the desktop file, at least the browsers Firefox and Chromium will -suggest to start VLC when selecting a magnet URI on a web page. The -end result is that now, with the plugin installed in Buster og Sid, -one can visit any -Internet -Archive page with movies using a web browser and click on the -torrent link to start streaming the movie.
- -Note, there is still some misfeatures in the plugin. One is the -fact that it will hang and -block VLC -from exiting until the torrent streaming starts. Another is the -fact that it -will pick -and play a random file in a multi file torrent. This is not -always the video file you want. Combined with the first it can be a -bit hard to get the video streaming going. But when it work, it seem -to do a good job.
- -For the Debian packaging, I would love to find a good way to test -if the plugin work with VLC using autopkgtest. I tried, but do not -know enough of the inner workings of VLC to get it working. For now -the autopkgtest script is only checking if the .so file was -successfully loaded by VLC. If you have any suggestions, please -submit a patch to the Debian bug tracking system.
- -As usual, if you use Bitcoin and want to show your support of my -activities, please send Bitcoin donations to my address -15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b.
+ +Jeg er blitt spurt hva jeg synes om lansering av smittestopp-appen, +overvåkningsløsningen lansert av Folkehelseinstituttet, +Simula-senteret og Regjeringen i dag, fulgt av klare trusler fra +regjeringen om konsekvenser hvis befolkningen ikke tar den i bruk. +Rekker ikke skrive noe fyldig om temaet, men det er klart for meg at +den utraderer retten til privatliv samt utgjør en personlig +sikkerhetsrisiko for alle som tar den i bruk. Bare det er nok til at +det fremstår som en svert dårlig ide å bli med på denne "dugnaden". +Det finnes andre og bedre tilnærminger enn den valgt av FHI. Har de +valgt den for å sikre seg nok et datasett i den fremtidige +ehelse-portalen? Potensialet for misbruk av informasjon samlet inn av +appen er for stort, effekten på neste krise for klar og gevinsten for +liten.
+ +For å si det med forhenværende leder i Datatilsynet, Georg Apenes, +som skrev i en kronikk den gang Datatilsynet vernet +privatsfæren at +«SENTRALT +I en liberal forestillingsverden finner vi aksept av borgerens rett +til å kunne velge å være i fred; å være u-iakttatt, uregistrert og +anonym». Det er ikke uten grunn han startet kronikken med +«Personvern et fremmedord i enkelte av de statsorganene som samler +inn, oppbevarer og bruker personopplysninger». Der har nok +statsorganene bare blitt dårligere på 13 år.
+ +Det er jo også verdt å merke seg at personvernrådet i EU (EDPB) +mener smittestopp-appen +opererer +i strid med prinsippet om dataminimering. Også de ser at det +finnes mye bedre måter å gjøre dette på.
+ + +Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til +det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner +til min adresse +15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b. +Merk, betaling med bitcoin er ikke anonymt. :)
This morning, the new release of the -Nikita -Noark 5 core project was -announced -on the project mailing list. The free software solution is an -implementation of the Norwegian archive standard Noark 5 used by -government offices in Norway. These were the changes in version 0.2 -since version 0.1.1 (from NEWS.md): - -
-
-
- Fix typos in REL names -
- Tidy up error message reporting -
- Fix issue where we used Integer.valueOf(), not Integer.getInteger() -
- Change some String handling to StringBuffer -
- Fix error reporting -
- Code tidy-up -
- Fix issue using static non-synchronized SimpleDateFormat to avoid - race conditions -
- Fix problem where deserialisers were treating integers as strings -
- Update methods to make them null-safe -
- Fix many issues reported by coverity -
- Improve equals(), compareTo() and hash() in domain model -
- Improvements to the domain model for metadata classes -
- Fix CORS issues when downloading document -
- Implementation of case-handling with registryEntry and document upload -
- Better support in Javascript for OPTIONS -
- Adding concept description of mail integration -
- Improve setting of default values for GET on ny-journalpost -
- Better handling of required values during deserialisation -
- Changed tilknyttetDato (M620) from date to dateTime -
- Corrected some opprettetDato (M600) (de)serialisation errors. -
- Improve parse error reporting. -
- Started on OData search and filtering. -
- Added Contributor Covenant Code of Conduct to project. -
- Moved repository and project from Github to Gitlab. -
- Restructured repository, moved code into src/ and web/. -
- Updated code to use Spring Boot version 2. -
- Added support for OAuth2 authentication. -
- Fixed several bugs discovered by Coverity. -
- Corrected handling of date/datetime fields. -
- Improved error reporting when rejecting during deserializatoin. -
- Adjusted default values provided for ny-arkivdel, ny-mappe, - ny-saksmappe, ny-journalpost and ny-dokumentbeskrivelse. -
- Several fixes for korrespondansepart*. -
- Updated web GUI:
-
-
-
- Now handle both file upload and download. -
- Uses new OAuth2 authentication for login. -
- Forms now fetches default values from API using GET. -
- Added RFC 822 (email), TIFF and JPEG to list of possible file formats. -
-
The changes and improvements are extensive. Running diffstat on -the changes between git tab 0.1.1 and 0.2 show 1098 files changed, -108666 insertions(+), 54066 deletions(-).
- -If free and open standardized archiving API sound interesting to -you, please contact us on IRC -(#nikita on -irc.freenode.net) or email -(nikita-noark -mailing list).
- -As usual, if you use Bitcoin and want to show your support of my -activities, please send Bitcoin donations to my address -15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b.
+ +Det er lenge siden jeg har sett på den norske stavekontrollen, sist +jeg skrev om temaet var i 2016, og i mellomtiden har nettstedet +no.speling.org forsvunnet, og både git-depotet på Alioth og +mailman-tjenesten som hadde epostlistene for oversettelser blitt lagt +ned. Men bokmål og nynorsk trenger fortsatt stavekontroll, så etter +et par purringer fra en som har lyst til å forbedre stavekontrollen +har jeg endelig fått lagt ut ny offentlig kopi av git-depotet. Jeg +valgte gitlab foran github.. Siste utgave av stavekontrollen kan +hentes ned fra +https://gitlab.com/norwegian-language-tools/spell-norwegian. +Ingen ny versjon i denne omgang altså, bare et nytt sted å samle +forbedringer til den frie norske stavekontrollen. :) + +
Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til +det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner +til min adresse +15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b. +Merk, betaling med bitcoin er ikke anonymt. :)
I have earlier covered the basics of trusted timestamping using the -'openssl ts' client. See blog post for -2014, -2016 -and -2017 -for those stories. But some times I want to integrate the timestamping -in other code, and recently I needed to integrate it into Python. -After searching a bit, I found -the -rfc3161 library which seemed like a good fit, but I soon -discovered it only worked for python version 2, and I needed something -that work with python version 3. Luckily I next came across -the rfc3161ng library, -a fork of the original rfc3161 library. Not only is it working with -python 3, it have fixed a few of the bugs in the original library, and -it has an active maintainer. I decided to wrap it up and make it -available in -Debian, and a few days ago it entered Debian unstable and testing.
- -Using the library is fairly straight forward. The only slightly -problematic step is to fetch the required certificates to verify the -timestamp. For some services it is straight forward, while for others -I have not yet figured out how to do it. Here is a small standalone -code example based on of the integration tests in the library code:
- --#!/usr/bin/python3 - -""" - -Python 3 script demonstrating how to use the rfc3161ng module to -get trusted timestamps. - -The license of this code is the same as the license of the rfc3161ng -library, ie MIT/BSD. - -""" - -import os -import pyasn1.codec.der -import rfc3161ng -import subprocess -import tempfile -import urllib.request - -def store(f, data): - f.write(data) - f.flush() - f.seek(0) - -def fetch(url, f=None): - response = urllib.request.urlopen(url) - data = response.read() - if f: - store(f, data) - return data - -def main(): - with tempfile.NamedTemporaryFile() as cert_f,\ - tempfile.NamedTemporaryFile() as ca_f,\ - tempfile.NamedTemporaryFile() as msg_f,\ - tempfile.NamedTemporaryFile() as tsr_f: - - # First fetch certificates used by service - certificate_data = fetch('https://freetsa.org/files/tsa.crt', cert_f) - ca_data_data = fetch('https://freetsa.org/files/cacert.pem', ca_f) - - # Then timestamp the message - timestamper = \ - rfc3161ng.RemoteTimestamper('http://freetsa.org/tsr', - certificate=certificate_data) - data = b"Python forever!\n" - tsr = timestamper(data=data, return_tsr=True) - - # Finally, convert message and response to something 'openssl ts' can verify - store(msg_f, data) - store(tsr_f, pyasn1.codec.der.encoder.encode(tsr)) - args = ["openssl", "ts", "-verify", - "-data", msg_f.name, - "-in", tsr_f.name, - "-CAfile", ca_f.name, - "-untrusted", cert_f.name] - subprocess.check_call(args) - -if '__main__' == __name__: - main() -- -
The code fetches the required certificates, store them as temporary -files, timestamp a simple message, store the message and timestamp to -disk and ask 'openssl ts' to verify the timestamp. A timestamp is -around 1.5 kiB in size, and should be fairly easy to store for future -use.
+ +Today, after many months of development, a new release of
+
-
+
+
- Updated to Noark 5 versjon 5.0 API specification.
+
-
+
- Changed formatting of _links from [] to {} to match IETF draft + on JSON HAL. +
- Merged Registrering og Basisregistrering in version 4 to + combined Registrering. +
- DokumentObjekt is now subtype of ArkivEnhet. +
- Introducing new entity Arkivnotat. +
- Changed all relation keys to use /v5/ instead of /v4/. +
- Corrected to use new official relation keys when possible. +
- Renamed Sakspart to Part and connect it to Mappe, Registrering + and Dokumentbeskrivelse instead of only Saksmappe. +
- Moved Korrespondansepart connection from Journalpost to + Registrering. +
- Moved Part and Korrespondansepart from package sakarkiv to + arkivstruktur. +
- Renamed presedensstatus to presedensStatus. +
- Use new JSON content-type "application/vnd.noark5+json". +
- Updated prepopulated format list to use PRONOM codes. +
- Implemented endpoint for system information. +
- Implemented national identifiers for both file and record. +
- Implemented comments. +
- implemented sign off. +
- implemented conversion. +
+ - Improved/implemented OData search and paging support for more entities. +
- No longer exposes attribute Dokumentobjekt.referanseDokumentfil, + one should use the relation in _links instead. +
- Corrected relation keys under + https://rel.arkivverket.no/noark5/v5/api/administrasjon/, replacing + 'administrasjon' with 'admin'. +
- Fixed several security and stability issues discovered by Coverity. +
- Corrected handling ETag errors, now return code 409. +
- Improved handling of Kryssreferanse. +
- Changed internal database model to use UUID/SystemID as primary keys + in tables. +
- Changed internal database table names to use package prefix. +
- Changed time zone handling for date and datetime attributes, to be + more according to the new definition in the API specification. +
- Change revoke-token to only drop token on POST requests, not GET. +
- Updated to newer Spring version. +
- Changed primary key and URL component for metadata code lists to + use the 'kode' value instead of a SystemID. +
- Corrected implementation of Part and Sakspart. +
- Changed instance lists with subtypes (like .../registrering/ and + .../mappe/) to include the attributes and _links entries for the + subtype in the supertype lists. +
- Adjusted _links relations to make it possible to figure out the + entity of an instance using the self->href->relation key lookup + method. +
- Fixed several end points to make sure GET, PUT, POST and DELETE + match each other. +
- Updated DELETE endpoints to work with UUID based entity + identifiers. +
- Restructured code to use more common URL related constants in entry + point values and replace @RequestMapping with method specific + annotations. +
- Added first unit test code. +
- Updated web GUI to work with the updated API. +
- Changed integer fields, enforce them as numeric. +
- Rewrote and simplify metadata handling to use common service and + controller code instead of duplicating for each type. +
- Implemented the remaining metadata types. +
- Changed Country list source from Wikipedia to Debian iso-codes and + updated the list of Countries. +
- Many many corrections and improvements. + +
If free and open standardized archiving API sound interesting to +you, please contact us on IRC +(#nikita on +irc.freenode.net) or email +(nikita-noark +mailing list).
As usual, if you use Bitcoin and want to show your support of my activities, please send Bitcoin donations to my address @@ -273,7 +200,7 @@ activities, please send Bitcoin donations to my address
@@ -281,59 +208,31 @@ activities, please send Bitcoin donations to my addressA few days, I rescued a Windows victim over to Debian. To try to -rescue the remains, I helped set up automatic sync with Google Drive. -I did not find any sensible Debian package handling this -automatically, so I rebuild the grive2 source from -the Ubuntu UPD8 PPA to do the -task and added a autostart desktop entry and a small shell script to -run in the background while the user is logged in to do the sync. -Here is a sketch of the setup for future reference.
- -I first created ~/googledrive, entered the directory and -ran 'grive -a' to authenticate the machine/user. Next, I -created a autostart hook in ~/.config/autostart/grive.desktop -to start the sync when the user log in:
- -- --[Desktop Entry] -Name=Google drive autosync -Type=Application -Exec=/home/user/bin/grive-sync -
Finally, I wrote the ~/bin/grive-sync script to sync -~/googledrive/ with the files in Google Drive.
- -- --#!/bin/sh -set -e -cd ~/ -cleanup() { - if [ "$syncpid" ] ; then - kill $syncpid - fi -} -trap cleanup EXIT INT QUIT -/usr/lib/grive/grive-sync.sh listen googledrive 2>&1 | sed "s%^%$0:%" & -syncpdi=$! -while true; do - if ! xhost >/dev/null 2>&1 ; then - echo "no DISPLAY, exiting as the user probably logged out" - exit 1 - fi - if [ ! -e /run/user/1000/grive-sync.sh_googledrive ] ; then - /usr/lib/grive/grive-sync.sh sync googledrive - fi - sleep 300 -done 2>&1 | sed "s%^%$0:%" -
Feel free to use the setup if you want. It can be assumed to be -GNU GPL v2 licensed (or any later version, at your leisure), but I -doubt this code is possible to claim copyright on.
+ +On Tuesday, two scietific articles we have been working on for a +while, was finally accepted for publication into +Records +Management Journal. Still waiting for the assigned DOI urls to +start working, but you can have a look at the LaTeX originals here.
+ +The first article is +"A +record-keeping approach to managing IoT-data for government +agencies" (DOI +10.1108/RMJ-09-2019-0056) by Thomas Sødring, Petter Reinholdtsen +and David Massey, and sketches some approaches for storing measurement +data (aka Internet of Things sensor data) in a archive, thus providing +a well defined mechanism for screening and deletion of the information
+ +The second article is +"Publishing +and using record-keeping structural information in a blockchain" +(DOI +10.1108/RMJ-09-2019-0050) by Thomas Sødring, Petter Reinholdtsen +and Svein Ãlnes, where we describe a way for third parties to validate +authenticity and thus improve trust in the records kept in a +archive.
As usual, if you use Bitcoin and want to show your support of my activities, please send Bitcoin donations to my address @@ -342,7 +241,7 @@ activities, please send Bitcoin donations to my address
@@ -350,161 +249,45 @@ activities, please send Bitcoin donations to my addressIt would come as no surprise to anyone that I am interested in -bitcoins and virtual currencies. I've been keeping an eye on virtual -currencies for many years, and it is part of the reason a few months -ago, I started writing a python library for collecting currency -exchange rates and trade on virtual currency exchanges. I decided to -name the end result valutakrambod, which perhaps can be translated to -small currency shop.
- -The library uses the tornado python library to handle HTTP and -websocket connections, and provide a asynchronous system for -connecting to and tracking several services. The code is available -from -github.
- -There are two example clients of the library. One is very simple and -list every updated buy/sell price received from the various services. -This code is started by running bin/btc-rates and call the client code -in valutakrambod/client.py. The simple client look like this: - -- --import functools -import tornado.ioloop -import valutakrambod -class SimpleClient(object): - def __init__(self): - self.services = [] - self.streams = [] - pass - def newdata(self, service, pair, changed): - print("%-15s %s-%s: %8.3f %8.3f" % ( - service.servicename(), - pair[0], - pair[1], - service.rates[pair]['ask'], - service.rates[pair]['bid']) - ) - async def refresh(self, service): - await service.fetchRates(service.wantedpairs) - def run(self): - self.ioloop = tornado.ioloop.IOLoop.current() - self.services = valutakrambod.service.knownServices() - for e in self.services: - service = e() - service.subscribe(self.newdata) - stream = service.websocket() - if stream: - self.streams.append(stream) - else: - # Fetch information from non-streaming services immediately - self.ioloop.call_later(len(self.services), - functools.partial(self.refresh, service)) - # as well as regularly - service.periodicUpdate(60) - for stream in self.streams: - stream.connect() - try: - self.ioloop.start() - except KeyboardInterrupt: - print("Interrupted by keyboard, closing all connections.") - pass - for stream in self.streams: - stream.close() -
The library client loops over all known "public" services, -initialises it, subscribes to any updates from the service, checks and -activates websocket streaming if the service provide it, and if no -streaming is supported, fetches information from the service and sets -up a periodic update every 60 seconds. The output from this client -can look like this:
- -- --Bl3p BTC-EUR: 5687.110 5653.690 -Bl3p BTC-EUR: 5687.110 5653.690 -Bl3p BTC-EUR: 5687.110 5653.690 -Hitbtc BTC-USD: 6594.560 6593.690 -Hitbtc BTC-USD: 6594.560 6593.690 -Bl3p BTC-EUR: 5687.110 5653.690 -Hitbtc BTC-USD: 6594.570 6593.690 -Bitstamp EUR-USD: 1.159 1.154 -Hitbtc BTC-USD: 6594.570 6593.690 -Hitbtc BTC-USD: 6594.580 6593.690 -Hitbtc BTC-USD: 6594.580 6593.690 -Hitbtc BTC-USD: 6594.580 6593.690 -Bl3p BTC-EUR: 5687.110 5653.690 -Paymium BTC-EUR: 5680.000 5620.240 -
The exchange order book is tracked in addition to the best buy/sell -price, for those that need to know the details.
- -The other example client is focusing on providing a curses view -with updated buy/sell prices as soon as they are received from the -services. This code is located in bin/btc-rates-curses and activated -by using the '-c' argument. Without the argument the "curses" output -is printed without using curses, which is useful for debugging. The -curses view look like this:
- -- -- Name Pair Bid Ask Spr Ftcd Age - BitcoinsNorway BTCEUR 5591.8400 5711.0800 2.1% 16 nan 60 - Bitfinex BTCEUR 5671.0000 5671.2000 0.0% 16 22 59 - Bitmynt BTCEUR 5580.8000 5807.5200 3.9% 16 41 60 - Bitpay BTCEUR 5663.2700 nan nan% 15 nan 60 - Bitstamp BTCEUR 5664.8400 5676.5300 0.2% 0 1 1 - Bl3p BTCEUR 5653.6900 5684.9400 0.5% 0 nan 19 - Coinbase BTCEUR 5600.8200 5714.9000 2.0% 15 nan nan - Kraken BTCEUR 5670.1000 5670.2000 0.0% 14 17 60 - Paymium BTCEUR 5620.0600 5680.0000 1.1% 1 7515 nan - BitcoinsNorway BTCNOK 52898.9700 54034.6100 2.1% 16 nan 60 - Bitmynt BTCNOK 52960.3200 54031.1900 2.0% 16 41 60 - Bitpay BTCNOK 53477.7833 nan nan% 16 nan 60 - Coinbase BTCNOK 52990.3500 54063.0600 2.0% 15 nan nan - MiraiEx BTCNOK 52856.5300 54100.6000 2.3% 16 nan nan - BitcoinsNorway BTCUSD 6495.5300 6631.5400 2.1% 16 nan 60 - Bitfinex BTCUSD 6590.6000 6590.7000 0.0% 16 23 57 - Bitpay BTCUSD 6564.1300 nan nan% 15 nan 60 - Bitstamp BTCUSD 6561.1400 6565.6200 0.1% 0 2 1 - Coinbase BTCUSD 6504.0600 6635.9700 2.0% 14 nan 117 - Gemini BTCUSD 6567.1300 6573.0700 0.1% 16 89 nan - Hitbtc+BTCUSD 6592.6200 6594.2100 0.0% 0 0 0 - Kraken BTCUSD 6565.2000 6570.9000 0.1% 15 17 58 - Exchangerates EURNOK 9.4665 9.4665 0.0% 16 107789 nan - Norgesbank EURNOK 9.4665 9.4665 0.0% 16 107789 nan - Bitstamp EURUSD 1.1537 1.1593 0.5% 4 5 1 - Exchangerates EURUSD 1.1576 1.1576 0.0% 16 107789 nan - BitcoinsNorway LTCEUR 1.0000 49.0000 98.0% 16 nan nan - BitcoinsNorway LTCNOK 492.4800 503.7500 2.2% 16 nan 60 - BitcoinsNorway LTCUSD 1.0221 49.0000 97.9% 15 nan nan - Norgesbank USDNOK 8.1777 8.1777 0.0% 16 107789 nan -
The code for this client is too complex for a simple blog post, so -you will have to check out the git repository to figure out how it -work. What I can tell is how the three last numbers on each line -should be interpreted. The first is how many seconds ago information -was received from the service. The second is how long ago, according -to the service, the provided information was updated. The last is an -estimate on how often the buy/sell values change.
- -If you find this library useful, or would like to improve it, I -would love to hear from you. Note that for some of the services I've -implemented a trading API. It might be the topic of a future blog -post.
- -As usual, if you use Bitcoin and want to show your support of my -activities, please send Bitcoin donations to my address -15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b.
+ +Arbeidet med å lage et godt, fritt og åpent standardisert maskinelt +grensesnitt for arkivering, med tilhørende fri +programvareimplementasjon fortsetter. Jeg snakker om +Noark +5 Tjenestegrensesnitt og +Nikita. +Siste nytt etter +seminaret +for noen dager siden, er vi i Nikita-prosjektet har fått beskjed +fra Arkivverket at det blir satt ned en redaksjon for å videreutvikle +spesifikasjonen. Redaksjonen består av Mona Danielsen og Anne Sofie +Knutsen ved arkivverket, Thomas Sødring ved OsloMet, og meg selv fra +NUUG. De to sistenevnte tar seg av de åpenbare forbedringene, mens +hele redaksjonen diskuterer tvilstilfeller. Jeg håper dette vil bidra +til at vi lykkes i å gjøre denne protokollspesifikasjonen så entydig +og klar at den vil bidra til et velfungerende marked for +arkivsystemer, og sikre at programmer som trenger å snakke med +arkivsystemet kan snakke med enhver implementasjon av +API-spesifikasjonen. Nikita er den første implementasjonen, men det +bør blir flere.
+ +Det gjenstår riktig nok endel før vi er i mål, selv om svært mye +allerede er på plass. Med innspill og forslag til forbedringer fra +alle som vil ha et leverandøruavhengig og fullstendig +datamaskinlesbart grensesnitt til arkivet, så tror jeg vi vil +lykkes.
+ +Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til +det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner +til min adresse +15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b. +Merk, betaling med bitcoin er ikke anonymt. :)
Back in February, I got curious to see -if -VLC now supported Bittorrent streaming. It did not, despite the -fact that the idea and code to handle such streaming had been floating -around for years. I did however find -a standalone plugin -for VLC to do it, and half a year later I decided to wrap up the -plugin and get it into Debian. I uploaded it to NEW a few days ago, -and am very happy to report that it -entered -Debian a few hours ago, and should be available in Debian/Unstable -tomorrow, and Debian/Testing in a few days.
- -With the vlc-plugin-bittorrent package installed you should be able -to stream videos using a simple call to
- -- -It can handle magnet links too. Now if only native vlc had -bittorrent support. Then a lot more would be helping each other to -share public domain and creative commons movies. The plugin need some -stability work with seeking and picking the right file in a torrent -with many files, but is already usable. Please note that the plugin -is not removing downloaded files when vlc is stopped, so it can fill -up your disk if you are not careful. Have fun. :) - --vlc https://archive.org/download/TheGoat/TheGoat_archive.torrent -
I would love to get help maintaining this package. Get in touch if -you are interested.
- -As usual, if you use Bitcoin and want to show your support of my -activities, please send Bitcoin donations to my address -15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b.
+ +Like før julaften ble en artikkel jeg har skrevet om vedlikehold av +Noark +5 Tjenestegrensesnitt og Nikita publisert i tidsskriftet Arkivråd. +Det er basert på +min bloggpost +om samme tema som ble publisert 2019-03-11. Jeg oppdaget nettopp +at nettsiden til tidsskriftet Arkivråd er oppdatert med siste utgave, +og artikkelen dermed er tilgjengelig for alle. Du finner den i +PDF-en +til nummer 2019/3 på side 30-33. Jeg håper leserne av +tidsskriftet får lyst til å sjekke ut tjenestegrensesnittet og at +artikkelen vil gjøre det enklere for flere å bidra til en enda bedre, +klarere og mer entydig API-spesifikasjon. Det kan gjøre at +arkivsystemet +Nikita kan bli enda bedre når spesifikasjonen forbedres.
+ +Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til +det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner +til min adresse +15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b. +Merk, betaling med bitcoin er ikke anonymt. :)
I continue to explore my Kodi installation, and today I wanted to -tell it to play a youtube URL I received in a chat, without having to -insert search terms using the on-screen keyboard. After searching the -web for API access to the Youtube plugin and testing a bit, I managed -to find a recipe that worked. If you got a kodi instance with its API -available from http://kodihost/jsonrpc, you can try the following to -have check out a nice cover band.
- -- -curl --silent --header 'Content-Type: application/json' \ - --data-binary '{ "id": 1, "jsonrpc": "2.0", "method": "Player.Open", - "params": {"item": { "file": - "plugin://plugin.video.youtube/play/?video_id=LuRGVM9O0qg" } } }' \ - http://projector.local/jsonrpc
I've extended kodi-stream program to take a video source as its -first argument. It can now handle direct video links, youtube links -and 'desktop' to stream my desktop to Kodi. It is almost like a -Chromecast. :)
- -As usual, if you use Bitcoin and want to show your support of my -activities, please send Bitcoin donations to my address -15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b.
+ +En historie som har betydd endel for meg, og som jeg av og til +tenker på når hverdagen tynger, ble så vidt jeg har klart å finne ut, +skrevet av Loren +Eiseley i +flere ulike varianter. På norsk tror jeg den går under navnet +«Gutten og sjøstjernen», og jeg fant en oversettelse av en utgave av den +hos +Quora. +Fant også en +filmatisering, men den versjonen jeg liker best fant jeg +hos +Goodreads. Jeg oversatte den utgaven til norsk i går, og har lyst +til å dele den med deg: + +
+ +Mens jeg tok en pause fra skrivingen og vandret på en +øde strand ved daggry, så jeg en gutt i det fjerne bøye seg ned og +kaste noe mens han vandret mot meg over den endeløse stranden. Da han +kom nærmere, kunne jeg se at han kastet sjøstjerner, som var etterlatt +i sanden av tidevannet, tilbake i havet. Da han var nær nok spurte jeg +ham hvorfor han jobbet så hardt på denne merkelige oppgaven. Han sa at +solen snart ville stå opp og tørke sjøstjernene slik at de ville +dø.
+ +Jeg sa til ham at dette var helt meningsløst. Det var kilometer på +kilometer med strand, og det lå sjøstjerner hele veien. En person +alene kunne ikke gjøre noen forskjell. Han smilte da han plukket opp +neste sjøstjerne. Mens han kastet den så langt ut i havet som han +klarte sa han, «for denne gjør det en forskjell». Jeg droppet +skrivingen og tilbrakte resten av morgenen med å kaste +sjøstjerner.
+ +- Loren Eiseley
+
Kanskje noe du også kan ha glede av å tenke på når ting virker +håpløst?
+ +Teksten er gjengitt og oversatt basert på utgaven på Good Read, +uten tillatelse fra noen andre enn meg selv. Jeg håper på tilgivelse, +hvis det er et problem for noen, da det er gjort i beste mening. Hvis +eventuell rettighetshaver tar kontakt vil jeg fjerne teksten og i +stedet legge ut henvendelsen der teksten kreves fjernet.
+ +Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til +det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner +til min adresse +15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b. +Merk, betaling med bitcoin er ikke anonymt. :)
It might seem obvious that software created using tax money should -be available for everyone to use and improve. Free Software -Foundation Europe recentlystarted a campaign to help get more people -to understand this, and I just signed the petition on -Public Money, Public Code to help -them. I hope you too will do the same.
+ +Jeg hadde i dag gleden av å oppdage at en artikkel om +arkivsystemet +Nikita som vi skrev i sommer, nå er publisert i +Arkheion, fagtidsskrift for kommunial +arkivsektor. Du finner artikkelen på side 30-33 i nummer 2019/2, +PDF kan lastes ned fra nettstedet til tidsskriftet. Kanskje +publiseringen kan føre til at noen flere får øynene opp for verdien av +et åpent standardisert API for arkivering og søk i arkivet.
+ +Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til +det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner +til min adresse +15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b. +Merk, betaling med bitcoin er ikke anonymt. :)
A few days ago, I wondered if there are any privacy respecting -health monitors and/or fitness trackers available for sale these days. -I would like to buy one, but do not want to share my personal data -with strangers, nor be forced to have a mobile phone to get data out -of the unit. I've received some ideas, and would like to share them -with you. - -One interesting data point was a pointer to a Free Software app for -Android named -Gadgetbridge. -It provide cloudless collection and storing of data from a variety of -trackers. Its -list -of supported devices is a good indicator for units where the -protocol is fairly open, as it is obviously being handled by Free -Software. Other units are reportedly encrypting the collected -information with their own public key, making sure only the vendor -cloud service is able to extract data from the unit. The people -contacting me about Gadgetbirde said they were using -Amazfit -Bip and -Xiaomi -Band 3.
- -I also got a suggestion to look at some of the units from Garmin. -I was told their GPS watches can be connected via USB and show up as a -USB storage device with -Garmin -FIT files containing the collected measurements. While -proprietary, FIT files apparently can be read at least by -GPSBabel and the -GpxPod Nextcloud -app. It is unclear to me if they can read step count and heart rate -data. The person I talked to was using a -Garmin Forerunner -935, which is a fairly expensive unit. I doubt it is worth it for -a unit where the vendor clearly is trying its best to move from open -to closed systems. I still remember when Garmin dropped NMEA support -in its GPSes.
- -A final idea was to build ones own unit, perhaps by basing it on a -wearable hardware platforms like -the Flora Geo -Watch. Sound like fun, but I had more money than time to spend on -the topic, so I suspect it will have to wait for another time.
- -While I was working on tracking down links, I came across an -inspiring TED talk by Dave Debronkart about -being a -e-patient, and discovered the web site -Participatory -Medicine. If you too want to track your own health and fitness -without having information about your private life floating around on -computers owned by others, I recommend checking it out.
+ +When asked to accept terms of use and privacy policies that state +it will to remove rights I otherwise had or accept unreasonable terms +undermining my privacy, I choose away the service. I simply do not +have the conscience to accept terms I have no indention of upholding. +But how are the system and service providers to know how many people +they scared away? Normally I just quietly walk away. But today, I +tried a new approach. I sent the following email (removing the +specifics, as I am not out to take the specific service in question) +to the service provider I decided to not use, to at least give them +one data point on how many users are unhappy with their terms:
+ ++From: Petter Reinholdtsen ++ +
Subject: When terms of use turn users away +
To: [contact@some.site] +
Date: Sat, 07 Dec 2019 16:30:56 +0100 + +Dear [Site Owner],
+ +I was eager to test the system, as it seemed like a fun and +interesting application of [some] technology, but after reading the +terms of use and privacy policy on <URL: +https://www.[some.site]/terms-of-use > and <URL: +https://www.[some.site]/privacy-policy > I want you to know that I +decided to turn away. There were several provisions in the terms and +policy turning me off, but the final term that convinced me was being +asked to sign away my right to reverse engineer.
+ +-- +
+
Happy hacking +
Petter Reinholdtsen
I do not expect much to come out of it, but sharing it here in case +others want to give something similar a try too. If companies +discover their terms scare away enough people, perhaps they will be +improved...
As usual, if you use Bitcoin and want to show your support of my activities, please send Bitcoin donations to my address @@ -680,7 +468,7 @@ activities, please send Bitcoin donations to my address
@@ -688,36 +476,61 @@ activities, please send Bitcoin donations to my addressDear lazyweb,
- -I wonder, is there a fitness tracker / health monitor available for -sale today that respect the users privacy? With this I mean a -watch/bracelet capable of measuring pulse rate and other -fitness/health related values (and by all means, also the correct time -and location if possible), which is only provided for -me to extract/read from the unit with computer without a radio beacon -and Internet connection. In other words, it do not depend on a cell -phone app, and do make the measurements available via other peoples -computer (aka "the cloud"). The collected data should be available -using only free software. I'm not interested in depending on some -non-free software that will leave me high and dry some time in the -future. I've been unable to find any such unit. I would like to buy -it. The ones I have seen for sale here in Norway are proud to report -that they share my health data with strangers (aka "cloud enabled"). -Is there an alternative? I'm not interested in giving money to people -requiring me to accept "privacy terms" to allow myself to measure my -own health.
- -As usual, if you use Bitcoin and want to show your support of my -activities, please send Bitcoin donations to my address -15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b.
+ +Four years ago, I did a back of the envelope calculation on +how +much it would cost to store audio recordings of all the phone calls in +Norway, and came up with NOK 2.1 million / EUR 250 000 for the +year 2013. It is time to repeat the calculation using updated +numbers. The calculation is based on how much data storage is needed +for each minute of audio, how many minutes all the calls in Norway +sums up to, multiplied by the cost of data storage.
+ +The number of phone call minutes for 2018 was fetched from +the NKOM statistics +site, and for 2018, land line calls are listed as 434 238 000 +minutes, while mobile phone calls are listed with 7 542 006 000 +minutes. The total number of minutes is thus 7 976 244 000. For +simplicity, I decided to ignore any advantages in audio compression the +last four years, and continue to assume 60 Kbytes/min as the last +time.
+ +Storage prices still varies a lot, but as last time, I decide to +take a reasonable big and cheap hard drive, and double its price to +include the surrounding costs into account. A 10 TB disk cost less +than 4500 NOK / 450 EUR these days, and doubling it give 9000 NOK per +10 TB.
+ +So, with the parameters in place, lets update the old table +estimating cost for calls in a given year:
+ +Year | Call minutes | Size | Price in NOK / EUR |
---|---|---|---|
2005 | 24 000 000 000 | 1.3 PiB | 1 170 000 / 117 000 |
2012 | 18 000 000 000 | 1.0 PiB | 900 000 / 90 000 |
2013 | 17 000 000 000 | 950 TiB | 855 000 / 85 500 |
2018 | 7 976 244 000 | 445 TiB | 401 100 / 40 110 |
Both the cost of storage and the number of phone call minutes have +dropped since the last time, bringing the cost down to a level where I +guess even small organizations can afford to store the audio recording +from every phone call taken in a year in Norway. Of course, this is +just the cost of buying the storage equipment. Maintenance, need to +be included as well, but the volume of a single year is about a single +rack of hard drives, so it is not much more than I could fit in my own +home. Wonder how much the electricity bill would raise if I had that +kind of storage? I doubt it would be more than a few tens of thousand +NOK per year.
Archive
-
+
- 2020
+
-
+
+
- February (2) + +
- March (2) + +
- April (1) + +
+
+ - 2019
+
-
+
+
- January (4) + +
- February (3) + +
- March (3) + +
- May (2) + +
- June (5) + +
- July (2) + +
- August (1) + +
- September (1) + +
- November (1) + +
- December (4) + +
+
- 2018
-
@@ -751,7 +600,11 @@ activities, please send Bitcoin donations to my address
- September (3) -
- October (4) +
- October (5) + +
- November (2) + +
- December (4)
@@ -1038,7 +891,9 @@ activities, please send Bitcoin donations to my address
- bankid (4) -
- bitcoin (10) +
- betalkontant (8) + +
- bitcoin (11)
- bootsystem (17) @@ -1046,31 +901,31 @@ activities, please send Bitcoin donations to my address
- chrpath (2) -
- debian (163) +
- debian (168)
- debian edu (158)
- debian-handbook (4) -
- digistan (10) +
- digistan (11)
- dld (17) -
- docbook (25) +
- docbook (26)
- drivstoffpriser (4) -
- english (389) +
- english (413)
- fiksgatami (23) -
- fildeling (13) +
- fildeling (14) -
- freeculture (32) +
- freeculture (34)
- freedombox (9) -
- frikanalen (18) +
- frikanalen (20)
- h264 (20) @@ -1078,9 +933,9 @@ activities, please send Bitcoin donations to my address
- isenkram (16) -
- kart (20) +
- kart (22) -
- kodi (3) +
- kodi (4)
- ldap (9) @@ -1094,21 +949,23 @@ activities, please send Bitcoin donations to my address
- mesh network (8) -
- multimedia (41) +
- multimedia (42) + +
- nice free software (12) -
- nice free software (10) +
- noark5 (22) -
- norsk (299) +
- norsk (313) -
- nuug (191) +
- nuug (197) -
- offentlig innsyn (34) +
- offentlig innsyn (38)
- open311 (2) -
- opphavsrett (72) +
- opphavsrett (75) -
- personvern (107) +
- personvern (111)
- raid (2) @@ -1118,27 +975,27 @@ activities, please send Bitcoin donations to my address
- rfid (3) -
- robot (10) +
- robot (12)
- rss (1) -
- ruter (6) +
- ruter (7)
- scraperwiki (2) -
- sikkerhet (55) +
- sikkerhet (56)
- sitesummary (4)
- skepsis (5) -
- standard (56) +
- standard (70) -
- stavekontroll (6) +
- stavekontroll (7)
- stortinget (12) -
- surveillance (55) +
- surveillance (58)
- sysadmin (4) @@ -1146,13 +1003,13 @@ activities, please send Bitcoin donations to my address
- valg (9) -
- verkidetfri (13) +
- verkidetfri (17) -
- video (69) +
- video (73)
- vitenskap (4) -
- web (41) +
- web (42)