Merge remote-tracking branch 'refs/remotes/origin/master'
This commit is contained in:
D. Joe
commit
6aaa63e30f
|
|
@ -0,0 +1,12 @@
|
|||
|
||||
|
||||
At
|
||||
|
||||
http://www.akura.org/
|
||||
|
||||
in the line of text under
|
||||
|
||||
"Learn. Play. Help."
|
||||
|
||||
"apporach" should probably be "approach"
|
||||
|
||||
|
|
@ -0,0 +1,22 @@
|
|||
|
||||
David A. Wheeler in his **How to Evaluate Open Source Software / Free Software (OSS/FS) Programs**
|
||||
as revised August 5, 2011 an as found here:
|
||||
|
||||
<https://www.dwheeler.com/oss_fs_eval.html>
|
||||
[Wayback Machine version](https://web.archive.org/web/20170824001553/https://www.dwheeler.com/oss_fs_eval.html)
|
||||
|
||||
Includes two references to **The IDA Open Source Migration Guidelines** via
|
||||
a now-broken link, http://europa.eu.int/ISPO/ida/jsps/index.jsp?fuseAction=showDocument&parent=news&documentID=1647
|
||||
|
||||
The Internet Archive's Wayback Machine holds at least this archived copy of
|
||||
that page:
|
||||
|
||||
<https://web.archive.org/web/20031202191002/http://europa.eu.int/ISPO/ida/jsps/index.jsp?fuseAction=showDocument&parent=news&documentID=1647>
|
||||
|
||||
and of the PDF to which that page then points (this is for the English
|
||||
version, there is at least a link also to a version in French):
|
||||
|
||||
<https://web.archive.org/web/20031121150329/http://europa.eu.int:80/ISPO/ida/export/files/en/1618.pdf>
|
||||
|
||||
(Wheeler's article contains a great many links, many of which I've not yet checked, but which checking might benefit from a spot of automation.)
|
||||
|
||||
|
|
@ -0,0 +1,10 @@
|
|||
|
||||
|
||||
https://support.mozilla.org/en-US/kb/tabs-organize-websites-single-window#w_tab-tips
|
||||
|
||||
> To bookmark a set of tabs all at once use the keyboard shortcut Ctrl + Shift + D.
|
||||
|
||||
This one appears to be a documentation bug, since by all accounts the option
|
||||
is deliberately gone from the top-tier menus, having been relegated to the
|
||||
tabs contextual menu.
|
||||
|
||||
|
|
@ -0,0 +1,21 @@
|
|||
|
||||
|
||||
In
|
||||
|
||||
<http://gitready.com/beginner/2009/03/09/remote-tracking-branches.html>
|
||||
|
||||
there is a link to a git cheat sheet that was at
|
||||
|
||||
<http://cheat.errtheblog.com/s/git/>
|
||||
|
||||
but that seems broken
|
||||
|
||||
The content can be found at:
|
||||
|
||||
<https://web.archive.org/web/20170606084016/http://cheat.errtheblog.com/s/git/>
|
||||
|
||||
|
||||
It's a "Not Found" error but the parent site still exists at least. Most of
|
||||
the blog functionality (browse, add, edit functions) are broken.
|
||||
|
||||
|
||||
|
|
@ -0,0 +1,6 @@
|
|||
|
||||
|
||||
https://opensource.com/users/jkrieger
|
||||
|
||||
has a duplicate "with", eg, "with with"
|
||||
|
||||
|
|
@ -0,0 +1,13 @@
|
|||
|
||||
Starting from their main page
|
||||
and following the
|
||||
[Resources](https://libraryfreedomproject.org/resources/)
|
||||
link, one of the sections is for the
|
||||
[Mobile Privacy Crash Course](https://libraryfreedomproject.org/mobileprivacytoolkit/).
|
||||
|
||||
Following the link for that, then, shows a couple of stale resources.
|
||||
|
||||
The biggest one is for the broken link to the now defunct CyanogenMod
|
||||
project. That should probably be replaced by a link to CyanogenMod's
|
||||
successor, [LineageOS](https://lineageos.org/).
|
||||
|
||||
|
|
@ -0,0 +1,14 @@
|
|||
|
||||
Starting from their main page
|
||||
and following the
|
||||
[Resources](https://libraryfreedomproject.org/resources/)
|
||||
link, one of the sections is for the
|
||||
[Mobile Privacy Crash Course](https://libraryfreedomproject.org/mobileprivacytoolkit/).
|
||||
|
||||
Following the link for that, then, shows a couple of stale resources.
|
||||
|
||||
A more minor omission is in listing only [OwnCloud](https://owncloud.com/).
|
||||
|
||||
For more complete coverage in this area, [NextCloud](https://nextcloud.com/) should also be
|
||||
listed.
|
||||
|
||||
|
|
@ -0,0 +1,18 @@
|
|||
|
||||
# deprecated endpoint in API docs
|
||||
|
||||
In, eg,
|
||||
|
||||
https://developers.linode.com/v4/filtering
|
||||
|
||||
but also elsewhere in the API documentation, the 'distributions' endpoint is
|
||||
used as an example, yet that endpoint was deprecated, as per the *Breaking*
|
||||
section of the **2018-02-26** entry in
|
||||
|
||||
https://developers.linode.com/v4/changelogs
|
||||
|
||||
All these examples should be re-worked using a current endpoint.
|
||||
|
||||
(I tried to sort out if, and if so where, in https://github.com/linode this
|
||||
documentation sits, but with no luck just yet).
|
||||
|
||||
|
|
@ -0,0 +1,57 @@
|
|||
|
||||
OK, backing out of earlier suggestion, which was based on a misunderstanding
|
||||
of the document in question:
|
||||
|
||||
<https://linode.com/docs/tools-reference/custom-kernels-distros/install-a-custom-distribution-on-a-linode/#download-and-install-image>
|
||||
|
||||
The problem occurs if the reader loses track of the roles of the disk images
|
||||
through the process. In **Rescue Mode**, a pile of bits goes into a volume
|
||||
known temporarily as ```/dev/sda```.
|
||||
|
||||
Then, booting into the **Installer profile**, that pile of bits gets a
|
||||
different name, ```/dev/sdb```. Those bits are used to boot, but only
|
||||
temporarily, during installation. Unlike in **Rescue mode**, the name
|
||||
```/dev/sda``` is applied to a different volume, a volume intended to receive the
|
||||
installed system and eventually to become the boot volume.
|
||||
|
||||
Finally, in the **Boot profile**, that pile of bits, still under the name
|
||||
```/dev/sda```, is used to boot the system.
|
||||
|
||||
At this point, I think I'll suggest changing the language so that the two
|
||||
profiles do not have the same names as the two disk images. Use of the term
|
||||
**boot** to indicate a profile or a disk image either one is a problem,
|
||||
since one boots a system into each of three modes: Rescue, Installer, and
|
||||
the final configuration, which I suggest here be called **Production** but
|
||||
could be called **Final** or something else, so long as it does not collide
|
||||
with the name used for the volume that is the ultimate destination of the
|
||||
installation process.
|
||||
|
||||
So, instead of
|
||||
|
||||
* **Installer** profile and **Installer** image
|
||||
* **Boot** profile and **Boot** image
|
||||
|
||||
we would have
|
||||
|
||||
* **Installation** profile, but **installer** image.
|
||||
* **Production** profile, but **target** image.
|
||||
|
||||
So, in Rescue Mode, one writes, eg, a GNU/Linux distribution's
|
||||
download ISO file to the **installer** disk image.
|
||||
|
||||
When booted into the **Installation** profile, one boots from the **installer** image, but writes to the **target** image.
|
||||
|
||||
In the **Production** profile, one boots from the **target** image, and the **installer** image is dormant.
|
||||
|
||||
The process optionally can stop here, or continue into the improvements
|
||||
suggested by the rest of the document.
|
||||
|
||||
Again, the installation necessarily entails 3 boots--into **Rescue Mode**,
|
||||
into the **Installer** profile, and into the **Boot** profile
|
||||
|
||||
It is easier to miss the switch in the role of the disk names and volume
|
||||
roles through this process because this document visually draws out the two
|
||||
profiles **Installer** and **Boot**. In contrast, it somewhat buries the
|
||||
implicit aspects of the existing volume from which the system is booted into
|
||||
**Rescue Mode**.
|
||||
|
||||
|
|
@ -0,0 +1,17 @@
|
|||
|
||||
|
||||
In the page
|
||||
|
||||
**Monorepos in the Wild**
|
||||
|
||||
https://medium.com/@maoberlehner/monorepos-in-the-wild-33c6eb246cb9
|
||||
|
||||
the apostrophe should be removed from the phrase
|
||||
|
||||
> all it’s official components
|
||||
|
||||
to read
|
||||
|
||||
> all its official components
|
||||
|
||||
|
||||
|
|
@ -2,24 +2,25 @@
|
|||
|
||||
In the main PyGTK page:
|
||||
|
||||
http://www.pygtk.org/index.html
|
||||
<http://www.pygtk.org/index.html>
|
||||
|
||||
in the right-hand sidebar under the headings:
|
||||
|
||||
Documentation
|
||||
Wiki
|
||||
> Documentation
|
||||
> Wiki
|
||||
|
||||
There is a link to a wiki page that does not exist:
|
||||
|
||||
https://wiki.gnome.org/PyGTK
|
||||
<https://wiki.gnome.org/PyGTK>
|
||||
|
||||
"This page does not exist yet. You can create a new empty page, or use one of
|
||||
the page templates."
|
||||
> This page does not exist yet. You can create a new empty page, or use one of
|
||||
> the page templates."
|
||||
|
||||
|
||||
However, on the same wiki this page exists and is the presumbable original
|
||||
target of the link from the sidebar, but was perhaps moved in a
|
||||
reorganization:
|
||||
|
||||
https://wiki.gnome.org/Projects/PyGTK
|
||||
<https://wiki.gnome.org/Projects/PyGTK>
|
||||
|
||||
|
||||
|
|
@ -1,24 +0,0 @@
|
|||
|
||||
|
||||
|
||||
This
|
||||
|
||||
https://www.python.org/doc/current/tut/tut.html
|
||||
|
||||
is 404 as of Thu Mar 23 13:12:13 EDT 2017
|
||||
|
||||
but there is a link to it in:
|
||||
|
||||
http://www.pygtk.org/pygtk2tutorial/ch-Introduction.html
|
||||
|
||||
These following links exist.
|
||||
|
||||
This one:
|
||||
|
||||
https://docs.python.org/tutorial/
|
||||
|
||||
currently redirects to this one:
|
||||
|
||||
https://docs.python.org/3/tutorial/
|
||||
|
||||
https://docs.python.org/2/tutorial/
|
||||
|
|
@ -0,0 +1,27 @@
|
|||
|
||||
|
||||
|
||||
This
|
||||
|
||||
<https://www.python.org/doc/current/tut/tut.html>
|
||||
|
||||
is 404 as of Thu Mar 23 13:12:13 EDT 2017
|
||||
|
||||
but there is a link to it in:
|
||||
|
||||
<http://www.pygtk.org/pygtk2tutorial/ch-Introduction.html>
|
||||
|
||||
These following links exist:
|
||||
|
||||
This one:
|
||||
|
||||
<https://docs.python.org/tutorial/>
|
||||
|
||||
currently redirects to this one:
|
||||
|
||||
<https://docs.python.org/3/tutorial/>
|
||||
|
||||
but there is also
|
||||
|
||||
<https://docs.python.org/2/tutorial/>
|
||||
|
||||
|
|
@ -0,0 +1,15 @@
|
|||
|
||||
|
||||
Links in [ralphbean](http://threebean.org/)'s [gitflow presentation](https://github.com/ralphbean/presentations/blob/master/gitflow.rst) to externally-hosted images are
|
||||
broken, most likely because those images have moved.
|
||||
|
||||
I've begun to track down where and what the links were, and what might be
|
||||
the appropriate updated locations of those images, but this is so far
|
||||
incomplete:
|
||||
|
||||
http://nvie.com/img/2009/12/Screen-shot-2009-12-24-at-11.32.03.png
|
||||
|
||||
http://nvie.com/img/git-model@2x.png
|
||||
|
||||
http://nvie.com/img/centr-decentr@2x.png
|
||||
|
||||
|
|
@ -0,0 +1,20 @@
|
|||
|
||||
The Sugar Labs wiki page for Fedora
|
||||
|
||||
<http://wiki.sugarlabs.org/go/Fedora>
|
||||
|
||||
has the following links for Sugar packages, but they return with a **No repositories found**
|
||||
error:
|
||||
|
||||
* <http://pkgs.fedoraproject.org/cgit/sugar.git/>
|
||||
* <http://pkgs.fedoraproject.org/cgit/sugar-artwork.git/>
|
||||
* <http://pkgs.fedoraproject.org/cgit/sugar-toolkit-gtk3.git/>
|
||||
* <http://pkgs.fedoraproject.org/cgit/sugar-datastore.git/>
|
||||
|
||||
These links currently (2017-12-18) work:
|
||||
|
||||
* <https://src.fedoraproject.org/rpms/sugar>
|
||||
* <https://src.fedoraproject.org/rpms/sugar-artwork>
|
||||
* <https://src.fedoraproject.org/rpms/sugar-toolkit-gtk3>
|
||||
* <https://src.fedoraproject.org/rpms/sugar-datastore>
|
||||
|
||||
|
|
@ -0,0 +1,21 @@
|
|||
|
||||
|
||||
There's a link in
|
||||
|
||||
http://threebean.org/presentations/hfoss-lecture-2013-10-21/#/step-1
|
||||
|
||||
to the now-infamous tweet
|
||||
|
||||
https://twitter.com/pornelski/status/316190292443267073
|
||||
|
||||
but which tweet is no longer available.
|
||||
|
||||
The Wayback Machine has it, though, at:
|
||||
|
||||
https://web.archive.org/web/20140328205442/https://twitter.com/pornelski/status/316190292443267073
|
||||
|
||||
the more involved blog post in this vein remains
|
||||
|
||||
http://tartley.com/?p=1267
|
||||
|
||||
|
||||
|
|
@ -0,0 +1,38 @@
|
|||
|
||||
I just popped into the tmux window in which I have running a tootstream
|
||||
instance working against my @ritjoe@mastotech account, only to see that it stopped
|
||||
streaming a couple of days ago:
|
||||
|
||||
```
|
||||
Now Playing in the Toot-Lab @nowplaying@toot-lab.reclaim.technology 2018-03-10 15:36:01 (21 seconds ago)
|
||||
♺:1 ♥:0 id:76 vis:🌎
|
||||
🎶 #nowplaying #np #tootlabradio #fediplay 🎶
|
||||
|
||||
The Brand New Heavies - "You Are The Universe"
|
||||
|
||||
https://www.youtube.com/watch?v=BeVutyFHYKk
|
||||
|
||||
🎵 https://libre.fm/artist/The+Brand+New+Heavies/album/Shelter/track/You+Are+
|
||||
The+Universe 🎵
|
||||
|
||||
Something went wrong: ('Connection broken: IncompleteRead(0 bytes read)', IncompleteRead(0 bytes read))
|
||||
[@ritjoe (mastotech)]:
|
||||
```
|
||||
|
||||
My use here of tootstream with this account serves at least two purposes for
|
||||
me:
|
||||
|
||||
* It's a role-specific account in which I *try* to keep separate at least some of my RIT-related work.
|
||||
* It's an account separate from my @deejoe@mstdn.io account, in which to some degree I can compare and contrast the server-specific interactions of that account with tootstream, most obviously to me the severe bugs I've noticed in the interaction between that server and that client: https://github.com/magicalraccoon/tootstream/issues/163
|
||||
|
||||
The latter role, of contrasting server-specific behaviors with the same client, seems relevant to that latter bug.
|
||||
|
||||
There's a certain level of *not it* happening between the admin of that instance (@angristan) and folks helping maintain that client (@craigmaloney), perhaps understandably so, but still.
|
||||
|
||||
In any case, I think I'll open a new issue against tootstream, but since I
|
||||
haven't yet discovered what the relevant mentions are for mastotech, rather
|
||||
than fall prey to the yak shaving predators that swallow reports on their
|
||||
way at least to being reported successfully, I'm going to stash this in my own bugjar
|
||||
for now and will pop it back out and polish it back up as time allows and as
|
||||
additional circumstance demands.
|
||||
|
||||
Loading…
Reference in New Issue