X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/89981edcb09593d3ea8a84f56e5137462aef4e5a..cded90eceb255184a3506b35d622eea9760ea993:/blog/index.rss diff --git a/blog/index.rss b/blog/index.rss index 0042b34ae4..770eae38cb 100644 --- a/blog/index.rss +++ b/blog/index.rss @@ -7,331 +7,252 @@ - Teach kids to protect their privacy - the EDRi way - http://people.skolelinux.org/pere/blog/Teach_kids_to_protect_their_privacy___the_EDRi_way.html - http://people.skolelinux.org/pere/blog/Teach_kids_to_protect_their_privacy___the_EDRi_way.html - Thu, 4 Jul 2019 19:10:00 +0200 - <p>Childs need to learn how to guard their privacy too. To help them, -<a href="https://edri.org/">European Digital Rights (EDRi)</a> created -a colorful booklet providing information on several privacy related topics, -and tips on how to protect ones privacy in the digital age.</p> - -<p>The 24 page booklet titled Digital Defenders is -<a href="https://edri.org/digital-defenders-help-kids-defend-their-privacy-around-europe">available -in several languages</a>. Thanks to the valuable contributions from -members of <a href="https://efn.no/">the Electronic Foundation Norway -(EFN)</a> and others, it is also available in Norwegian Bokmål. -If you would like to have it available in your language too, -<a href="https://hosted.weblate.org/projects/efn/privacy4kids/">contribute -via Weblate</a> and get in touch.</p> - -<p>But a funny, well written and good looking PDF do not have much -impact, unless it is read by the right audience. To increase the -chance of kids reading it, I am currently assisting EFN in getting -copies printed on paper to distribute on the street and in class -rooms. Print the booklet was made possible thanks to a small et of -great sponsors. Thank you very much to each and every one of them! I -hope to have the printed booklet ready to hand out on Tuesday, when -<a href="https://www.nuug.no/>">the Norwegian Unix Users Group</a> is -organizing <a href="https://wiki.nuug.no/sommerfest2019">its yearly -barbecue for geeks and free software zealots in the Oslo area</a>. If -you are nearby, feel free to come by and check out the party and the -booklet.</p> - -<p>If the booklet proves to be a success, it would be great to get -more sponsoring and distribute it to every kid in the country. :)</p> - -<p>As usual, if you use Bitcoin and want to show your support of my -activities, please send Bitcoin donations to my address -<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p> - - - - - Nikita og Noark 5 tjenestegrensesnittet tilbyr ny måte å tenke arkivering - http://people.skolelinux.org/pere/blog/Nikita_og_Noark_5_tjenestegrensesnittet_tilbyr_ny_m_te___tenke_arkivering.html - http://people.skolelinux.org/pere/blog/Nikita_og_Noark_5_tjenestegrensesnittet_tilbyr_ny_m_te___tenke_arkivering.html - Fri, 21 Jun 2019 11:30:00 +0200 - <p><em>av Thomas Sødring (OsloMet) og Petter Reinholdtsen (foreningen -NUUG)</em></p> - -<p>Nikita Noark 5-kjerne er et fri programvareprosjekt som tar i bruk -Arkivverkets spesifikasjonen for Noark 5 Tjenestegrensesnitt og tilbyr -et maskinlesbart grensesnitt (arkiv-API) til datasystemer som trenger å -arkivere dokumenter og informasjon. I tillegg tilbyr Nikita et -nettleserbasert brukergrensesnitt for brukere av arkivet. Dette -brukergrensesnittet benytter det maskinlesbare grensesnittet. Noark 5 -Tjenestegrensesnitt er en ny måte å tenke arkivering, med fokus på -automatisering og maskinell behandling av arkivmateriale, i stedet for -å fokusere på brukergrensesnitt. En kan tenke på -tjenestegrensesnittet som arkivet uten brukergrensesnitt, der flere -aktører kan koble til ulike brukergrensesnitt, tilpasset ulike -behov.</p> - -<p>Historisk sett gjorde Noark standarden en veldig bra jobb med -overgangen fra -papir til digital saksbehandling, men det har kommet til kort på andre -områder. Den teknologiske utviklingen har brakt oss ditt at vi kan og -skal forvente langt mer fra en arkivkjerne enn før, men det offentlig -er ofte konservativ når det gjelder nytenking. For lengst skulle -begreper som samvirke mellom datasystemer, metadata, prosess og -tjenestegrensesnitt (API) vært dominerende når systemer kjøpes -inn. Dessverre er det slik at ikke alle ønsker samvirke mellom -datasystemer velkommen, og det kan være trygt å kjøpe «svarte bokser» -der du slipper å ta stilling til hvordan man skal få flere systemer -til å virke sammen. Men IT-arkitektur er et begrep arkivfolk også -begynner å ta inn over seg.</p> - -<p>Slike systemer for å organisere metadata bør ha nettbaserte -tjenestegrensesnitt der brukergrensesnitt er tydelig adskilt fra -bakenforliggende system. Det finnes mange rapporter som snakker om å -bryte ned siloer i forvaltningen og standardiserte tjenestegrensesnitt -er det viktigste virkemiddel mot datasiloer og legger til rette for -økt samvirke mellom systemer. Et standardisert tjenestegrensesnitt er -et viktig middel for å få systemer til å samhandle da det sikrer at -ulike produsenters systemer kan snakke sammen på tvers. Samfunnet -fungerer ikke uten standardisering. Vi har alle samme strømstyrke og -kontakter i veggene og kjører alle på høyre side av veien i Norge. Det er i en slik -sammenheng at prosjektet «Noark 5 Tjenestegrensesnitt» er veldig -viktig. Hvis alle leverandører av arkivsystemer forholdt seg til et -standardisert tjenestegrensesnitt kunne kostnadene for arkivering -reduseres. Tenk deg at du er en kommune som ønsker et fagsystem integrert -med arkivløsningen din. I dag må fagsystemleverandøren vite og -tilpasse seg den spesifikke versjonen og varianten av arkivløsningen -du har. Hvis vi antar at alle leverandører av arkivkjerner har solgt -inn enten SOAP eller REST-grensesnitt til kunder de siste 10 årene og -det kommer endret versjon av grensesnittet innimellom, så gir det -veldig mange forskjellige tjenestegrensesnitt en fagsystemleverandør -må forholde seg til. Med 12 leverandører og kvartalsvise oppdateringer -kan det potensielt bli 96 ulike varianter hvert eneste år. Det sier -seg selv at det blir dyrt. Men det blir faktisk verre. Hvis du senere -ønsker å bytte ut arkivsystemet med et annet så er du avhengig å få -alle integrasjonene dine laget på nytt. Dette kan gjøre at du velger å -forbli hos en dårlig leverandør framfor å skaffe nytt system, fordi -det blir for vanskelig og dyrt å bytte. Dermed etableres det «små» -monopolsituasjoner som er vanskelig å bryte ut av. Dårlige valg i dag -kan ha uante kostander på sikt. I Nikita-prosjektet har vi kun jobbet -opp mot Noark 5 Tjenestegrensesnittet. Det har tatt en god del -ressurser å sette seg inn i spesifikasjonen og ta den i bruk, spesielt -på grunn av uklarheter i spesifikasjonen. Hvis vi måtte gjøre det -samme for alle versjoner og varianter av de forskjellige -tjenestegrensesnittene ville det blitt veldig tidkrevende og -kostbart.</p> - -<p>For deg som arkivar er digitalisering og systemer som skal virke -sammen en del av den nye hverdagen. Du har kanskje blitt skånet for -det ved å kjøpe svarte bokser, men du risikerer at du gjør deg selv en -bjørnetjeneste. Det kan oppleves som kjedelig å fortelle kolleger at -du skal sette deg inn i et tjenestegrensesnitt, men dette er faktisk -veldig spennende. Tjenestegrensesnittet er på en måte blitt levende og -det er spesielt et begrep du bør merke deg: OData. Å trekke inn deler -av OData-standarden som en måte å filtrere entitetsøk i et arkivsystem -var et nyttig trekk i prosjektet. Følgende eksempel er en -OData-spørring det går an å sende inn til en standardisert -arkivkjerne:</p> + Nikita version 0.6 released - free software archive API server + http://people.skolelinux.org/pere/blog/Nikita_version_0_6_released___free_software_archive_API_server.html + http://people.skolelinux.org/pere/blog/Nikita_version_0_6_released___free_software_archive_API_server.html + Thu, 10 Jun 2021 17:10:00 +0200 + <p>I am very pleased to be able to share with you +<a href="https://lists.nuug.no/pipermail/nikita-noark/2021-June/000576.html">the +announcement of a new version of the archiving system Nikita</a> +published by its lead developer Thomas Sødring:</p> <p><blockquote> -.../sakarkiv/journalpost?filter=contains(tittel, 'nabovarsel') + +<p>It is with great pleasure that we can announce a new release of +nikita. Version 0.6 +(<a href="https://gitlab.com/OsloMet-ABI/nikita-noark5-core">https://gitlab.com/OsloMet-ABI/nikita-noark5-core</a>). This +release makes new record keeping functionality available. This really +is a maturity release. Both in terms of functionality but also code. +Considerable effort has gone into refactoring the codebase and +simplifying the code. Notable changes for this release include:</p> + +<ul> + + <li>Significantly improved OData parsing</li> + <li>Support for business specific metadata and national identifiers</li> + <li>Continued implementation of domain model and endpoints</li> + <li>Improved testing</li> + <li>Ability to export and import from arkivstruktur.xml</li> + +</ul> + +<p>We are currently in the process of reaching an agreement with an +archive institution to publish their picture archive using nikita with +business specific metadata and we hope that we can share this with you +soon. This is an interesting project as it allows the organisation to +bring an older picture archive back to life while using the original +metadata values stored as business specific metadata. Combined with +OData means the scope and use of the archive is significantly +increased and will showcase both the flexibility and power of +Noark.</p> + +<p>I really think we are approaching a version 1.0 of nikita, even +though there is still a lot of work to be done. The notable work at +the moment is to implement access-control and full text indexing of +documents.</p> + +<p>My sincere thanks to everyone who has contributed to this +release!</p> + +<p>- Thomas</p> + +<p><strong>Release 0.6 2021-06-10 (d1ba5fc7e8bad0cfdce45ac20354b19d10ebbc7b)</strong></p> + +<ul> + + <li>Refactor metadata entity search</li> + <li>Remove redundant security configuration</li> + <li>Make OpenAPI documentation work</li> + <li>Change database structure / inheritance model to a more sensible approach</li> + <li>Make it possible to move entities around the fonds structure</li> + <li>Implemented a number of missing endpoints</li> + <li>Make sure yml files are in sync</li> + <li>Implemented/finalised storing and use of + <ul> +     <li>Business Specific Metadata</li> +     <li>Norwegian National Identifiers</li> +     <li>Cross Reference</li> +     <li>Keyword</li> +     <li>StorageLocation</li> +     <li>Author</li> +     <li>Screening for relevant objects</li> +     <li>ChangeLog</li> +     <li>EventLog</li> + </ul></li> + <li>Make generation of updated docker image part of successful CI pipeline</li> + <li>Implement pagination for all list requests + <ul> +     <li>Refactor code to support lists</li> +     <li>Refactor code for readability</li> +     <li>Standardise the controller/service code</li> + </ul></li> + <li>Finalise File->CaseFile expansion and Record->registryEntry/recordNote +expansion</li> + <li>Improved Continuous Integration (CI) approach via gitlab</li> + <li>Changed conversion approach to generate tagged PDF documents</li> + <li>Updated dependencies + <ul> +     <li>For security reasons</li> +     <li>Brought codebase to spring-boot version 2.5.0</li> +     <li>Remove import of necessary dependencies</li> +     <li>Remove non-used metrics classes</li> + </ul></li> + <li>Added new analysis to CI including</li> + <li>Implemented storing of Keyword</li> + <li>Implemented storing of Screening and ScreeningMetadata</li> + <li>Improved OData support + <ul> +     <li>Better support for inheritance in queries where applicable</li> +     <li>Brought in more OData tests</li> +     <li>Improved OData/hibernate understanding of queries</li> +     <li>Implement $count, $orderby</li> +     <li>Finalise $top and $skip</li> +     <li>Make sure & is used between query parameters</li> + </ul></li> + <li>Improved Testing in codebase + <ul> +     <li>A new approach for integration tests to make test more readable</li> +     <li>Introduce tests in parallel with code development for TDD approach</li> +     <li>Remove test that required particular access to storage</li> + </ul></li> + <li>Implement case-handling process from received email to case-handler + <ul> +     <li>Develop required GUI elements (digital postroom from email)</li> +     <li>Introduced leader, quality control and postroom roles</li> + </ul></li> + <li>Make PUT requests return 200 OK not 201 CREATED</li> + <li>Make DELETE requests return 204 NO CONTENT not 200 OK</li> + <li>Replaced 'oppdatert*' with 'endret*' everywhere to match latest spec</li> + <li>Upgrade Gitlab CI to use python > 3 for CI scripts</li> + <li>Bug fixes + <ul> +     <li>Fix missing ALLOW</li> +     <li>Fix reading of objects from jar file during start-up</li> +     <li>Reduce the number of warnings in the codebase</li> +     <li>Fix delete problems</li> +     <li>Make better use of cascade for "leaf" objects</li> +     <li>Add missing annotations where relevant</li> +     <li>Remove the use of ETAG for delete</li> +     <li>Fix missing/wrong/broken rels discovered by runtest</li> +     <li>Drop unofficial convertFil (konverterFil) end point</li> +     <li>Fix regex problem for dateTime</li> +     <li>Fix multiple static analysis issues discovered by coverity</li> +     <li>Fix proxy problem when looking for object class names</li> +     <li>Add many missing translated Norwegian to English (internal) +attribute/entity names</li> +     <li>Change UUID generation approach to allow code also set a value</li> +     <li>Fix problem with Part/PartParson</li> +     <li>Fix problem with empty OData search results</li> +     <li>Fix metadata entity domain problem</li> + </ul></li> + <li>General Improvements + <ul> +     <li>Makes future refactoring easier as coupling is reduced</li> +     <li>Allow some constant variables to be set from property file</li> +     <li>Refactor code to make reflection work better across codebase</li> +     <li>Reduce the number of @Service layer classes used in @Controller +classes</li> +     <li>Be more consistent on naming of similar variable types</li> +     <li>Start printing rels/href if they are applicable</li> +     <li>Cleaner / standardised approach to deleting objects</li> +     <li>Avoid concatenation when using StringBuilder</li> +     <li>Consolidate code to avoid duplication</li> +     <li>Tidy formatting for a more consistent reading style across +similar class files</li> +     <li>Make throw a log.error message not an log.info message</li> +     <li>Make throw print the log value rather than printing in multiple +places</li> +     <li>Add some missing pronom codes</li> +     <li>Fix time formatting issue in Gitlab CI</li> +     <li>Remove stale / unused code</li> +     <li>Use only UUID datatype rather than combination String/UUID for systemID</li> +     <li>Mark variables final and @NotNull where relevant to indicate +intention</li> + </ul></li> + <li>Change Date values to DateTime to maintain compliance with Noark 5 +standard</li> + <li>Domain model improvements using Hypersistence Optimizer + <ul> +     <li>Move @Transactional from class to methods to avoid borrowing the JDBC Connection unnecessarily</li> +     <li>Fix OneToOne performance issues</li> +     <li>Fix ManyToMany performance issues</li> +     <li>Add missing bidirectional synchronization support</li> +     <li>Fix ManyToMany performance issue</li> + </ul></li> + <li>Make List<> and Set<> use final-keyword to avoid potential problems +during update operations</li> + <li>Changed internal URLs, replaced "hateoas-api" with "api".</li> + <li>Implemented storing of Precedence.</li> + <li>Corrected handling of screening.</li> + <li>Corrected _links collection returned for list of mixed entity types +to match the specific entity.</li> + <li>Improved several internal structures.</li> +</ul> + </blockquote></p> -<p>Spørringen over vil hente en liste av alle dine journalposter der -tittelen til journalposten inneholder ordet 'nabovarsel'. Alle -leverandører som implementerer tjenestegrensesnittet vil måtte tilby -dette. Det betyr at hvis du lærer dette språket for et system, vil det -være gjeldende for alle. Dette er egentlig en ny måte å søke i -arkivdatabasen på og vil være svært nyttig, for eksempel kan søk i -tjenestegrensesnittet antagelig brukes til å hente ut offentlig -postjournal. I arkivverden pleier vi å like teknologier som er -menneskelesbart, da vet vi det er enkelt og nyttig! OData er også -viktig fordi det kan bli en ny måte å svare innsynsforespørsler på i -tråd med offentlighetsloven § 9, der retten til å kreve innsyn i -sammenstilling fra databaser er nedfelt. I dag ser vi -forvaltningsorganer som avviser slike krav fordi det «ikke kan gjøres -med enkle framgangsmåter». Bruken av OData i tjenestegrensesnittet, -sammen med maskinlesbar markeringsformater kan være et viktig bidrag -til å åpne arkivene i tråd med prinsippene om en åpen og transparent -forvaltning.</p> - -<p>Standardisering er viktig fordi det <em>kan</em> sikre samvirke. -Men den effekten kommer kun hvis standardiseringen sikrer at alle -forstår standarden på samme måte, dvs. at den er entydig og klar. En -god måte å sikre en entydig og klar spesifikasjon er ved å kreve at -det finnes minst to ulike implementasjoner som følger spesifikasjonen -og som kan snakke sammen, det vil si at de snakker samme språk, slik -IETF krever for alle sine standarder, før spesifikasjonen anses å være -ferdig. Tilbakemelding fra miljøet forteller at både leverandører og -kunder har et avslappet forhold til Noark 5 Tjenestegrensesnitt og det -er så langt kun Evry som har visst offentlig at de har en -implementasjon av tjenestegrensesnittet. Evry, HK Data og Fredrikstad -kommune er igang med et pilotprosjekt på Noark 5 -Tjenestegrensesnitt. For å redusere kostnadene for samvirkende -datasystemer betraktelig, er det veldig viktig at vi kommer i en -situasjon der alle leverandører har sine egne implementasjoner av -tjenestegrensesnittet, og at disse oppfører seg likt og i tråd med det -som er beskrevet i spesifikasjonen.</p> - -<p>Det er her fri programvare spiller en viktig rolle. Med en uklar -standard blir det som en polsk riksdag, der ingenting fungerer. Nikita -er en fri programvareimplementasjon av tjenestegrensesnitt og kan -fungere som teknisk referanse slik at leverandører enklere kan se og -forstå hvordan standarden skal tolkes. Vi har i Nikitaprosjektet -erfart å ende opp med vidt forskjellige tolkninger når -prosjektmedlemmene leser spesifikasjonsteksten, en effekt av en uklar -spesifikasjon. Men Nikitaprosjektet har også utviklet et test-program -som sjekker om et tjenestegrensesnitt er i samsvar med standarden, og -prosjektet bruker det hele tiden for å sikre at endringer og -forbedringer fungerer. Egenerklæringsskjemaenes dager kan være talte! -Snart vil du selv kunne teste hver oppdatering av arkivsystemet med en -uavhengig sjekk.</p> - -<p>Fri programvare representerer en demokratisering av kunnskap der -tolkning- og innlåsingsmakt flyttes fra leverandør til allmenheten. -Med fri programvare har du en litt annerledes verdikjede, der selve -produktet ikke holdes hemmelig for å tjene penger, slik en gjør med -ufri programvare og skytjenester som ikke bruker fri programvare, men -du kan tjene penger på andre deler av verdikjeden. Med fri programvare -kan samfunnet betale for å videreutvikle nyttig -fellesfunksjonalitet.</p> - -<p>Nikita er en fri programvareimplementasjon av tjenestegrensesnittet og -kan fungere som en referanseimplementasjon dersom det er ønskelig. -Alle har lik tilgang til koden og det koster ingenting å ta den i bruk -og utforske det. Nikitaprosjektet ønsker tjenestegrensesnittet -velkommen og stiller veldig gjerne opp i diskusjoner om tolkning av -tjenestegrensesnittet. Nikita er bygget på moderne -programmeringsrammeverk og utviklet i full åpenhet. Men Nikita er ikke -noe du kan kjøpe. Nikita er først og fremst et verktøy for forsking og -utvikling laget for å fremme forskning på arkivfeltet. Systemer som -virker sammen har alltid vært hovedfokus og vil være det fremover. -Det brukes som undervisningsverktøy der studentene ved OsloMet lærer -om administrativt oppsett, saksbehandling, uttrekk og samvirkende -datasystemer. Det brukes også som forskningsobjekt der vi ser på -import av dokumentsamlinger, bruk av blokkjede og andre nyskapende -måter å tenke arkiv på. Det er dog helt greit om andre tar Nikita og -pakker det for å selge det som produkt. Forvaltningsorganer med -sterke drift- og utviklingsmiljøer kan også se på Nikita og utforske -hva som er mulig. Dette kan de gjøre uten å måtte betale for -bruksrettigheter eller tilgang til konsulenter. Men arkivering blir -ikke gratis på grunn av Nikita. Det trengs fortsatt folk med -kompetanse og tid til å ta i bruk Nikita.</p> - -<p>Nikita har nylig kommet med en ny utgave, den sjette i rekken. -Systemet er ikke ferdig, mest på grunn av at API-spesifikasjonen for -Noark 5 Tjenestegrensesnitt ikke er ferdig, men allerede i dag kan en -bruke Nikita som arkiv. Vi har laget eksempelsystem for å importere -data fra deponi-XML og slik gjøre eksisterende arkivdata tilgjengelig -via et API. Vi har også laget en testklient som importerer epost inn -i arkivet med vedlegg der epostenes trådinformasjon brukes til å legge -eposttråder i samme arkivmappe, og en annen testklient som henter -epost ut av en arkivmappe på mbox-format slik at en vanlig epostklient -kan brukes til å lese igjennom og svare på epostene i en -arkivmappe. De som vil ta en titt på Nikita kan besøke -<a href="https://nikita.oslomet.no">https://nikita.oslomet.no</a> og -logge inn med brukernavn «admin@example.com» og passord «password». -Dette gir tilgang til det forenklede brukergrensesnittet som brukes -til undervisning. De som heller vil ta en titt under panseret kan -besøke -<a href="https://nikita.oslomet.no/browse.html">https://nikita.oslomet.no/browse.html</a> -og der se hvordan API-et fungerer mer i detalj. Innloggingsdetaljer -her er det samme som for brukergrensesnittet.</p> - -<p>Fremover er fokuset på forbedring av spesifikasjonen Noark 5 -Tjenestegrensesnitt. De som skrev tjenestegrensesnittet gjorde et -interessant og framtidsrettet grep, de skilte sak fra arkiv. -Tjenestegrensesnittet består av flere "pakker", der noen er -grunnleggende mens andre bygger på de grunnleggende pakkene. Pakkene -som er beskrevet så langt heter «arkivstruktur», «sakarkiv», -«administrasjon», «loggogsporing» og «moeter» (dessverre -<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/pull/120">planlagt -fjernet</a> i første utgave). Etter hvert håper vi å utforske -prosses- og metadatabeskrivelser til flere fagområder og bidra til at -tjenestegrensesnittet kan legge til flere pakker som «byggarkiv», -«barnevern», «personal», «barnehage», der arkivfaglig metadata- og -dokumentasjonsbehov er kartlagt og standardisert.</p> - -<p>Nikita utvikles av en liten prosjektgruppe, og vi er alltid -interessert å bli flere. Hvis en åpen, fri og standardisert tilnærming -til arkivering høres interessant ut, bli med oss på veien videre. Vi -er tilstede på IRC-kanalen #nikita hos FreeNode (tilgjengelig via -nettleser på -<a href="https://webchat.freenode.net?channels=#nikita">https://webchat.freenode.net?channels=#nikita</a>), -og har en e-postliste nikita-noark@nuug.no hos NUUG (tilgjengelig for -påmelding og arkiv på -<a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">https://lists.nuug.no/mailman/listinfo/nikita-noark</a>) -der en kan følge med eller være med oss på den spennende veien videre. -Spesifikasjonen for Noark 5 Tjenestegrensesnitt vedlikeholdes på -github, -<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/">https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/</a>.</p> +<p>If free and open standardized archiving API sound interesting to +you, please contact us on IRC +(<a href="irc://irc.oftc.net/%23nikita">#nikita on +irc.oftc.net</a>) or email +(<a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">nikita-noark +mailing list</a>).</p> -<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 +<p>As usual, if you use Bitcoin and want to show your support of my +activities, please send Bitcoin donations to my address <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p> - Jami/Ring, finally functioning peer to peer communication client - http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html - http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html - Wed, 19 Jun 2019 08:50:00 +0200 - <p>Some years ago, in 2016, I -<a href="http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html">wrote -for the first time about</a> the Ring peer to peer messaging system. -It would provide messaging without any central server coordinating the -system and without requiring all users to register a phone number or -own a mobile phone. Back then, I could not get it to work, and put it -aside until it had seen more development. A few days ago I decided to -give it another try, and am happy to report that this time I am able -to not only send and receive messages, but also place audio and video -calls. But only if UDP is not blocked into your network.</p> - -<p>The Ring system changed name earlier this year to -<a href="https://en.wikipedia.org/wiki/Jami_(software)">Jami</a>. I -tried doing web search for 'ring' when I discovered it for the first -time, and can only applaud this change as it is impossible to find -something called Ring among the noise of other uses of that word. Now -you can search for 'jami' and this client and -<a href="https://jami.net/">the Jami system</a> is the first hit at -least on duckduckgo.</p> - -<p>Jami will by default encrypt messages as well as audio and video -calls, and try to send them directly between the communicating parties -if possible. If this proves impossible (for example if both ends are -behind NAT), it will use a central SIP TURN server maintained by the -Jami project. Jami can also be a normal SIP client. If the SIP -server is unencrypted, the audio and video calls will also be -unencrypted. This is as far as I know the only case where Jami will -do anything without encryption.</p> - -<p>Jami is available for several platforms: Linux, Windows, MacOSX, -Android, iOS, and Android TV. It is included in Debian already. Jami -also work for those using F-Droid without any Google connections, -while Signal do not. -<a href="https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Protocol">The -protocol</a> is described in the Ring project wiki. The system uses a -distributed hash table (DHT) system (similar to BitTorrent) running -over UDP. On one of the networks I use, I discovered Jami failed to -work. I tracked this down to the fact that incoming UDP packages -going to ports 1-49999 were blocked, and the DHT would pick a random -port and end up in the low range most of the time. After talking to -the developers, I solved this by enabling the dhtproxy in the -settings, thus using TCP to talk to a central DHT proxy instead of - -peering directly with others. I've been told the developers are -working on allowing DHT to use TCP to avoid this problem. I also ran -into a problem when trying to talk to the version of Ring included in -Debian Stable (Stretch). Apparently the protocol changed between -beta2 and the current version, making these clients incompatible. -Hopefully the protocol will not be made incompatible in the -future.</p> - -<p>It is worth noting that while looking at Jami and its features, I -came across another communication platform I have not tested yet. The -<a href="https://en.wikipedia.org/wiki/Tox_(protocol)">Tox protocol</a> -and <a href="https://tox.chat/">family of Tox clients</a>. It might -become the topic of a future blog post.</p> - + VLC bittorrent plugin in Bullseye, saved by the bell? + http://people.skolelinux.org/pere/blog/VLC_bittorrent_plugin_in_Bullseye__saved_by_the_bell_.html + http://people.skolelinux.org/pere/blog/VLC_bittorrent_plugin_in_Bullseye__saved_by_the_bell_.html + Sat, 1 May 2021 11:00:00 +0200 + <p>Yesterday morning I got a warning call from the Debian quality +control system that +<a href="https://tracker.debian.org/pkg/vlc-plugin-bittorrent">the VLC +bittorrent plugin</a> was due to be removed because of a release +critical bug in one of its dependencies. As you might remember, this +plugin make VLC able to stream videos directly from a bittorrent +source using both torrent files and magnet links, similar to using a +HTTP source. I believe such protocol support is a vital feature in +VLC, allowing efficient streaming from sources such at the almost 7 +million movies in <a href="https://archive.org/">the Internet +Archive</a>.</p> + +<p>The dependency was the unmaintained +<a href="https://tracker.debian.org/pkg/libtorrent-rasterbar">libtorrent-rasterbar</a> +package, and <a href="https://bugs.debian.org/987306">the bug in +question</a> blocked its python library from working properly. As I +did not want Bullseye to release without bittorrent support in VLC, I +set out to check out the status, and track down a fix for the problem. +Luckily the issue had already been identified and fixed upstream, +providing everything needed. All I needed to do was to fetch the +Debian git repository, extract and trim the patch from upstream and +apply it to the Debian package for upload.</p> + +<p>The fixed library was uploaded yesterday evening. But that is not +enough to get it into Bullseye, as Debian is currently in package +freeze to prepare for a new next stable release. Only non-critical +packages with +<a href="https://wiki.debian.org/ContinuousIntegration/autopkgtest">autopkgtest +setup</a> included, in other words able to validate automatically that +the package is working, are allowed to migrate automatically into the +next release at this stage. And the unmaintained libtorrent-rasterbar +lack such testing, and thus needed a manual override. I am happy to +report that such manual override was approved a few minutes ago, thus +increasing significantly the chance of VLC bittorrent streaming being +available out of the box also for Debian/Buster users. A bit too +close shave for my liking, as the Bullseye release is most likely just +a few days away, and this did feel like the package was saved by the +bell. I am so glad the warning email showed up in time for me to +handle the issue, and a big thanks go to the Debian Release team for +the quick feedback on +<a href="irc://irc.debian.org/%23debian-release">#debian-release</a> +and their <a href="https://bugs.debian.org/987865">swift +unblocking</a>.</p> + <p>As usual, if you use Bitcoin and want to show your support of my activities, please send Bitcoin donations to my address <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p> @@ -339,187 +260,290 @@ activities, please send Bitcoin donations to my address - More sales number for my Free Culture paper editions (2019-edition) - http://people.skolelinux.org/pere/blog/More_sales_number_for_my_Free_Culture_paper_editions__2019_edition_.html - http://people.skolelinux.org/pere/blog/More_sales_number_for_my_Free_Culture_paper_editions__2019_edition_.html - Tue, 11 Jun 2019 16:05:00 +0200 - <p>The first book I published, -<a href="http://www.free-culture.cc/">Free Culture by Lawrence -Lessig</a>, is still selling a few copies. Not a lot, but enough to -have contributed slightly over $500 to the <a -href="https://creativecommons.org/">Creative Commons Corporation</a> -so far. All the profit is sent there. Most books are still sold via -Amazon (83 copies), with Ingram second (49) and Lulu (12) and Machette (7) as -minor channels. Bying directly from Lulu bring the largest cut to -Creative Commons. The English Edition sold 80 copies so far, the -French 59 copies, and Norwegian only 8 copies. Nothing impressive, -but nice to see the work we put down is still being appreciated. The -ebook edition is available for free from -<a href="https://github.com/petterreinholdtsen/free-culture-lessig">Github</a>.</p> - -<table border="0"> -<tr><th rowspan="2" valign="bottom">Title / language</th> -<th colspan="7">Quantity</th></tr> -<tr> -<th>2016 jan-jun</th> -<th>2016 jul-dec</th> -<th>2017 jan-jun</th> -<th>2017 jul-dec</th> -<th>2018 jan-jun</th> -<th>2018 jul-dec</th> -<th>2019 jan-may</th> -</tr> - -<tr> - <td><a href="http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html">Culture Libre / French</a></td> - <td align="right">3</td> - <td align="right">6</td> - <td align="right">19</td> - <td align="right">11</td> - <td align="right">7</td> - <td align="right">6</td> - <td align="right">7</td> -</tr> - -<tr> - <td><a href="http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html">Fri kultur / Norwegian</a></td> - <td align="right">7</td> - <td align="right">1</td> - <td align="right">0</td> - <td align="right">0</td> - <td align="right">0</td> - <td align="right">0</td> - <td align="right">0</td> -</tr> - -<tr> - <td><a href="http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html">Free Culture / English</a></td> - <td align="right">14</td> - <td align="right">27</td> - <td align="right">16</td> - <td align="right">9</td> - <td align="right">3</td> - <td align="right">7</td> - <td align="right">3</td> -</tr> - -<tr> - <td>Total</td> - <td align="right">24</td> - <td align="right">34</td> - <td align="right">35</td> - <td align="right">20</td> - <td align="right">10</td> - <td align="right">13</td> - <td align="right">10</td> -</tr> - -</table> - -<p>It is fun to see the French edition being more popular than the -English one.</p> - -<p>If you would like to translate and publish the book in your native -language, I would be happy to help make it happen. Please get in -touch.</p> + Updated Valutakrambod, now also with information from NBX + http://people.skolelinux.org/pere/blog/Updated_Valutakrambod__now_also_with_information_from_NBX.html + http://people.skolelinux.org/pere/blog/Updated_Valutakrambod__now_also_with_information_from_NBX.html + Sat, 27 Feb 2021 13:30:00 +0100 + <p>I have neglected the Valutakrambod library for a while, but decided +this weekend to give it a face lift. I fixed a few minor glitches in +several of the service drivers, where the API had changed since I last +looked at the code. I also added support for fetching the order book +from the newcomer Norwegian Bitcoin Exchange.</p> + +<p>I also decided to migrate the project from github to gitlab in the +process. If you want a python library for talking to various currency +exchanges, check out +<a href="https://gitlab.com/petterreinholdtsen/valutakrambod">code for +valutakrambod</a>.</p> + +<p>This is what the output from '<tt>bin/btc-rates-curses -c</tt>' +looked like a few minutes ago:</p> + +<p><blockquote><pre> + Name Pair Bid Ask Spread Ftcd Age Freq + Bitfinex BTCEUR 39229.0000 39246.0000 0.0% 44 44 nan + Bitmynt BTCEUR 39071.0000 41048.9000 4.8% 43 74 nan + Bitpay BTCEUR 39326.7000 nan nan% 39 nan nan + Bitstamp BTCEUR 39398.7900 39417.3200 0.0% 0 0 1 + Bl3p BTCEUR 39158.7800 39581.9000 1.1% 0 nan 3 + Coinbase BTCEUR 39197.3100 39621.9300 1.1% 38 nan nan + Kraken+BTCEUR 39432.9000 39433.0000 0.0% 0 0 0 + Paymium BTCEUR 39437.2100 39499.9300 0.2% 0 2264 nan + Bitmynt BTCNOK 409750.9600 420516.8500 2.6% 43 74 nan + Bitpay BTCNOK 410332.4000 nan nan% 39 nan nan + Coinbase BTCNOK 408675.7300 412813.7900 1.0% 38 nan nan + MiraiEx BTCNOK 412174.1800 418396.1500 1.5% 34 nan nan + NBX BTCNOK 405835.9000 408921.4300 0.8% 33 nan nan + Bitfinex BTCUSD 47341.0000 47355.0000 0.0% 44 53 nan + Bitpay BTCUSD 47388.5100 nan nan% 39 nan nan + Coinbase BTCUSD 47153.6500 47651.3700 1.0% 37 nan nan + Gemini BTCUSD 47416.0900 47439.0500 0.0% 36 336 nan + Hitbtc BTCUSD 47429.9900 47386.7400 -0.1% 0 0 0 + Kraken+BTCUSD 47401.7000 47401.8000 0.0% 0 0 0 + Exchangerates EURNOK 10.4012 10.4012 0.0% 38 76236 nan + Norgesbank EURNOK 10.4012 10.4012 0.0% 31 76236 nan + Bitstamp EURUSD 1.2030 1.2045 0.1% 2 2 1 + Exchangerates EURUSD 1.2121 1.2121 0.0% 38 76236 nan + Norgesbank USDNOK 8.5811 8.5811 0.0% 31 76236 nan +</pre></blockquote></p> + +<p>Yes, I notice the negative spread on Hitbtc. Either I fail to +understand their Websocket API or they are sending bogus data. I've +seen the same with Kraken, and suspect there is something wrong with +the data they send.</p> + +<p>As usual, if you use Bitcoin and want to show your support of my +activities, please send Bitcoin donations to my address +<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p> - Official MIME type "text/vnd.sosi" for SOSI map data - http://people.skolelinux.org/pere/blog/Official_MIME_type__text_vnd_sosi__for_SOSI_map_data.html - http://people.skolelinux.org/pere/blog/Official_MIME_type__text_vnd_sosi__for_SOSI_map_data.html - Tue, 4 Jun 2019 09:20:00 +0200 - <p>Just 15 days ago, -<ahref="http://people.skolelinux.org/pere/blog/MIME_type__text_vnd_sosi__for_SOSI_map_data.html">I -mentioned</a> my submission to IANA to register an official MIME type -for the SOSI vector map format. This morning, just an hour ago, I was -notified that -<a href="https://www.iana.org/assignments/media-types/text/vnd.sosi">the -MIME type "text/vnd.sosi"</a> is registered for this format. In -addition to this registration, my -<a href="https://github.com/file/file/blob/master/magic/Magdir/sosi">file(1) -patch for a pattern matching rule for SOSI files</a> has been accepted -into the official source of that program (pending a new release), and -I've been told by the team behind -<a href="https://www.nationalarchives.gov.uk/PRONOM/">PRONOM</a> that -the SOSI format will be included in the next release of PRONOM, which -they plan to release this summer around July.</p> - -<p>I am very happy to see all of this fall into place, for use by -<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/">the -Noark 5 Tjenestegrensesnitt</a> implementations.</p> + Boken «Hvordan knuse overvåkningskapitalismen» lanseres på norsk + http://people.skolelinux.org/pere/blog/Boken__Hvordan_knuse_overv_kningskapitalismen__lanseres_p__norsk.html + http://people.skolelinux.org/pere/blog/Boken__Hvordan_knuse_overv_kningskapitalismen__lanseres_p__norsk.html + Tue, 26 Jan 2021 19:10:00 +0100 + <p>Etter intenst arbeid over mange måneder er endelig den norske +utgaven av «Hvordan knuse overvåkningskapitalismen» av Cory Doctorow +ferdig og klar til å glede millioner av lesere over hele verden. +Følgende pressemelding ble nettopp sendt ut til norske redaksjoner: + +<blockquote> + +<p><strong>Hva gjør stordata med oss, og hvordan gjør algoritmene +«fake news» til realiter?</strong></p> + +<p>Nå foreligger en viktig bok om temaet også på norsk. Boken klargjør +og foreslår hvordan vi selv som enkeltpersoner, men også nasjonalt og +internasjonalt kan bekjempe stordatakonsentrasjonene; +«overvåkingskapitalismen». Boken er «Hvordan knuse +overvåkingskapitalismen» av dr. Cory Doctorow. Den engelske +bokutgivelsen kom for noen dager siden og lanseres med et Webinar +torsdag 2021-01-28. Doctorow besøkte Norge og NUUG i desember med sin +presentasjon Monopoly, Not Mind Control: What's Really Happening With +"Surveillance Capitalism".</p> + +<p>I funn etter funn, eksempel etter eksempel, gjennomgår og +analyserer dr. Doctorow de utfordringer vi møter i større og større +omfang. Ikke bare i USA, men også her hjemme.</p> + +<p>Cory Doctorow er en britisk-kanadisk forfatter, journalist og +aktivist, kjent for sine science fiction-romaner, for arbeidet for +Creative Commons-bevegelsen, og for sine bidrag til reform av +opphavsretten. Han er både æresdoktor og gjesteforeleser i +datavitenskap ved Open University i UK, konsulent for Electronic +Frontier Foundation, og godt kjent for innsiktsfullt å kommentere og +skrive om digital utvikling.</p> + +<p>Boken lanseres nå på norsk, både som ebok og på papir, oversatt av +en dugnadsgjeng ledet av Petter Reinholdtsen.</p> + +<p>Boken reiser noen helt grunnleggende og samfunnskritiske spørsmål: +Hva fører det til når store deler av Internettet domineres av få store +aktører og deres styringsverktøy og algoritmer?</p> + +<p>Som individer bør vi være opptatt at grenser blir satt og håndhevet +- grenser for overvåkning av individet, for utøvelse av kommersiell +og politisk påvirkning, og for monopoldannelser i +dataverdenen. Slik grensesetting styrker personvernet.</p> + +<p>Konkurransetilsynet har ansvaret for at konkurranselovens § 11 skal +forby «et dominerende foretak for utilbørlig å utnytte og misbruke +sin dominerende stilling». Et tilsvarende forbud omfattes også av +EØS-avtalens artikkel 54. Boken går i detalj om serien av +innskrenkninger vi møter i valgfriheten, innskrenkninger som denne +lovgivningen nettopp skal forhindre. Håndhevelse av en slik lovgivning +er også til fordel for mindre næringsdrivende som uten dette får +begrenset sine faktiske eller potensielle muligheter for vekst og +etablering. «Slik atferd kan utgjøre et misbruk og kan ta ulike +former», skriver Konkurransetilsynet.</p> + +<p>Cory Doctorow går i sin bok lengre enn det med sine mange eksempler +på forhold det burde vært grepet inn mot.</p> + +<p>«Boken bør bidra til et sterkere engasjemen fra voktere av +Inter­nettet nasjonalt og internasjonalt - EU medregnet» sier +oversetter Ole-Erik Yrvin og fortsetter: «Vi har derfor +<a href="http://people.skolelinux.org/pere/blog/images/2021-01-26-knus-overvaakningskapitalismen-helleland.pdf">allerede +tatt opp bokens forslag</a> direkte med Distrikts- og +digitaliseringsminister Linda Hofstad Helleland (H) og +Konkurransetilsynet slik at de kan følges opp.»</p> + +<p>«Også Norge bør innta en pådriverrolle i denne utviklingen», sier +Petter Reinholdtsen. «Tiden er knapp, og tilsynsmyndighetene må få +de verktøy og de ressurser de trenger for at vi her hjemme skal oppnå +nødvendige resultater. Dette gjelder ikke bare vår egen generasjon; +det gjelder alle generasjoner fremover», avslutter Petter +Reinholdsen.</p> + +<p>Kontaktinformasjon:</p> -<p>As usual, if you use Bitcoin and want to show your support of my -activities, please send Bitcoin donations to my address -<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p> +<ul> + +<li>Ole-Erik Yrvin, oeyrvin (at) gmail.com, +47 46500450</li> + +<li>Petter Reinholdtsen, pere (at) hungry.com</li> + +</ul> + +<p>Relevante lenker:<p> + +<ul> + +<li>«Hvordan knuse overvåkingskapitalismen» kan bestilles på papir, +som ebok eller leses på nett via +<a href="http://www.hungry.com/~pere/publisher/">http://www.hungry.com/~pere/publisher/</a>.</li> + +<li>Opptak av NUUG-møtet Monopoly, Not Mind Control: What's Really +Happening With "Surveillance Capitalism" med Cory Doctorow, +<a href="https://www.nuug.no/aktiviteter/20201208-doctorow/">https://www.nuug.no/aktiviteter/20201208-doctorow/</a>.</li> + +<li>Påmelding til webinar som lanserer den engelske utgaven kan gjøres +via +<a href="https://craphound.com/category/destroy/">https://craphound.com/category/destroy/</a>.</li> + +<li>Cory Doctorows nettsted er +<a href="https://craphound.com/">https://craphound.com/</a>.</li> + +</ul> + +</blockquote> + +<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 +<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>. +Merk, betaling med bitcoin er ikke anonymt. :)</p> - The space rover coquine, or how I ended up on the dark side of the moon - http://people.skolelinux.org/pere/blog/The_space_rover_coquine__or_how_I_ended_up_on_the_dark_side_of_the_moon.html - http://people.skolelinux.org/pere/blog/The_space_rover_coquine__or_how_I_ended_up_on_the_dark_side_of_the_moon.html - Sun, 2 Jun 2019 23:55:00 +0200 - <p>A while back a college and friend from Debian and the Skolelinux / -Debian Edu project approached me, asking if I knew someone that might -be interested in helping out with a technology project he was running -as a teacher at <a href="https://www.ecolefrancodanoise.dk/">L'école -franco-danoise</a> - the Danish-French school and kindergarden. The -kids were building robots, rovers. The story behind it is to build a -rover for use -<a href="http://blog.ecolefrancodanoise.dk/first-week-on-the-dark-side">on -the dark side of the moon</a>, and remote control it. As travel cost -was a bit high for the final destination, and they wanted to test the -concept first, he was looking for volunteers to host a rover for the -kids to control in a foreign country. I ended up volunteering as a -host, and last week the rover arrived. It took a while to arrive -after <a href="http://blog.ecolefrancodanoise.dk/model-moms">it was -built and shipped</a>, because of customs confusion. Luckily we were -able fix it quickly with help from my colleges at work.</p> - -<p>This is what it looked like when the rover arrived. Note the cute -eyes looking up on me from the wrapping</p> - -<img src="http://people.skolelinux.org/pere/blog/images/2019-06-02-robot-dark-side-of-moon-esken-med-det-rare-i.jpeg" width="32%" style="clear:left"/> -<img src="http://people.skolelinux.org/pere/blog/images/2019-06-02-robot-dark-side-of-moon-den-ser-meg.jpeg" width="32%" style="clear:left"/> -<img src="http://people.skolelinux.org/pere/blog/images/2019-06-02-robot-dark-side-of-moon-en-skrue-loes.jpeg" width="32%" style="clear:left"/> - -<p style="text-align:left">Once the robot arrived, we needed to track -down batteries and figure out how to build custom firmware for it with -the appropriate wifi settings. I asked a friend if I could get two -18650 batteries from his pile of Tesla batteries (he had them from the -wrack of a crashed Tesla), so now the rover is running on Tesla -batteries.</p> - -<p>Building -<a href="https://gitlab.com/ecolefrancodanoise/arduino-efd/">the rover -firmware</a> proved a bit harder, as the code did not work out of the -box with the Arduino IDE package in Debian Buster. I suspect this is -due to a unsolved -<a href="https://github.com/arduino/Arduino/pull/2703"> license problem -with arduino</a> blocking Debian from upgrading to the latest version. -In the end we gave up debugging why the IDE failed to find the -required libraries, and ended up using the Arduino Makefile from the -<a href="https://tracker.debian.org/pkg/arduino-mk">arduino-mk Debian -package</a> instead. Unfortunately the camera library is missing from -the Arduino environment in Debian, so we disabled the camera support -for the first firmware build, to get something up and running. With -this reduced firmware, the robot could be controlled via the -controller server, driving around and measuring distance using its -internal acoustic sensor.</p> - -<p>Next, With some help from my friend in Denmark, which checked in the -camera library into the gitlab repository for me to use, we were able -to build a new and more complete version of the firmware, and the -robot is now up and running. This is what the "commander" web page -look like after taking a measurement and a snapshot:</p> - -<img src="http://people.skolelinux.org/pere/blog/images/2019-06-02-robot-dark-side-of-moon-commander.png" width="40%" border="1" align="center"/> - -<p>If you want to learn more about this project, you can check out the -<a href="https://hackaday.io/project/164082-the-dark-side-challenge">The -Dark Side Challenge</a> Hackaday web pages.</p> + Latest Jami back in Debian Testing, and scriptable using dbus + http://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html + http://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html + Tue, 12 Jan 2021 17:00:00 +0100 + <p>After a lot of hard work by its maintainer Alexandre Viau and +others, the decentralized communication platform +<a href="https://en.wikipedia.org/wiki/Jami_(software)">Jami</a> +(earlier known as Ring), managed to get +<a href="https://tracker.debian.org/pkg/ring">its latest version</a> +into Debian Testing. Several of its dependencies has caused build and +propagation problems, which all seem to be solved now.</p> + +<p>In addition to the fact that Jami is decentralized, similar to how +bittorrent is decentralized, I first of all like how it is not +connected to external IDs like phone numbers. This allow me to set up +computers to send me notifications using Jami without having to find +get a phone number for each computer. Automatic notification via Jami +is also made trivial thanks to the provided client side API (as a DBus +service). Here is my bourne shell script demonstrating how to let any +system send a message to any Jami address. It will create a new +identity before sending the message, if no Jami identity exist +already:</p> + +<p><pre> +#!/bin/sh +# +# Usage: $0 <jami-address> <message> +# +# Send <message> to <jami-address>, create local jami account if +# missing. +# +# License: GPL v2 or later at your choice +# Author: Petter Reinholdtsen + + +if [ -z "$HOME" ] ; then + echo "error: missing \$HOME, required for dbus to work" + exit 1 +fi + +# First, get dbus running if not already running +DBUSLAUNCH=/usr/bin/dbus-launch +PIDFILE=/run/asterisk/dbus-session.pid +if [ -e $PIDFILE ] ; then + . $PIDFILE + if ! kill -0 $DBUS_SESSION_BUS_PID 2>/dev/null ; then + unset DBUS_SESSION_BUS_ADDRESS + fi +fi +if [ -z "$DBUS_SESSION_BUS_ADDRESS" ] && [ -x "$DBUSLAUNCH" ]; then + DBUS_SESSION_BUS_ADDRESS="unix:path=$HOME/.dbus" + dbus-daemon --session --address="$DBUS_SESSION_BUS_ADDRESS" --nofork --nopidfile --syslog-only < /dev/null > /dev/null 2>&1 3>&1 & + DBUS_SESSION_BUS_PID=$! + ( + echo DBUS_SESSION_BUS_PID=$DBUS_SESSION_BUS_PID + echo DBUS_SESSION_BUS_ADDRESS=\""$DBUS_SESSION_BUS_ADDRESS"\" + echo export DBUS_SESSION_BUS_ADDRESS + ) > $PIDFILE + . $PIDFILE +fi & + +dringop() { + part="$1"; shift + op="$1"; shift + dbus-send --session \ + --dest="cx.ring.Ring" /cx/ring/Ring/$part cx.ring.Ring.$part.$op $* +} + +dringopreply() { + part="$1"; shift + op="$1"; shift + dbus-send --session --print-reply \ + --dest="cx.ring.Ring" /cx/ring/Ring/$part cx.ring.Ring.$part.$op $* +} + +firstaccount() { + dringopreply ConfigurationManager getAccountList | \ + grep string | awk -F'"' '{print $2}' | head -n 1 +} + +account=$(firstaccount) + +if [ -z "$account" ] ; then + echo "Missing local account, trying to create it" + dringop ConfigurationManager addAccount \ + dict:string:string:"Account.type","RING","Account.videoEnabled","false" + account=$(firstaccount) + if [ -z "$account" ] ; then + echo "unable to create local account" + exit 1 + fi +fi + +# Not using dringopreply to ensure $2 can contain spaces +dbus-send --print-reply --session \ + --dest=cx.ring.Ring \ + /cx/ring/Ring/ConfigurationManager \ + cx.ring.Ring.ConfigurationManager.sendTextMessage \ + string:"$account" string:"$1" \ + dict:string:string:"text/plain","$2" +</pre></p> + +<p>If you want to check it out yourself, visit the +<a href="https://jami.net/">the Jami system project page</a> to learn +more, and install the latest Jami client from Debian Unstable or +Testing.</p> <p>As usual, if you use Bitcoin and want to show your support of my activities, please send Bitcoin donations to my address @@ -528,66 +552,109 @@ activities, please send Bitcoin donations to my address - Nikita version 0.4 released - free software archive API server - http://people.skolelinux.org/pere/blog/Nikita_version_0_4_released___free_software_archive_API_server.html - http://people.skolelinux.org/pere/blog/Nikita_version_0_4_released___free_software_archive_API_server.html - Wed, 22 May 2019 11:30:00 +0200 - <p>This morning, a new release of -<a href="https://gitlab.com/OsloMet-ABI/nikita-noark5-core/">Nikita -Noark 5 core project</a> was -<a href="https://lists.nuug.no/pipermail/nikita-noark/2019-May/000468.html">announced -on the project mailing list</a>. The Nikita 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.4 -since version 0.3, see the email link above for links to a demo site:</p> + Boken «Made with Creative Commons» lanseres på norsk + http://people.skolelinux.org/pere/blog/Boken__Made_with_Creative_Commons__lanseres_p__norsk.html + http://people.skolelinux.org/pere/blog/Boken__Made_with_Creative_Commons__lanseres_p__norsk.html + Sun, 15 Nov 2020 23:50:00 +0100 + <p>Endelig er den norske utgaven av «Made with Creative Commons» +ferdig og publisert. Følgende pressemelding ble nettopp sendt ut: -<ul> +<blockquote> + +<p><strong>Boken «Made with Creative Commons» lanseres på norsk</strong></p> - <li>Roll out OData handling to all endpoints where applicable</li> - <li>Changed the relation key for "ny-journalpost" to the official one.</li> - <li>Better link generation on outgoing links.</li> - <li>Tidy up code and make code and approaches more consistent throughout - the codebase</li> - <li>Update rels to be in compliance with updated version in the - interface standard</li> - <li>Avoid printing links on empty objects as they can't have links</li> - <li>Small bug fixes and improvements</li> - <li>Start moving generation of outgoing links to @Service layer so access - control can be used when generating links</li> - <li>Log exception that was being swallowed so it's traceable</li> - <li>Fix name mapping problem</li> - <li>Update templated printing so templated should only be printed if it - is set true. Requires more work to roll out across entire - application.</li> - <li>Remove Record->DocumentObject as per domain model of n5v4</li> - <li>Add ability to delete lists filtered with OData</li> - <li>Return NO_CONTENT (204) on delete as per interface standard</li> - <li>Introduce support for ConstraintViolationException exception</li> - <li>Make Service classes extend NoarkService</li> - <li>Make code base respect X-Forwarded-Host, X-Forwarded-Proto and - X-Forwarded-Port</li> - <li>Update CorrespondencePart* code to be more in line with Single - Responsibility Principle</li> - <li>Make package name follow directory structure</li> - <li>Make sure Document number starts at 1, not 0</li> - <li>Fix isues discovered by FindBugs</li> - <li>Update from Date to ZonedDateTime</li> - <li>Fix wrong tablename</li> - <li>Introduce Service layer tests</li> - <li>Improvements to CorrespondencePart</li> - <li>Continued work on Class / Classificationsystem</li> - <li>Fix feature where authors were stored as storageLocations</li> - <li>Update HQL builder for OData</li> - <li>Update OData search capability from webpage</li> +<p>«Gjort med Creative Commons» er en bok om gjenbruk, deling og den +digitale allmenningen. Boken omhandler å bygge en forretningsmodell på +åpne verdier, endringene i tankesett og filosofi, og fordelene og +praksisen som kommer med å være «åpen».</p> +<p>Forfatterne Paul Stacey og Sarah Hinchliff Pearson tar oss med inn +i samtaler med 24 mennesker, prosjekter og organisasjoner som på ulike +måter generere inntekter gjennom deling av sine verk. Som leser får +man innsikt i hvordan alt fra forskere, forfattere, kunstnere og +filmskapere tjener penger basert på åpne forretningsmodeller. En av +referansestudiene i denne boken viser hvordan Blender Animation Studio +lager vakre animasjonsfilmer som de publiserer under en fri lisens, +basert på en plattform som er fri programvare.</p> + +<p>Utover praktiske eksempler på forskjellige forretningsmodeller berører +også boken forskjellen mellom tradisjonelle kommersielle virksomheter og +de som tar utgangspunkt i den globale delingskulturen.</p> + +<p>«Hvis du ønsker å lære mer om digital delingskultur og Creative Commons +er dette en bok som både vil inspirere og gi grunnleggende innsikt» sier +leder av Creative Commons Norge, Christer Solheim Gundersen. «De siste +årene har denne globale bevegelsen sett en betydelig vekst med totalt +over 1,6 milliarder verk med CC-lisens tilgjengelig på nett.» + +Nå er den tilgjengelig på norsk takket være liten gruppe frivillige +entusiaster ledet av Petter Reinholdtsen. «På vegne av Creative Commons +Norge vil jeg takke hver enkelt bidragsyter. Dette prosjektet er i seg +selv et inspirerende eksempel på at delingskulturen også har godt +fotfeste her i Norge.», avslutter Gundersen.</p> + +<p>Boken er selvsagt fritt tilgjengelig under en Creative Commons lisens, +og kan også kjøpes som ebok og papirutgave på blant annet Lulu.com og +Amazon.</p> + +<p><strong>Lenker og kontaktinformasjon</strong></p> + +<ul> + +<li>Kontaktpunkt: +<br>Ole-Erik Yrvin (oeyrvin@gmail.com) og +<br>Christer Solheim Gundersen (christer@goopen.no), +47 9341 1360</li> + +<li>Bokens <a href="https://madewith.cc/">engelske nettside</a></li> + +<li>Den <a href="http://www.hungry.com/~pere/publisher/">norske utgavens nettside</a></li> + +<li><a href="https://www.lulu.com/en/us/shop/sarah-hinchliff-pearson-and-paul-stacey-and-bryan-mathers-and-ryan-merkley/gjort-med-creative-commons/paperback/product-m5jy75.html">Papirutgaven fra Lulu</a></li> + +<li><a href="https://www.lulu.com/en/us/shop/sarah-hinchliff-pearson-and-paul-stacey-and-bryan-mathers-and-ryan-merkley/gjort-med-creative-commons/ebook/product-zw2r4k.html">Epub-utgaven fra lulu</a></li> + </ul> -<p>If free and open standardized archiving API sound interesting to -you, please contact us on IRC -(<a href="irc://irc.freenode.net/%23nikita">#nikita on -irc.freenode.net</a>) or email -(<a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">nikita-noark -mailing list</a>).</p> +</blockquote> + +<p>Nå håper jeg bare den får mange lesere, og finner veien under mange +juletrær.</p> + +<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 +<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>. +Merk, betaling med bitcoin er ikke anonymt. :)</p> + + + + + Buster based Bokmål edition of Debian Administrator's Handbook + http://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html + http://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html + Tue, 20 Oct 2020 18:35:00 +0200 + <p align="center"><img align="center" src="http://people.skolelinux.org/pere/blog/images/2020-10-20-debian-handbook-nb-testprint.jpeg" width="60%"/></p> + +<p>I am happy to report that we finally made it! Norwegian Bokmål +became the first translation published on paper of the new Buster +based edition of "<a href="https://debian-handbook.info/">The Debian +Administrator's Handbook</a>". The print proof reading copy arrived +some days ago, and it looked good, so now the book is approved for +general distribution. This updated paperback edition <a +href="https://debian-handbook.info/get/#norwegian">is available from +lulu.com</a>. The book is also available for download in electronic +form as PDF, EPUB and Mobipocket, and can also be +<a href="https://debian-handbook.info/browse/nb-NO/stable/">read online</a>.</p> + +<p>I am very happy to wrap up this Creative Common licensed project, +which concludes several months of work by several volunteers. The +number of Linux related books published in Norwegian are few, and I +really hope this one will gain many readers, as it is packed with deep +knowledge on Linux and the Debian ecosystem. The book will be +available for various Internet book stores like Amazon and Barnes & +Noble soon, but I recommend buying +"<a href="https://www.lulu.com/en/us/shop/roland-mas-and-rapha%C3%ABl-hertzog/h%C3%A5ndbok-for-debian-administratoren/paperback/product-9j7qwq.html">Håndbok +for Debian-administratoren</a>" directly from the source at Lulu. <p>As usual, if you use Bitcoin and want to show your support of my activities, please send Bitcoin donations to my address @@ -596,52 +663,26 @@ activities, please send Bitcoin donations to my address - MIME type "text/vnd.sosi" for SOSI map data - http://people.skolelinux.org/pere/blog/MIME_type__text_vnd_sosi__for_SOSI_map_data.html - http://people.skolelinux.org/pere/blog/MIME_type__text_vnd_sosi__for_SOSI_map_data.html - Mon, 20 May 2019 08:35:00 +0200 - <p>As part of my involvement in the work to -<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard">standardise -a REST based API for Noark 5</a>, the Norwegian archiving standard, I -spent some time the last few months to try to register a -<a href="https://www.iana.org/assignments/media-types/">MIME type</a> -and <a href="https://www.nationalarchives.gov.uk/PRONOM/">PRONOM -code</a> for the SOSI file format. The background is that there is a -set of formats approved for long term storage and archiving in Norway, -and among these formats, SOSI is the only format missing a MIME type -and PRONOM code.</p> - -<p>What is SOSI, you might ask? To quote Wikipedia: SOSI is short for -Samordnet Opplegg for Stedfestet Informasjon (literally "Coordinated -Approach for Spatial Information", but more commonly expanded in -English to Systematic Organization of Spatial Information). It is a -text based file format for geo-spatial vector information used in -Norway. Information about the SOSI format can be found in English -from <a href="https://en.wikipedia.org/wiki/SOSI">Wikipedia</a>. The -specification is available in Norwegian from -<a href="https://www.kartverket.no/geodataarbeid/Standarder/SOSI/">the -Norwegian mapping authority</a>. The SOSI standard, which originated -in the beginning of nineteen eighties, was the inspiration and formed the -basis for the XML based -<a href="https://en.wikipedia.org/wiki/Geography_Markup_Language">Geography -Markup Language</a>.</p> - -<p>I have so far written -<a href="https://github.com/file/file/pull/67">a pattern matching -rule</a> for the file(1) unix tool to recognize SOSI files, submitted -a request to the PRONOM project to have a PRONOM ID assigned to the -format (reference TNA1555078202S60), and today send a request to IANA -to register the "text/vnd.sosi" MIME type for this format (referanse -<a href="https://tools.iana.org/public-view/viewticket/1143144">IANA -#1143144</a>). If all goes well, in a few months, anyone implementing -the Noark 5 Tjenestegrensesnitt API spesification should be able to -use an official MIME type and PRONOM code for SOSI files. In -addition, anyone using SOSI files on Linux should be able to -automatically recognise the format and web sites handing out SOSI -files can begin providing a more specific MIME type. So far, SOSI -files has been handed out from web sites using the -"application/octet-stream" MIME type, which is just a nice way of -stating "I do not know". Soon, we will know. :)</p> + Buster update of Norwegian Bokmål edition of Debian Administrator's Handbook almost done + http://people.skolelinux.org/pere/blog/Buster_update_of_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_almost_done.html + http://people.skolelinux.org/pere/blog/Buster_update_of_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_almost_done.html + Fri, 11 Sep 2020 09:45:00 +0200 + <p>Thanks to the good work of several volunteers, the updated edition +of the Norwegian translation for +"<a href="https://debian-handbook.info/">The Debian Administrator's +Handbook</a>" is now almost completed. After many months of proof +reading, I consider the proof reading complete enough for us to move +to the next step, and have asked for the print version to be prepared +and sent of to the print on demand service lulu.com. While it is +still not to late if you find any incorrect translations on +<a href="https://hosted.weblate.org/languages/nb_NO/debian-handbook/">the +hosted Weblate service</a>, but it will be soon. :) You can check out +<a href=" https://debian-handbook.info/browse/nb-NO/stable/">the Buster +edition on the web</a> until the print edition is ready.</p> + +<p>The book will be for sale on lulu.com and various web book stores, +with links available from the web site for the book linked to above. +I hope a lot of readers find it useful.</p> <p>As usual, if you use Bitcoin and want to show your support of my activities, please send Bitcoin donations to my address @@ -650,148 +691,26 @@ activities, please send Bitcoin donations to my address - PlantUML for text based UML diagram modelling - nice free software - http://people.skolelinux.org/pere/blog/PlantUML_for_text_based_UML_diagram_modelling___nice_free_software.html - http://people.skolelinux.org/pere/blog/PlantUML_for_text_based_UML_diagram_modelling___nice_free_software.html - Mon, 25 Mar 2019 09:35:00 +0100 - <p>As part of my involvement with the -<a href="https://gitlab.com/OsloMet-ABI/nikita-noark5-core/">Nikita -Noark 5 core project</a>, I have been proposing improvements to the -API specification created by <a href="https://www.arkivverket.no/">The -National Archives of Norway</a> and helped migrating the text from a -version control system unfriendly binary format (docx) to Markdown in -git. Combined with the migration to a public git repository (on -github), this has made it possible for anyone to suggest improvement -to the text.</p> - -<p>The specification is filled with UML diagrams. I believe the -original diagrams were modelled using Sparx Systems Enterprise -Architect, and exported as EMF files for import into docx. This -approach make it very hard to track changes using a version control -system. To improve the situation I have been looking for a good text -based UML format with associated command line free software tools on -Linux and Windows, to allow anyone to send in corrections to the UML -diagrams in the specification. The tool must be text based to work -with git, and command line to be able to run it automatically to -generate the diagram images. Finally, it must be free software to -allow anyone, even those that can not accept a non-free software -license, to contribute.</p> - -<p>I did not know much about free software UML modelling tools when I -started. I have used dia and inkscape for simple modelling in the -past, but neither are available on Windows, as far as I could tell. I -came across a nice -<a href="https://modeling-languages.com/text-uml-tools-complete-list/">list -of text mode uml tools</a>, and tested out a few of the tools listed -there. <a href="http://plantuml.com/">The PlantUML tool</a> seemed -most promising. After verifying that the packages -<a href="https://tracker.debian.org/pkg/plantuml">is available in -Debian</a> and found <a href="https://github.com/plantuml/plantuml">its -Java source</a> under a GPL license on github, I set out to test if it -could represent the diagrams we needed, ie the ones currently in -<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/">the -Noark 5 Tjenestegrensesnitt specification</a>. I am happy to report -that it could represent them, even thought it have a few warts here -and there.</p> - -<p>After a few days of modelling I completed the task this weekend. A -temporary link to the complete set of diagrams (original and from -PlantUML) is available in -<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/issues/76">the -github issue discussing the need for a text based UML format</a>, but -please note I lack a sensible tool to convert EMF files to PNGs, so -the "original" rendering is not as good as the original was in the -publised PDF.</p> - -<p>Here is an example UML diagram, showing the core classes for -keeping metadata about archived documents:</p> - -<pre> -@startuml -skinparam classAttributeIconSize 0 - -!include media/uml-class-arkivskaper.iuml -!include media/uml-class-arkiv.iuml -!include media/uml-class-klassifikasjonssystem.iuml -!include media/uml-class-klasse.iuml -!include media/uml-class-arkivdel.iuml -!include media/uml-class-mappe.iuml -!include media/uml-class-merknad.iuml -!include media/uml-class-registrering.iuml -!include media/uml-class-basisregistrering.iuml -!include media/uml-class-dokumentbeskrivelse.iuml -!include media/uml-class-dokumentobjekt.iuml -!include media/uml-class-konvertering.iuml -!include media/uml-datatype-elektronisksignatur.iuml - -Arkivstruktur.Arkivskaper "+arkivskaper 1..*" <-o "+arkiv 0..*" Arkivstruktur.Arkiv -Arkivstruktur.Arkiv o--> "+underarkiv 0..*" Arkivstruktur.Arkiv -Arkivstruktur.Arkiv "+arkiv 1" o--> "+arkivdel 0..*" Arkivstruktur.Arkivdel -Arkivstruktur.Klassifikasjonssystem "+klassifikasjonssystem [0..1]" <--o "+arkivdel 1..*" Arkivstruktur.Arkivdel -Arkivstruktur.Klassifikasjonssystem "+klassifikasjonssystem [0..1]" o--> "+klasse 0..*" Arkivstruktur.Klasse -Arkivstruktur.Arkivdel "+arkivdel 0..1" o--> "+mappe 0..*" Arkivstruktur.Mappe -Arkivstruktur.Arkivdel "+arkivdel 0..1" o--> "+registrering 0..*" Arkivstruktur.Registrering -Arkivstruktur.Klasse "+klasse 0..1" o--> "+mappe 0..*" Arkivstruktur.Mappe -Arkivstruktur.Klasse "+klasse 0..1" o--> "+registrering 0..*" Arkivstruktur.Registrering -Arkivstruktur.Mappe --> "+undermappe 0..*" Arkivstruktur.Mappe -Arkivstruktur.Mappe "+mappe 0..1" o--> "+registrering 0..*" Arkivstruktur.Registrering -Arkivstruktur.Merknad "+merknad 0..*" <--* Arkivstruktur.Mappe -Arkivstruktur.Merknad "+merknad 0..*" <--* Arkivstruktur.Dokumentbeskrivelse -Arkivstruktur.Basisregistrering -|> Arkivstruktur.Registrering -Arkivstruktur.Merknad "+merknad 0..*" <--* Arkivstruktur.Basisregistrering -Arkivstruktur.Registrering "+registrering 1..*" o--> "+dokumentbeskrivelse 0..*" Arkivstruktur.Dokumentbeskrivelse -Arkivstruktur.Dokumentbeskrivelse "+dokumentbeskrivelse 1" o-> "+dokumentobjekt 0..*" Arkivstruktur.Dokumentobjekt -Arkivstruktur.Dokumentobjekt *-> "+konvertering 0..*" Arkivstruktur.Konvertering -Arkivstruktur.ElektroniskSignatur -[hidden]-> Arkivstruktur.Dokumentobjekt -@enduml -</pre> - -<p><a href="http://plantuml.com/class-diagram">The format</a> is quite -compact, with little redundant information. The text expresses -entities and relations, and there is little layout related fluff. One -can reuse content by using include files, allowing for consistent -naming across several diagrams. The include files can be standalone -PlantUML too. Here is the content of -<tt>media/uml-class-arkivskaper.iuml<tt>:</p> - -<pre> -@startuml -class Arkivstruktur.Arkivskaper <Arkivenhet> { - +arkivskaperID : string - +arkivskaperNavn : string - +beskrivelse : string [0..1] -} -@enduml -</pre> - -<p>This is what the complete diagram for the PlantUML notation above -look like:</p> - -<p><img width="80%" src="http://people.skolelinux.org/pere/blog/images/2019-03-25-noark5-plantuml-diagrameksempel.png"></p> - -<p>A cool feature of PlantUML is that the generated PNG files include -the entire original source diagram as text. The source (with include -statements expanded) can be extracted using for example -<tt>exiftool</tt>. Another cool feature is that parts of the entities -can be hidden after inclusion. This allow to use include files with -all attributes listed, even for UML diagrams that should not list any -attributes.</p> - -<p>The diagram also show some of the warts. Some times the layout -engine place text labels on top of each other, and some times it place -the class boxes too close to each other, not leaving room for the -labels on the relationship arrows. The former can be worked around by -placing extra newlines in the labes (ie "\n"). I did not do it here -to be able to demonstrate the issue. I have not found a good way -around the latter, so I normally try to reduce the problem by changing -from vertical to horizontal links to improve the layout.</p> - -<p>All in all, I am quite happy with PlantUML, and very impressed with -how quickly its lead developer responds to questions. So far I got an -answer to my questions in a few hours when I send an email. I -definitely recommend looking at PlantUML if you need to make UML -diagrams. Note, PlantUML can draw a lot more than class relations. -Check out the documention for a complete list. :)</p> + Working on updated Norwegian Bokmål edition of Debian Administrator's Handbook + http://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html + http://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html + Sat, 4 Jul 2020 23:55:00 +0200 + <p>Three years ago, the first Norwegian Bokmål edition of +"<a href="https://debian-handbook.info/">The Debian Administrator's +Handbook</a>" was published. This was based on Debian Jessie. Now a +new and updated version based on Buster is getting ready. Work on the +updated Norwegian Bokmål edition has been going on for a few months +now, and yesterday, we reached the first mile stone, with 100% of the +texts being translated. A lot of proof reading remains, of course, +but a major step towards a new edition has been taken.</p> + +<p>The book is translated by volunteers, and we would love to get some +help with the proof reading. The translation uses +<a href="https://hosted.weblate.org/languages/nb_NO/debian-handbook/">the +hosted Weblate service</a>, and we welcome everyone to have a look and +submit improvements and suggestions. There is also a proof readers +PDF available on request, get in touch if you want to help out that +way.</p> <p>As usual, if you use Bitcoin and want to show your support of my activities, please send Bitcoin donations to my address @@ -800,49 +719,66 @@ activities, please send Bitcoin donations to my address - Release 0.3 of free software archive API system Nikita announced - http://people.skolelinux.org/pere/blog/Release_0_3_of_free_software_archive_API_system_Nikita_announced.html - http://people.skolelinux.org/pere/blog/Release_0_3_of_free_software_archive_API_system_Nikita_announced.html - Sun, 24 Mar 2019 14:30:00 +0100 - <p>Yesterday, a new release of -<a href="https://gitlab.com/OsloMet-ABI/nikita-noark5-core/">Nikita -Noark 5 core project</a> was -<a href="https://lists.nuug.no/pipermail/nikita-noark/2019-March/000451.html">announced -on the project mailing list</a>. 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.3 -since version 0.2.1 (from NEWS.md):</p> - -<ul> - <li>Improved ClassificationSystem and Class behaviour.</li> - <li>Tidied up known inconsistencies between domain model and hateaos links.</li> - <li>Added experimental code for blockchain integration. </li> - <li>Make token expiry time configurable at upstart from properties file.</li> - <li>Continued work on OData search syntax.</li> - <li>Started work on pagination for entities, partly implemented for Saksmappe.</li> - <li>Finalise ClassifiedCode Metadata entity.</li> - <li>Implement mechanism to check if authentication token is still - valid. This allow the GUI to return a more sensible message to the - user if the token is expired.</li> - <li>Reintroduce browse.html page to allow user to browse JSON API using - hateoas links.</li> - <li>Fix bug in handling file/mappe sequence number. Year change was - not properly handled.</li> - <li>Update application yml files to be in sync with current development.</li> - <li>Stop 'converting' everything to PDF using libreoffice. Only - convert the file formats doc, ppt, xls, docx, pptx, xlsx, odt, odp - and ods.</li> - <li>Continued code style fixing, making code more readable.</li> - <li>Minor bug fixes.</li> - -</ul> - -<p>If free and open standardized archiving API sound interesting to -you, please contact us on IRC -(<a href="irc://irc.freenode.net/%23nikita">#nikita on -irc.freenode.net</a>) or email -(<a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">nikita-noark -mailing list</a>).</p> + Secure Socket API - a simple and powerful approach for TLS support in software + http://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html + http://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html + Sat, 6 Jun 2020 12:40:00 +0200 + <p>As a member of the <a href="https://www.nuug.no/">Norwegian Unix +User Group</a>, I have the pleasure of receiving the +<a href="https://www.usenix.org/">USENIX</a> magazine +<a href="https://www.usenix.org/publications/login/">;login:</a> +several times a year. I rarely have time to read all the articles, +but try to at least skim through them all as there is a lot of nice +knowledge passed on there. I even carry the latest issue with me most +of the time to try to get through all the articles when I have a few +spare minutes.</p> + +<p>The other day I came across a nice article titled +"<a href="https://www.usenix.org/publications/login/winter2018/oneill">The +Secure Socket API: TLS as an Operating System Service</a>" with a +marvellous idea I hope can make it all the way into the POSIX standard. +The idea is as simple as it is powerful. By introducing a new +socket() option IPPROTO_TLS to use TLS, and a system wide service to +handle setting up TLS connections, one both make it trivial to add TLS +support to any program currently using the POSIX socket API, and gain +system wide control over certificates, TLS versions and encryption +systems used. Instead of doing this:</p> + +<p><blockquote><pre> +int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TCP); +</pre></blockquote></p> + +<p>the program code would be doing this:<p> + +<p><blockquote><pre> +int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TLS); +</pre></blockquote></p> + +<p>According to the ;login: article, converting a C program to use TLS +would normally modify only 5-10 lines in the code, which is amazing +when compared to using for example the OpenSSL API.</p> + +<p>The project has set up the +<a href="https://securesocketapi.org/">https://securesocketapi.org/</a> +web site to spread the idea, and the code for a kernel module and the +associated system daemon is available from two github repositories: +<a href="https://github.com/markoneill/ssa">ssa</a> and +<a href="https://github.com/markoneill/ssa-daemon">ssa-daemon</a>. +Unfortunately there is no explicit license information with the code, +so its copyright status is unclear. A +<a href="https://github.com/markoneill/ssa/issues/2">request to solve +this</a> about it has been unsolved since 2018-08-17.</p> + +<p>I love the idea of extending socket() to gain TLS support, and +understand why it is an advantage to implement this as a kernel module +and system wide service daemon, but can not help to think that it +would be a lot easier to get projects to move to this way of setting +up TLS if it was done with a user space approach where programs +wanting to use this API approach could just link with a wrapper +library.</p> + +<p>I recommend you check out this simple and powerful approach to more +secure network connections. :)</p> <p>As usual, if you use Bitcoin and want to show your support of my activities, please send Bitcoin donations to my address