add tags, change link style, smol things
This commit is contained in:
parent
1993714d32
commit
dfcf0b3fd5
50
blog.org
50
blog.org
|
@ -4,7 +4,7 @@
|
|||
|
||||
* Meta :@Meta:
|
||||
* Technology :@Technology:
|
||||
** TODO Audacity and the telemetry pull request
|
||||
** TODO Audacity and the telemetry pull request :Open__source__culture:Audio__editing:Music:Drama:
|
||||
:PROPERTIES:
|
||||
:EXPORT_FILE_NAME: audacity-and-the-telemetry-pull-request
|
||||
:EXPORT_HUGO_CUSTOM_FRONT_MATTER: :toc true
|
||||
|
@ -30,7 +30,7 @@ edited in the future.
|
|||
I haven't been able to find /much/ information in this area so forgive me
|
||||
if I'm scant on details.
|
||||
|
||||
On 30 April, a company called [[https://mu.se/][Muse Group]] acquired [[https://www.audacityteam.org/][Audacity]]. According to
|
||||
On 30 April, a company called [[https://mu.se/][Muse Group]] acquired [[https://www.audacityteam.org/][Audacity.]] According to
|
||||
[[https://mu.se][their website]], Muse is the parent company behind many musical
|
||||
applications and tools. It was founded by Eugeny Naidenov just days
|
||||
before it acquired Audacity. Before all of this, Eugeny Naidenov founded
|
||||
|
@ -40,7 +40,7 @@ has over 300 million users. UG acquired [[https://deanzelinsky.com/][Dean Zelins
|
|||
Group was established in 2021 and it seems as if all of the services UG
|
||||
acquired were (or will be) transferred to Muse Group, as well as UG
|
||||
itself. Immediately following its establishment, Muse not only acquired
|
||||
Audacity but also [[https://www.staffpad.net/][StaffPad]].
|
||||
Audacity but also [[https://www.staffpad.net/][StaffPad.]]
|
||||
|
||||
I say 30 April because that's when Muse published their [[https://mu.se/newsroom/tpost/6dhedma301-muse-group-acquires-audacity-expanding-c][press release]]
|
||||
and when Martin Keary (Tantacrul) published a video entitled [[https://www.youtube.com/watch?v=RMWNvwLiXIQ][/I’m now in
|
||||
|
@ -138,7 +138,7 @@ There are other problems with the code that include [[https://github.com/audacit
|
|||
[[https://github.https://github.com/audacity/audacity/pull/835#discussion_r628774985][styling that's inconsistent with the rest of the project,]] [[https://github.com/audacity/audacity/pull/835#discussion_r628500849][unhandled
|
||||
return values resulting in skewed data,]] [[https://github.com/audacity/audacity/pull/835#discussion_r628792423][use of inappropriate functions,]]
|
||||
and [[https://github.com/audacity/audacity/pull/835#discussion_r628818054][spelling errors in the comments.]] I believe these are less important
|
||||
that those above so they won't be discussed.
|
||||
than those above so they won't be discussed.
|
||||
|
||||
*** Community opinions
|
||||
There were many strong opinions regarding both the frontend and backend
|
||||
|
@ -151,7 +151,7 @@ data that /was/ collected.
|
|||
|
||||
Really, the only frontend here is the consent dialogue. However, there
|
||||
are /many/ comments about it, the most common of which is probably that
|
||||
the wording is not only too vague[fn:13] but also inaccurate[fn:14]. The
|
||||
the wording is not only too vague[fn:13] but also inaccurate.[fn:14] The
|
||||
assertion that Google Analytics are not anonymous and any data sent can
|
||||
be trivially de-anonymised (or de-pseudonymised) is repeated many times
|
||||
over. Below are a few links to comments stating such. I searched for the
|
||||
|
@ -293,7 +293,7 @@ accidentally swiping my hand through it before it's finished and
|
|||
smearing a bit of ink across the page, cursing under my breath as I dab
|
||||
it up with a handkerchief or a napkin or something else nearby. I also
|
||||
love that writing things by hand [[https://journals.sagepub.com/doi/abs/10.1177/0956797614524581][has an impact on memory and improves
|
||||
retention]].
|
||||
retention.]]
|
||||
|
||||
*** The problem
|
||||
Unfortunately, I don't love keeping up with that paper. Across many
|
||||
|
@ -309,19 +309,19 @@ dislike wasting whole pages because of a couple mistakes.
|
|||
The obvious solution here is to get an iPad with an Apple Pen, right?
|
||||
Right??
|
||||
|
||||
Wrong because Apple bad[fn:2].
|
||||
Wrong because Apple bad.[fn:2]
|
||||
|
||||
*** The solution
|
||||
Enter the world of ... what are they even called? E-ink notebooks? Paper
|
||||
tablets? E-R/W[fn:1]? Do they even have a "device category" yet? I don't
|
||||
tablets? E-R/W?[fn:1] Do they even have a "device category" yet? I don't
|
||||
know but they solve my problem in a wonderful way.
|
||||
|
||||
As the names suggest, these are devices that can /usually/ open and read
|
||||
e-books (EPUBs, PDFs, etc.), annotate them, and create standalone pages
|
||||
of notes as if they were full notebooks. The most well-known of these
|
||||
devices is likely the [[https://remarkable.com/][reMarkable]]. They had a [[https://venturebeat.com/2019/10/08/remarkable-raises-15-million-to-bring-its-e-paper-tablets-to-more-scribblers/][hugely successful
|
||||
devices is likely the [[https://remarkable.com/][reMarkable.]] They had a [[https://venturebeat.com/2019/10/08/remarkable-raises-15-million-to-bring-its-e-paper-tablets-to-more-scribblers/][hugely successful
|
||||
crowdfunding campaign]] and produced the reMarkable 1, followed by [[https://blog.remarkable.com/remarkable-2-the-next-generation-paper-tablet-91b47d0080cb][the
|
||||
reMarkable 2 in 2020]]. There are a few others by now but we'll look at
|
||||
reMarkable 2 in 2020.]] There are a few others by now but we'll look at
|
||||
the reMarkable first.
|
||||
|
||||
*** The reMarkable
|
||||
|
@ -335,11 +335,11 @@ It even runs Linux and the developers have opened SSH up so you can
|
|||
remote in and tinker with it as much as you like. Because of this,
|
||||
there's a pretty awesome [[https://github.com/reHackable/awesome-reMarkable][community of people creating third-party tools
|
||||
and integrations]] that add even further functionality. My favourite is
|
||||
probably [[https://github.com/bordaigorl/rmview][rMview]], a really fast VNC client for the reMarkable that allows
|
||||
probably [[https://github.com/bordaigorl/rmview][rMview,]] a really fast VNC client for the reMarkable that allows
|
||||
you to view your device's screen on any computer.
|
||||
|
||||
After watching all of [[https://www.youtube.com/c/MyDeepGuide][MyDeepGuide's]] [[https://www.youtube.com/playlist?list=PLsSI9-gaSSmiXwb7Vjk5Vb-nB41UTnrXd][extensive playlist on the
|
||||
reMarkable]], however, I decided to go with a different product.
|
||||
reMarkable,]] however, I decided to go with a different product.
|
||||
|
||||
*** Enter the Supernote A5X
|
||||
The [[https://www.supernote.com/#/product?type=SN-A5-X][Supernote A5X]] has all of the basic features the reMarkable has:
|
||||
|
@ -348,7 +348,7 @@ implementation, on the other hand, seems to be much more polished. It
|
|||
also lacks some features from the reMarkable while adding others.
|
||||
|
||||
*** Operating System
|
||||
While the reMarkable runs Codex[fn:3], a /"custom Linux-based OS
|
||||
While the reMarkable runs Codex,[fn:3] a /"custom Linux-based OS
|
||||
optimised for low-latency e-paper"/, the Supernote just runs Android.
|
||||
There are both benefits and detriments to this; on one hand, they're
|
||||
running all of Android, bloated that it is, on a very lightweight
|
||||
|
@ -367,7 +367,7 @@ Android.
|
|||
*** Community
|
||||
I don't usually browse Reddit but [[https://old.reddit.com/r/Supernote/][the Supernote community]] there is
|
||||
fascinating. I haven't looked around enough to know exactly what his
|
||||
relationship is with the company, but one of the members, [[https://old.reddit.com/user/hex2asc][u/hex2asc]],
|
||||
relationship is with the company, but one of the members, [[https://old.reddit.com/user/hex2asc][u/hex2asc,]]
|
||||
seems to represent Supernote in something of an official capacity. He's
|
||||
incredibly active and usually responds to posts and questions within a
|
||||
couple of days.
|
||||
|
@ -384,7 +384,7 @@ functionality would be implemented soon™. u/hex2asc responded /the day
|
|||
after/ and said that WebDAV would be supported but not earlier than May,
|
||||
ODF would likely not be supported, and cross-note links were definitely
|
||||
a possibility. Another community member has been avidly following the
|
||||
subreddit and even put together an [[https://app-rm.roadmunk.com/publish/03e6dca3d769e2b7015f7f48a649cb3f75f44d9e][unofficial roadmap]].
|
||||
subreddit and even put together an [[https://app-rm.roadmunk.com/publish/03e6dca3d769e2b7015f7f48a649cb3f75f44d9e][unofficial roadmap.]]
|
||||
|
||||
*** Interfaces
|
||||
|
||||
|
@ -403,7 +403,7 @@ possible UI variations while reading a book. This first one is default,
|
|||
with the editing bar at the top. It is exactly the same as what's
|
||||
displayed on the blank pages for hand writing full notes. From left to
|
||||
right is the Table of Contents toggle, the pen tools (fineliner,
|
||||
"fountain" pen[fn:5], and highlighter), the erasers, lasso select tool,
|
||||
"fountain" pen,[fn:5] and highlighter), the erasers, lasso select tool,
|
||||
undo/redo, context menu, palm rejection toggle, previous page, goto
|
||||
page, next page, and exit.
|
||||
|
||||
|
@ -433,7 +433,7 @@ right edge.
|
|||
*** Experience
|
||||
**** Reading content
|
||||
I love e-ink. I think it looks beautiful and would love to have an e-ink
|
||||
monitor[fn:4]. That said, the Supernote has an especially nice display
|
||||
monitor.[fn:4] That said, the Supernote has an especially nice display
|
||||
with 226 PPI (pixels per inch). The image below was taken with my
|
||||
phone's camera so it's not very good. However, if you zoom in a bit, you
|
||||
can see that the curved edges of some letters are /slightly/ pixellated.
|
||||
|
@ -446,7 +446,7 @@ Viewing with my naked eye at a comfortable distance, it does look better
|
|||
for ePUBs. A great many of my books seem to use a legacy ToC format that
|
||||
the Supernote sees and tries/fails to read before attempting to read the
|
||||
more up-to-date one. This is easily remedied by editing the ePUB in
|
||||
[[https://calibre-ebook.com/][Calibre]], going to Tools → Upgrade Book Internals → Remove the legacy
|
||||
[[https://calibre-ebook.com/][Calibre,]] going to Tools → Upgrade Book Internals → Remove the legacy
|
||||
Table of Contents in NCX format. You might need to make a small change
|
||||
to one of the HTML files and revert it before the save button is
|
||||
enabled. After that, just copy it back over to the Supernote and
|
||||
|
@ -484,15 +484,15 @@ well and I rarely have to make edits.
|
|||
|
||||
*** TODO Pong Isi and Volpeon when finished
|
||||
** TODO Migrating repositories between git hosts
|
||||
** TODO A perfect email setup (for me)
|
||||
** TODO A perfect email setup (for me) :Email:Workflow:CLI:Efficiency:
|
||||
:PROPERTIES:
|
||||
:EXPORT_FILE_NAME: a-perfect-email-setup-for-me
|
||||
:EXPORT_HUGO_CUSTOM_FRONT_MATTER: :toc true
|
||||
:END:
|
||||
|
||||
I've never been satisfied with any of the email clients most people use.
|
||||
I've tried [[https://www.thunderbird.net/en-GB/][Thunderbird]], [[https://wiki.gnome.org/Apps/Evolution][Evolution]], [[https://getmailspring.com/][Mailspring]], [[https://support.apple.com/mail][Mail.app]], [[https://roundcube.net/][Roundcube]],
|
||||
[[https://sogo.nu/][SOGo]], [[https://wiki.gnome.org/Apps/Geary][Geary]], and /many/ more. /None/ of them handle multiple accounts
|
||||
I've tried [[https://www.thunderbird.net/en-GB/][Thunderbird,]] [[https://wiki.gnome.org/Apps/Evolution][Evolution,]] [[https://getmailspring.com/][Mailspring,]] [[https://support.apple.com/mail][Mail.app,]] [[https://roundcube.net/][Roundcube,]]
|
||||
[[https://sogo.nu/][SOGo,]] [[https://wiki.gnome.org/Apps/Geary][Geary,]] and /many/ more. /None/ of them handle multiple accounts
|
||||
particularly well because all of the emails associated with that account
|
||||
are bound within it. Sure, you can make a new folder somewhere called
|
||||
~TODO~ and move all of your actionable emails to that folder but, when you
|
||||
|
@ -536,7 +536,7 @@ efficient and they will remain my organisation system of choice.
|
|||
*** The tools
|
||||
In short, the tools we will be using are...
|
||||
+ [[https://www.offlineimap.org/][OfflineIMAP]] to download our emails
|
||||
+ [[https://notmuchmail.org/][~notmuch~]], the primary way emails will be organised
|
||||
+ [[https://notmuchmail.org/][~notmuch~,]] the primary way emails will be organised
|
||||
+ [[https://afew.readthedocs.io/en/latest/][~afew~]] to apply initial ~notmuch~ tags based on subject, sender, recipient, etc.
|
||||
+ [[https://neomutt.org/][NeoMutt]] to interact with those emails, reply, compose, add/remove
|
||||
tags, etc.
|
||||
|
@ -772,7 +772,7 @@ OfflineIMAP's.
|
|||
This section just sets the defaults. It uses port 587 (STARTTLS) for all
|
||||
SMTP servers unless otherwise specified and enables TLS.
|
||||
|
||||
#+BEGIN_SRC
|
||||
#+BEGIN_SRC text
|
||||
account user@example.com
|
||||
host smtp.example.com
|
||||
from user@example.com
|
||||
|
@ -820,7 +820,7 @@ I can't give other examples.
|
|||
You could also just use the same method I described in [[*Repository][the Repository
|
||||
section]]! It will work perfectly fine here as well.
|
||||
|
||||
#+BEGIN_SRC
|
||||
#+BEGIN_SRC text
|
||||
passwordeval gpg -dq ~/.mail_pass/use_exa.gpg
|
||||
#+END_SRC
|
||||
|
||||
|
@ -896,7 +896,7 @@ it; it's just pressure-sensitive.
|
|||
[fn:4] There does seem to be a group of people interested in just such a
|
||||
thing: /[[https://alexsoto.dev/challenges-building-an-open-source-eink-laptop.html][Challenges Building an Open-Source E Ink Laptop]]/
|
||||
|
||||
[fn:3]Taken from their [[https://support.remarkable.com/hc/en-us/articles/360006699537-About-reMarkable-2-][support page about the reMarkable 2]]; search the
|
||||
[fn:3]Taken from their [[https://support.remarkable.com/hc/en-us/articles/360006699537-About-reMarkable-2-][support page about the reMarkable 2;]] search the
|
||||
page for /operating system/ and it should show up.
|
||||
|
||||
[fn:2]I dislike Apple's operating system, their hardware, business
|
||||
|
|
Loading…
Reference in New Issue