Generated.

[homepage.git] / blog / archive / 2020 / 05 / index.html

diff --git a/blog/archive/2020/05/index.html b/blog/archive/2020/05/index.html
index 93d926d947b1a1821ceb04b0c064c29c6ad29339..62916aa9915deca6758650cd96c2ebbaa331d1b2 100644 (file)
--- a/blog/archive/2020/05/index.html
+++ b/blog/archive/2020/05/index.html
@@ -219,7 +219,7 @@ Zoom meetings with free software clients.</p>
 password set on the room.  The Jami daemon leak memory like crazy
 (approximately 1 GiB a minute) when I am connected to the video
 conference, so I had to restart the client every 7-10 minutes, which
-is not a great.  I tried to get other SIP Linux clients to work
+is not great.  I tried to get other SIP Linux clients to work
 without success, so I decided I would have to live with this wart
 until someone managed to fix the leak in the dring code base.  But
 another problem showed up once the rooms were password protected.  I
@@ -246,7 +246,7 @@ connect via SIP do not mention this.  The SIP address to use normally
 consist of the room ID (a number), an @ character and the IP address
 of the Zoom SIP gateway.  But Zoom understand a lot more than just the
 room ID in front of the at sign.  The format is "<tt>[Meeting
-ID].[Password].[Layout].[Host Key]</tt>", and you can hear see how you
+ID].[Password].[Layout].[Host Key]</tt>", and you can here see how you
 can both enter password, control the layout (full screen, active
 presence and gallery) and specify the host key to start the meeting.
 The full SIP address entered into Jami to provide the password will
@@ -282,6 +282,13 @@ activities, please send Bitcoin donations to my address
 <h2>Archive</h2>
 <ul>
 
+<li>2021
+<ul>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2021/01/">January (1)</a></li>
+
+</ul></li>
+
 <li>2020
 <ul>
 
@@ -650,7 +657,7 @@ activities, please send Bitcoin donations to my address
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
 
- <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (174)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (175)</a></li>
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (159)</a></li>
 
@@ -664,7 +671,7 @@ activities, please send Bitcoin donations to my address
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
 
- <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (421)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (422)</a></li>
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (23)</a></li>
 
@@ -732,7 +739,7 @@ activities, please send Bitcoin donations to my address
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
 
- <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (58)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (59)</a></li>
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
 
@@ -744,7 +751,7 @@ activities, please send Bitcoin donations to my address
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (12)</a></li>
 
- <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (60)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (61)</a></li>
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (5)</a></li>