Decent read, but dated. Hardy painstakingly goes through each and every
reason as to why pure math is the one true calling, making some
axiomatic guesstimates along the way. The logic is fairly sound however
I do not know if the same could be said for his premises. This is the
main point of contention that you can draw with it.
Of the quality of his message, is it outdated? Yes. Does it still hold
up today? Sadly, still yes. He hits the nail on the head when he sums
up the motivations for an academic.
The first (without which the rest must come to nothing) is intellectual curiosity, desire to know the truth. Then, professional pride, anxiety to be satisfied with one’s performance, the shame that overcomes any self-respecting craftsman when his work is unworthy of his talent. Finally, ambition, desire for reputation, and the position, even the power or the money, which it brings.
Overall a quick read and smooth at that. It is a bit to follow the logic at times but otherwise not to confusing. His worldview is pretty cold (unsurprisingly) but not out of line. Pretty ironic to consider that math is not as harmless as he'd like. I can only think of the atomic bomb being one counterexample but I am sure there are plenty more.
So a while back (over a year ago :x) I got
the Milk-V Duo 256M, but I never did anything with it because I didn't
want to fool with the UART all the time and I thought the network over
USB wouldn't work (I was wrong) and the toolchain was a mess. Anyways
being on FreeBSD I couldn't just use the provided toolchain because it
is only built for Linux, and unsurprisingly you can't link Linux
binaries against FreeBSD. However, the second time around it was a lot
easier than anticipated.
Problem One: Connecting over USB instead of UART
Really easy. I checked to see if the interface showed up...
and it did first try B). Next I popped an IP address for it
with dhclient
And voila! Now I could just ssh in
with the address and creds from the documentation.
Problem Two: Building the toolchain
Not a big deal on the surface, but turned into a complete mess. I started by
pulling from the RISC-V
Toolchain repository
and it goes super quick. So next I pull down the dependencies from
pkg
and honestly just hope for the best when some aren't there. make musl.
A lot of the projects
that it depends on are just linked in so on build they are pulled down
ad hoc with git submodule update --init --recursive.
However, the mirrors for something like half of them
are broken! So then I spent 30 minutes looking for source mirrors that
weren't seven years out of date and adding them to the git config.
Finally everything pulled down without issue and started
building. But of course it wasn't that easy. There was some missing
capabilities missing from the compiler or whatever producing a lot of
#error messages. I went for the easy way out
by deleting the offending lines then recompiling. But again, not that
easy. The file was autogenerated, so I then had to find the awk script
that was being such a drag. Finally I found it and commented out all
the lines with #error without remorse (my patch file). Once it built surprisingly
everything worked without issue and I just add the toolchain prefix to
my makefiles.
I probably broke something but the Hello World worked so I don't really
care :). Everything went over scp
without issue so problem solved. I have some benchmarks and am planning
on messing around with the vector extension and some SIMD but that will
be for a future post.
I just tried pulling the repo again and they fixed the references so now
it works T_T.
Pretty good read, but on the longer side and fairly verbose at that.
It is very obvious that it was originally intended for serialization
because the story starts slow and there is plenty of redundant
information throughout.
With regards to his style, I didn't find it out of the ordinary, but
it was good nonetheless. Dickens is so widely quoted and copied that
it makes his actual work feel cliche even though it is his style.
His social commentary is exaggerated to the point of exhaustion. In
this regard Dickens' characters outside of the main circle are little
more than stereotypes. Overall though, the plot is beautifully
constructed and his storytelling is one of a kind. He sets up every
little detail at the beginning then by then end everything meshes
together just right and it is very satisfying. No loose ends. I found
that reading it like a novel was a little exhausting, however taking it
one chapter at a time would probably be a great way to enjoy it. There
is a lot of redundant information throughout so forgetting small bits
isn't as detrimental as it is to other works.
An unexpectedly great novel! I didn't know what to expect since I
picked it up second hand on a whim, but what a read! I was expecting it
to be modern in style with the typical Hemingway-esque sentences and
pacing, however Williams' style was not quite the opposite but still a
much more refined approach than most post-war writers. It is very
deliberate, calculated way that was very easy to read. He is mostly
conventional but with some scenes regarding dialogue he favors the
modern style of cutting long conversations in favor of keeping them open
ended.
There was absolutely zero action in the novel. When I say zero, I mean
nothing that would make you out of breath or hold it. It's a sad story
overall but still moving despite it. I truly enjoyed this book but I
think that saying anymore would be spoiling it. It is just such a solid
book in ways that I can't seem to describe. I absolutely recommend
reading it. It's not exactly short at around 375 pages and it is a gray
book (that's really the only way to describe it) but it is worth every
single page.
Interesting novel. It is essentially a philosophical treatise behind a
thin veil of fiction. Closer to an allegory than anything else. It is
like Orwell's Animal Farm in that regard, but more dense as it
is not constricted to allegory.
Camus is a very strong writer. The Stranger is one of
the most brilliant novels let alone pieces of literature I have read.
The issue is that it is too strong, but this necessitates its brevity.
I can only describe its sensation as one of a chocolate liquor.
The prose was terse yet this was for a lack of meaning, but merely the
essence of the matter. Camus is so capable of distillation that not a
single character on the page is wasted.
The lack of fine-grained detail is both a curse and blessing. On the
one hand the reader is left to fill in most of the physical details
which does make it a more involved read, however this also leaves the
philosophical questions almost completely unhinged from the context in
which they take place. In this I think Camus has managed to create a
truly "great" book: one that is able to speak across generations and
cultures. Raymond could be any other sleazeball at any other time or
place and Meursault's plight would be unchanged.
I was very pleased with the brief Translator's Note. Often I find that
introductions are prone to spoiling large portions of the plot but Ward
did a great job of pointing things out without revealing them in their
entirety. Re: translation, as far as I can tell Matthew Ward's
translation is much closer to the original French in terms of style, but
supposedly other translations are better written. Anyways, I found the
1989
Vintage edition to be more than enough.
Stylistically I found it interesting, but not exactly groundbreaking.
Written as a stream of consciousness it is exhausting to read. I don't
disagree with Kerouac's use, however it is a sticking point nonetheless.
The first chapter was the worst in this regard as Kerouac establishes
the story with nasty blend of jarring, short sentences and longer ones.
The rest of the novel was fine though. I found that Kerouac really
pushes the pedal and you start to speed up and the sentences go one
after another and on and on in a way that I am just not used to.
Typically when writing is described as "poetic" it is just another
note of imagery but Kerouac is a certified master of rhythm; his control
of the tempo of reading is superb and I found myself just letting my
eyes go over the text letting the natural cadence of the words take me
instead of a more thoughtful and metered reading. In the same vane
there was plenty of onomatopoeia. Not particularly out there but still,
a nice addition.
Regarding the plot, there really wasn't a concrete one. Another gripe
with the first chapter was that it revealed Sal and Dean's modus
operandi, in my opinion, prematurely. Essentially the book is about
Sal and Dean crisscrossing the country and the journey along the way.
No complaints about the plot, even with a murky ark its not a big deal.
The various themes that Kerouac addresses are typically American and most
are purely conventional. Sal's hope for success is the exact same as the
49ers of the California gold rush and the settlers of the Northwest
Territory. Both blindly leave their homes in search of vast
wealth—in Sal's case abstract— and do nothing but search.
Viewed in this light, On the Road is as unique as sand on a
beach.
The way that it diverges from the typical American canon is the emphasis
on human connection as a way to discover truth instead of through
nature. This also shows a fundamental turning away from the sciences
towards the humanities as the primary way for interpreting the universe.
All throughout Kerouac places huge literary emphasis on how
people act, not their surrounding environments, and how this serves as a
source of fascination to Sal et al. instead of more concrete things such
as beauty. In a larger view it explains the whole aim of "the road": to
see as many different people and lifestyles as possible; a literal social
expedition. This really puts a new spin on the rampant hedonism
throughout the book. It shifts the purpose of substances from being one
of personal pleasure to one of a shared communal experience and further
understanding. Alcohol goes from being something to make you forget
your troubles to being something that makes it easier to share those
with others.
All in all a good read, but not a heavy one by any measure. Pretty
modern so if that's not your cup of tea I wouldn't bother.
Nice little essay. Quite short at about 40-60 pages depending on how large they
are. It took me between an hour and a half and two hours to read cover to
cover. While the style is antiquated (mid nineteenth century; same vintage as
Melville), it was only occasionally that I would find a sentence too difficult
to parse with only one pass. Thoreau often would wander away, saunter if you
will, from his argument and while over a longer essay it could certainly be
confusing, he never strays too far so that by the end the beginning is still
fresh. His style is more flowing than Melville, but still more focused than
most French or Russian writers. There were times that his descriptions of
Walden (the pond by which he lived) became tiresome, and of course the many
descriptions of the locale are not necessary to further his argument, however
overall Thoreau did well to water it down.
His etymological dissection of "sauntering" was novel and in my opinion the
most well done of any time I've seen something open with a definition. I just
accepted it as a rule that beginning with "The ___ dictionary defines..."
should be avoided completely and all the times I've seen it used it always felt
lackluster. Now certainly Thoreau was ahead of the modern overuse, however his
care and attention to detail really shone through. The two possible origins for
sauntering that he presents are Sainte-Terrer and sans terre
which play off of his lifestyle in the material sense, but more accurately in
the abstract. Granted, Thoreau did have his cabin so he was not truly sans
terre, but mentally he was at home as long as he was in nature and
by his words, "in the good sense, will mean, having no particular home, but
equally at home everywhere." This combined with his (and really the
Transcendentalists) search for spiritual truth—not nirvana per se, as
Buddhism was not a direct influence on the movement, but the idea is a good fit
nonetheless—makes his portrayal of himself as a pilgrim towards nature a fitting one.
The scope is fairly limited, which is to be expected for an essay, however
Thoreau really doesn't consider anything much outside of one's personal
relationship with nature, and further restricts this to specifically walking
while making only passing mention of fishing or light work and hardly any
mention of the work that occupies the large majority of one's day. This is too
harsh a criticism and in truth Thoreau was one of the few Transcendentalists
that actually "walked the walk" as opposed to say Emerson who took a more
philosophical as opposed to practical approach. Even so Walking is
more idealistic than Walden is, almost bordering daydreams.
I think that with all this considered it is a fine piece and though it is
severely optimistic and quite obviously painting Thoreau's reclusive way of life
in a rosy lens, Thoreau cannot be blamed for it. Throughout all his writing
Thoreau maintains his cheerful disposition so while Walking could be
viewed as propaganda for the Transcendentalist lifestyle, I think that Thoreau
is qualified to talk the talk.
Good, and almost but not quite great, read. Her style is very nice, however
there were times that I found her writing a tad repetitive. It is one of
Woolf's earlier works so I am not suprised by this and it definitely made me
want to read her better work, but regardless it holds the novel back from being
a "great" novel.
The plot was deathly slow. That being said I did enjoy the story, however the
emphasis is moreso focused on the characters even though at first glance it
appears more melodramatic. Woolf handled the secondary characters exceptionally
well, but for much of the novel I just could not sympathize with Katherine. Yes
she is introverted, yes she is cold, yes she is self-absorbed; there is nothing
wrong with that. However this is what makes her indecision between William and
Ralph (her suitors) unbearable. It was ridiculous to see her choose between two
men that treat her equally bad, just in a different way.
The one thing that bugged me so, so much was how Mary Dachet was
utterly discarded after the midpoint of the novel. She was so much better and
personable and well rounded than Katherine, yet lost out for no reason. I
suppose this is me complaining that "good" did not win, but is that so wrong?
Overall good stuff. I would recommend reading a used copy or one on sale.
P.S. I forgot to publish this even though it was finished two weeks ago.
Yikes.
This film is without a doubt one of my new favorites of all time. Just
everything about it is done really well. Firstly the cinematography: not
perfect, however this contributes to the film as a whole. The mix of
traditional shots with rougher shots and jump cuts, but also with more meditative
scenes. The director did a good job of using these to control the mood as well
as the pacing. Somewhat of an exception to this is the overlays of the forum
text, but I didn't feel that they were too fast paced to read or be confusing.
Re: the forum; it added a lot to the story and commentary behind the film. It
was a little hard at first to connect the characters to their aliases, however
slowly but surely you can connect the dots to most of them. It was a little
ridiculous how by the end it seems everyone listens to Lily Chou Chou but only
talks about her online.
The vacation bit was a good bridge between the two halves of the film, both
visually and with regards to the plot. This portion of the film is done
entirely with handheld video cameras from the perspective of the characters.
Something that I have to give the director a lot of credit for is keeping a
good balance between the static shots and more emotive ones. Some of the shots
require just a little bit of disbelief to be suspended, but that's alright.
The role of technology in the film is interesting in how subdued it is. Even
though the characters' connection to Lily Chou Chou and their outlook on life
is shaped by this medium that we never actually see. I think that there are a
couple of things that motivated this choice, namely: simplicity of the world,
anonymity of the characters, and to emphasize the concept (also play on words)
of "the Ether". Firstly, it makes the plot easier to track without specifics,
and truthfully, is it really needed? This would then make it confusing to have
the quotes from the site shown over other scenes, etc., so overall I think taken
on it's own this is a good enough reason to leave it out. Secondly, even though
it is at times obvious that the people interacting online are the ones from the
main story, by only showing Yuichi (who we know is on the site) I felt
that it anchored the plot around him really well.
I couldn't give you an exact definition of "the Ether", but it definitely is a
modern take on the concept of "the Sublime". The common thread that binds all
of the characters appeal to Lily is the way in which she captures each of their
individual understandings of life. While unrealistic the universality of her
music highlights the power of music that is lacking in most other forms of
media. In this sense even though music is considered a "low" art, it's appeal
is more broad.
Overall a really great film, but there are a couple parts that are really
tragic. Would definitely recommend any day of the week.
Really good novel! Structurally and setting wise it is what Hardy's
Tess of the D'Urbervilles aspired to, yet honestly I felt that because
of this Bronte spoke her mind much easier and unobstructed as opposed to Hardy
ocasionally falling back to more telling (as opposed to showing) than I felt
necessary. The many character's stories are all intertwined and—something
that I only noticed towards the end of the novel—Bronte "ties off" the
loose ends, say her adopted sisters. I found that because of this the plot
didn't exactly dissolve, per se, however it was not hard to guess the direction
of the plot towards the end. There were a fair amount of major plot twists and
I felt that most were not too extreme, but there was one that I could just not
get over about halfway through that was just over the top. When I say
absolutely out of left-field I mean it.
The imagery was much more reserved. The novel was heavier on internal
reflections and it was quite well suited to the plot. The introspection
would sometimes take a backseat for more melodramatic episodes (e.g. her childhood,
the visiting guests, etc.), yet this contributed to Bronte's commentary on class
as the upper class were accompanied with less charactrerization.
Jane is a strong character, and exceptionally perceptive, however at times she
is simply too perceptive to the point of stretching the first-person structure.
I understand the rational behind passing the novel as an autobiography, but in
my opinion Bronte loses much of her freedom to develop other characters
in exchange for the title of a "autobiography" that reduces to essentially a
farcical footnote. Also with regard to the romance element, I felt that it was
handled very gracefully. Personally I think that while Jane's choice between
her suitors was not entirely real, it does underly how in the end intellectual
connection trumps phsical attraction. This is reemphasized a couple of times
through her suitor's choice of her over other women.
Overall great read, but not a short one. The first hundred or so pages went by
very slowly, the next two hundred were at a nice pace, and the last two hundred
absolutely flew by. I just couldn't put it down towards the end.
Just a short note, but FreeBSD (kind of) has a wireless setup daemon! You just run
# bsdconfig wireless
Wish I remembered this sooner . . . but it doesn't matter because I'm using wifibox anyways :|. Still holding out for working drivers in 15.1 though (-_-)>.
Good novel, but not quite great. The narrative structure was not very coherent, but to almost no end. The weak
frame narrative of Brigge's time in Paris seems completely tangential to Rilke's messaging, and it certainly doesn't
help that he discards this and Brigge's "now" is never revisited after about a third through the novel. It was not
exactly shocking that this is how Rilke intended it as Rilke was mainly a poet, however it is still disappointing in
the novel format.
Stylistically it was plesant to read and there were only a few times that he went over board with the poetic
language. I found it a little more difficult to read because of this, but this could also be owing to the translation.
I forget where I read it (I think the translator's notes) but a lot of Rilke's style that is so distinctive in the original
German is lost in the English version just because of inherent incompatibilites betweeen German and English.
For this I would still say that in general The Notebooks of Malte Laurids Brigge is a great book, but
I myself couldn't see it in the english.
I think that the commentary that Rilke has on life and death is interesting, but for some reason I felt that it lacked
weight. The characters and plot (if you could call it that) were just too
flimsy to make me care.
Wasn't bad, but not super compelling. I wouldn't buy the book, but from a yard
sale or library I think it would be worth its weight.
Back to FreeBSD on the laptop because I though wireless was fixed for
rtw89 (its not), but turns out wifibox can do the trick so now that
works. However, the configuration was not the easiest in the world. Because
wifibox is not the default driver, wpa_supplicant.conf goes under
/usr/local/etc/wifibox/wpa_supplicant/. I thought at first that I
could just soft-link different presets in, but WRONG! Of course wifibox
needs the configuration file to be physical >:#. Anyways
WPA confuration was easy peasy.
The first obstacle I ran into was using my school's open network. I could not
for the life of me figure out the combination of values for an open network from
just the man page but setting key_mgmt=NONE did the trick (with the
SSID entered of course).
The next obstacle was DNS. I normally run local-unbound but on the school
network and in the public library, root DNS queries are blocked. This isn't
really an issue (just set new nameservers in /etc/resolv.conf) but finding
those servers can be a real challenge. Eventually I narrowed it down to having
to do it though the wifibox console.
# dhcpd -o domain_name_servers -T | grep dns nd1_rdnss1_servers='::1'
This is a bad example as I havent attempted IPv6 with the bridge, but basically
the point is that you have to grab the dhcpcd data from the VM and add it to the
host. Pretty annoying to be honest, but hopefully with FreeBSD 15.1 the drivers
will be stable enough for actual use.
I wrote a little script so that I wouldn't need to copy files over manually when
I wanted to switch networks.
#!/bin/sh if [ `whoami` != 'root' ]; then echo 'Must be root' exit fi if [ -f /usr/local/etc/wifibox/wpa_supplicant/wpa_supplicant.conf.$1 ]; then echo 'Switched config to' $1 cp /usr/local/etc/wifibox/wpa_supplicant/wpa_supplicant.conf.$1 /usr/local/etc/wifibox/wpa_supplicant/wpa_supplicant.conf wifibox restart guest else echo 'Invalid config' fi
(2026.07.26) P.S. It's a whole lot better when the drivers just work. Who would've thunk . . .
The first half was eerily similar to The Catcher in the Rye, very
typical bildungsroman. The second half, however, is where Plath really
starts to expand on her commentary. It is a very well studied book, and for
good reason, but I think that there definitely should be a warning associated
with it. Plath goes into a fair amount of detail with regards to self-hard,
suicide, etc. so I wouldn't really recommend it if you are irked by that stuff.
I think that the message is easily hurt by her inclusion of this as depending on
how sensitive you are the novel could just be a net-negative.
I instantly thought of the bell jar from Zamyatin's We and how it was
used in the same way as Priestley,
however in a malicious way. I think the analogy definitely holds when you
consider how Esther is gradually ascending the social ladder, and as you get
higher air pressure decreases. I think it makes more sense than the traditional
bell jar symbolism because instead of her just being preserved like decoration,
she is actively being tortured by her observers. But . . . I'm probably stretching it.
Stylistically I liked it. I think that there are some times where she gets a
little, lost, I suppose. Nothing world-ending, but I didn't think much of it
because at the end of the day she was primarily a poet. It was a little more
stream of consciousness than Salinger, but the main similarities were in the
structure (I was actually inspired to reread The Catcher in the Rye
because of this). I think that it's a good novel, but it's not the best. I
would place it above The Catcher in the Rye in terms of `deepness', but
it was in the same ballpark of nuance and appeal to angst. If The Catcher
in the Rye was aimed at fourteen-year-olds, The Bell Jar would be
aimed at seventeen-year-olds. All in all worth the read though.
Really amazing watch! It is a striking combination of both loose sci-fi and psychological themes all in an approachable setting. First: the plot; the characters are very tastefully done, with just enough craziness that makes it almost real.
Genuinely agonizing watch. I thought it would be cool and indie, etc. but it was just bad. The cinematography is alright and the plot is so-so, but the dialog is just awful. Don't bother.
I finished this book a while ago and even typed it up but totally forgot to
upload. I'm super behind on the reviews so there will be a bunch coming in
(hopefully) soon.
Got this book from a thrift store so I really didn't know whether it would be
any good or not, but I think that it paid off. It is a moderately long novel,
coming in at around 450 pages. This isn't without cause though as the scope of
the novel is fairly large (time-wise). The beginning was slow, but it
eventually got up to speed; not very quick but a nice trot. Hamsun is a
Nobel-laureate and it shows. I was a bit put-off, however, from the first chapter with
regards to the syntax. It started off extremely terse, but whether it be that I
built up a tolerance or he loosened up the story flowed much easier once I got
into it.
I really like the subtlety of the first two-thirds of the novel, but pretty soon
after the 300 page mark there were moments that were simply too preachy. Hamsun
mainly addresses the changes in Norwegian culture due to the Industrial
revolution and urbanization, and by choosing to focus on an admirably average
rural youth he pulled off his gradual transformation quite well. His mood
varies along with his wealth/status, however there is a secondary shift towards
bitterness and a desperate world-view. Hamsun severely
only hamstrings his commentary with the obvious self-insert of one of the
neighboring farmers. In the conversations about America and the pros and cons
of emigration, he is almost shoe-horned in to juxtapose the blind faith of most
of the workers and this witty and trite farmer. It reduces the near credible
observations that he makes into a straw-man. He's not wrong in attacking the
"grass is greener" mentality, but the way that he does it is superficial and
avoids valid reasons for emigrating to America.
All in all it was an enjoyable read. There were strong undertones of Norwegian
nationalism, but I think that was par for the course considering the context in
which it was written (1920's Europe). It was hard for me to separate
romanticization of the setting from fact so I couldn't say how accurate his
portrayal was. It is the first in a trilogy, but I wasn't inclined to read any
more. I would rate it as "buy if cheap": a good read that's not worth full price.
I figured it was high-time that the blog had a RSS feed and I had a
little extra time so I got to work. I was a little intimidated at first
because I really didn't know anything about RSS itself beyond putting a
link into a reader. There are two competing formats that are very
similar at first (both use XML) and share similar histories, but are not
compatible and have varying adoption across feed readers. From a little
research, I found that the 'RSS' standard was the simplest. However,
this comes at the cost of embedding HTML. The alternative is the Atom
specification, but this is still a little tricky as the 1.0 and 2.0
versions are not compatible. I went with the 2.0 standard as it seemed
to be the most common across blogs I frequent and the documentation was
fairly straightforward compared to the others.
I hooked the feed generation into the build system like any other page
(new script in ./build/), but this was a tad limiting in the
amount of custom entries I can add. Because the feed is regenerated at
every build it isn't feasible to manually edit after building, as it can
easily get written over. I'm planning on adding another folder of
manual updates that get spliced in but I don't think there's much use for
them now. Right now the feed is just a mirror of the Blog. I haven't
figured out how to embed HTML into the feed but I don't know if I'll do
it either because I'm not putting the whole article in the feed.
It's really common to have an abstract for the posts in the feed and
I really, really, considered it but (1) the posts are pretty short, (2)
I don't want to make a system of abstracts whether it's headers in the
post's source or another directory containing them, and (3) I don't want
to write abstracts for all of them. I kinda wanted to make a
rudimentary macro engine with sed for emojis, etc. but there's
just no way that it would be worth the effort.
Speaking of feeds, I needed a reader too. I wanted something simple
like w3m where I can have one feed per line and pressing enter
would open it in a browser or wherever. Oh and Vi-style keybindings too
:). I tried a couple of TUI feed readers but most of them were
way overkill for what I wanted, having three panes and all the bells and
whistles. I settled on using sfeed and kludged it together with
some shell scripting. Basically, sfeed is only the part that
converts the XML file to a format for other readers, but . . . there's
sfeed_curses for actually reading it. Luckily it had Vi-style
keybindings so I settled on using it. I used curl for downloading
the feeds, with a URL per line in a file under ~/.rss/.
However I didn't want to make calls out to the feed every time I wanted
to read so I separated reading and downloading into two scripts:
fr to fetch the RSS and rr to read. I didn't want to
keep track of manually fetching the feeds though so I added it to my
crontab to run at boot and every even hour. Definitely over engineered
but I haven't had the urge to change it recently so it must be good.
Anyways, you can check the feed out here.
I have a blog post detailing the RSS feed done but im too tired to type
it up :')
Anyways, inspired by some video, I don't remember by who, I got tired of
spaning stuff like mpv or xpdf and having a terminal
sticking around. There's something you can do with dwm but
that seemed way over the top. My little manual solution was to run the
command in the background with & then close the terminal. For
what it's worth, Bash complains that you have jobs left running, but the
traditional BSD shell (which I'm using) doesn't so it makes the function
easier but disowning the process is not especially hard. The little
function I wrote is this (named eat in reference to swallowing windows):
eat () {
$@ &
exit
}Basically it just runs whatever you put after eat in the background and kills the terminal. Simple over right any day ;)
Good read! The prose was quite good, especially with regards to the
sentence structure. The best way that I can describe it is Melville
done right. The use of semi-colons and em-dashes is still liberal, but
unlike Melville or Thoreau, Hardy's thoughts don't spill into run-on
sentences that become hard to parse with the many nested ideas. The
world-building (I suppose it is a more secondary aim as opposed to later
works, but regardless) is also notably good. I was a tad daunted at the
beginning with all of the names of the various hamlets and villages, but
as the story progresses they are memorable enough that even if the
precise location/meaning is not immediately known, it would still not
pose an issue to understanding the novel at large. The scenery quite
obviously (in retrospect) reflects Tess' emotions and actually
tastefully anticipates her according changes in character. I found it
hard to keep a precise gauge on the passage of time, but major events
all line up. But it really serves as reflection of Tess'
disassociation in response to certain events (I shall not spoil it) so
it is definitely to some literary end.
Another aspect was the delay between the
injustices and their complementary justice; however because of Tess'
passivity for much of the novel, the ending is not foreshadowed in the
slightest. Unlike say Crime and Punishment, this tension
between right and wrong is not what drives the plot forward, instead the
world seems to move around Tess, pulling her and the conflict along. A
large part of this is her internalization of guilt for something that
she had no will in whatsoever, so for better or worse this is what reins
the plot back until the end where she takes back, almost literally, her
agency. I'm not knowledgeable—truthfully not one bit—about
the Victorian period so I'm sure that there was plenty of context flying
right over my head, but to me the core of the novel was very
approachable and I didn't find my enjoyment hindered by this lack of
context. There were plenty of references to ancient literature, though
for this I had to fall back on the footnotes as they were more cryptic
than the quotes to contemporary poetry that were sprinkled in as well.
Now I suppose this could be controversial, but after the fact I don't
think that I like Angel very much. Provided, he is not evil in the same
sense that Alec is, but it seems as if his judgment completely
evaporates for a good portion of the novel, and his motivations seem so
out of line with his character that it incriminates his whole demeanor.
Looking back, it is almost as if his more rough-and-ready attitude from
the dairy was just a shallow attempt at rebellion to his clerical roots.
There is much more that I could write, but I'm trying to keep my reviews
spoiler-free (for the most part), so that pretty much sums it up. It is
not the shortest read (around four-hundred pages) but if Victorian
literature is your thing it will not disappoint.
I recently purchased a typewriter off of shopgoodwill.com
because why not? It came in good cosmetic condition (save a small crack)
and the mechanics were mostly in good condition as well. It was fairly
dusty but nothing a wet rag can't fix and the crack was on the back so
it isn't noticeable unless you are looking for it. I'll get onto the
mechanics in a little, but here's the run down of the machine itself.
It is a 1980's Royal Safari produced by Messa in Portugal. It was a low
end machine and the case is plastic, but this is actually a
benefit as it is very light (comparatively) at only 10lbs. It has a
cream-colored body with dark brown cover and case. I have to say that
it looked ugly in pictures, but in reality it is quite nice. It has a
three position ribbon selector: black, stencil, and red; three position
adjustable touch, and even an one key! It has a Pica typeface (10
characters per inch = 12 point) that looks alright. It comes with one
inch tab-stops, but I'm reluctant to use them as they move the whole
typewriter when it moves :'). I've seen other people put mats
under it so that it has more grip, but I think a little furniture
mesh (the stuff under carpets) would work alright.
Typing on it has taken some getting used to but it is funny in that it
is a lot closer to piano than I would have thought. It's a lot
different from a mechanical keyboard in that you can't "glide" over the
keys in the same way. The type-bars need to get out of the way in time
for another one to strike. I don't know exactly how it has affected my
typing speed, but I think I'm probably around 75% of my normal typing
speed, not to mention the carriage return.
The mechanical issues were fairly straightforward except for one: the
mainspring. When I first started using it I noticed that after passing
the six-inch mark the carriage wouldn't advance. The thing pulling the
carriage forward is a drawband (a piece of strong fishing line,
basically) connected to the mainspring. Because it's forty years old,
the spring had broken and was loosely slipping in its case. Luckily the
break was near the end so it did not need to be replaced. There were
four options for repair: put it in reverse and see if it worked, put it
in the right way and hope it would hold, bend the end into a hook (like
it was before it broke), or put a hole in the end to act like the hook
(what most other typewriters do). I'm ashamed to say I tried the first
two, and they didn't work. So now I was down to the two latter options.
Because the spring is made of spring steel, it is very strong, however
it is not very flexible, so to put the hook in the material it needs to
be heated, however this can make it lose its temper. The easy way out
was to put a hole in the end to hook the little notch, however this was
complicated by the fact that the spring's width was only about a
millimeter to two millimeters wider, so the tolerances are tight. I
tried using just a drill, but this caused the end to snap so I used a
Dremel next. It took a little bit, but eventually I got the hole big
enough to fit the notch. Reinstallation was not very hard, but the
tension needed a little adjustment.
Even though it was really annoying, I love fixing the typewriter! Being
able to visually see the problems is a nice break from debugging hell
and Valgrind. I suppose typewriters were the original WYSIWYG editors,
but thats stretching it a little ;).
It's been a while! But that's because I bit off a little more than I
could chew (at least quickly) by reading Moby-Dick. Let me
tell you, this book is not for the faint of heart. Some books, like
The Brothers Karamazov or The Count of Monte-Cristo
are long, but understandably so. They are more plot heavy and of course
fairly dense, but while they are long it doesn't feel like a chore to
read. Moby-Dick on the other hand is long, but really short;
not much happens, but a lot happens, if that makes any sense. The story
itself takes place over a long period of time—whaling voyages
would take place over three to four years—but the lack of a
definite time scale makes the plot look less like a time-line than a
slush of details and places. I'm sure that if you had a better grasp
than I on the geography of the South Seas and the Pacific then it would
make perfect sense, but many of the places are so antiquated that it is
hard to find references to them outside of the book, so even Google Maps
won't help. This confusion, however, serves to emphasize Ahab's own
descent into madness as the location gets less and less precise as the
story progresses.
The prose itself is very much like Thoreau in the sense that it wanders;
not as dramatically as him but still significantly. If Melville
sometimes gets off the path, Thoreau is no where close to it. I now
know more about whaling and whales than I ever would have thought there
was to know. Truth be told I was getting bored with some of the
chapters on whale biology but there was enough action interspersed and
the many chapters of background do help to flesh out the world. The
ending was quite anti-climatic though, having the five-hundred and fifty
pages all culminate in such a short time.
Definitely worth the read, but if 19th century American literature is
not your thing I wouldn't force myself to read it. That being said,
don't read the abridged version because then you lose almost the entire
point of the novel.
Really great read, but especially a fall read. Kind of a shame that I
read this in winter, but no matter. The book consists heavily of
autumn imagery and can sometimes be a bit much, however taken in context
of Dandelion Wine, both novels are set in the same town, it
paints a very vivid picture of the town and especially serves to
highlight the subliminal time between summer and winter that the book
occupies.
The atmosphere is really great but I wont get into it here. However
one of my qualms is his overuse of climax,
to the point of exhaustion. Otherwise stylistically I found it quite
enjoyable.
Even though the characters are only boys, he does a good job of making
them mature enough to make decisions, yet still realistic. I think that
he achieves this through juxtaposing their (Will and Jim's) amplified
feelings of fear as opposed to Will's father who is much more stoic.
I would say that it was better than Dandelion Wine, but more
so because of the plot. The story picks up fairly quick and keeps good
pace. The chapters are short, but it does not interfere with the
overarching plot. Something Wicked This Way Comes is
definitely the continuation of it, but with the polish and
refinement that Dandelion Wine lacked. Overall a great read.
Would recommend.
This novel was very good! It is a coming of age story set in small town
Illinois with the protagonist an eight-year-old boy (Douglas). Not a terribly
heavy read, but interesting enough to be thought provoking. I found it
to be a great night-time read because of the fact that it was episodic
in structure. On the one hand, I definitely enjoy long books and plots,
but the development of the characters was by no means hindered and even
was enhanced by the breaks in the plot. The gaps in story smooth over
otherwise somewhat abrupt jumps in maturity of the characters. However,
it also gives a chance to see more of the town outside of the actions of
Douglas. These episodes give us a chance to see Green Town through his
eyes and see his change from the inside out.
Thematically I found it concise, yet not preachy. The main concern is
mortality and Bradbury skillfully addresses this both head on and
indirectly. Douglas, being a child, views his current state as his only
one. The conversation between the old lady and the children, wherein
the children cannot relate to her because she seems so far removed from
them, both physically and mentally. The Colonel also seems immortal to
Douglas, like the summer, bottled up forever in the dandelion wine.
However, slowly Douglas has to come to terms with initially others
mortality: the Colonel dying, the trolley stopping, his Grandmother
dying; but this second-hand knowledge of death is not fully realized
until the ending.
Douglas watches all of this, still somewhat removed, but the encounter
between the woman and the Lonely One finally starts to bring this
reality of death closer to home than he really realizes. The whole
experience to him feels almost surreal. He makes excuses as to why that
couldn't have possibly been the Lonely One not out of real speculation
nor even a desire for the drama and excitement that the murders brought,
but because the death of the Lonely One—a legend; a curse; someone
untouchable—is another blow to his conceptions of his own
invincibility. If a serial killer, seemingly no more real than the
cowboys from the movies, was killed, couldn't it happen to him as well?
And this is where I found that Bradbury really excelled. Taking a trait
more commonly associated with teenagers and young men, and adapting it to
a younger protagonist made the theme stick out, not necessarily
elevating it, but more so eliminating other conflicting issues that
could have clouded the theme.
Tying into this, but taking on a more subtle role is his exploration of
the sublime. The warm weather, the new sneakers, friendship, all cannot
be captured. But the dandelion wine exists not for the summer, but for
the winter, as to relive these happy moments, if only for a second. And
in this I think that Bradbury hides a deeper metaphor. The dandelions
are the fruits of life, not intentional, but nature itself poking
through. He emphasizes this with Grandpa's abhorrence at the idea of
dandelion free grass. Although the lawn is cut and tended to, nature
still provides beauty in its dandelions. However, the pressing of this
nature really points to the role of artists in capturing the sublime.
Whether it be through poetry or painting, song or sculpture, these all
serve to take the full sweetness and savoriness and bitterness; the
richness of life and condense it down into a sip so that in times of
cold or darkness we can relive those happy moments.
I think that Bradbury hit it out of the park with Dandelion
Wine. It is easily a novel for all ages, yet it hides much deeper
meaning behind what is seemingly a children's novel. I would give it a
try no matter the season. It certainly warmed me up this winter.
One year of the blog and many more to come! I never thought that I
would make it to a year, but after much persistence and many posts, the
one year mark is here. Not quite to a round fifty-two posts but thirty-six
total comes out to about one every ten days. Not bad!
My goal for this year is one a week (or just about). I think that fifty
will do. I definitely have benefited greatly from the writing. The
source for the blog has just over a whopping (in my opinion)
two-thousand lines of writing and over ninety-thousand characters;
almost every character hand typed by me; or I suppose by my script, but I
digress. I am really, really, proud of this though! Reading Thoreau
has given me a bad taste for semicolons . . . it's my blog though
>:). Now instead of $28.12½, it is $16.88 for my digital
cottage, but as Thoreau, I don't pay a dime for my domain and
my cottage is similarly unadorned.
I think that there is a lot of wisdom still to be had in Thoreau.
Although indistinguishable at first glance from a common tramp, he had
purpose: to live life so as to not come to its end and find he had not
lived. Our digital lives are no different from the simple folk that he
complained about. While short form video and inflammatory writing has
taken the place of routine, how can scrolling be considered living? If
our digital lives are an extension of our physical ones, why should we
not live online with the same conviction and purpose as we do offline?
I did not start writing for this reason, but now I read, watch, listen,
write, with purpose. To suck the marrow not only from everyday life,
but from the many distant lives of literature and film. To become acquainted
with the digital logs and bricks that my digital life is
built of; from the HTML to the assembly. I think, therefore I am.
Yet if to write is to think, is not writing life?
My Walden is not the ether but instead the many blogs and writings of
others, a sea of knowledge that I have only begun to explore. On this
shore I have built my cottage and thus stayed to write with purpose. The
modern web has lost purpose; a mess of AI, low-quality content, and
social media. Provided, it is not for everyone, but why shouldn't it
be? The only way to live is intentionally, both online and off, but
online is not a bad place to start. If the best time to start your blog
was yesterday, then today is the second best.
We are defined by our thoughts, but more so by our actions. Writing,
whether it be about Tolstoy or Taylor Swift, is how we put our thoughts
in action, marshal them across the page, and through this action we
find ourselves.
What I learned over the last year? You should write!
This novel was much better than I initially thought and holds a
very interesting place in relation to other works such as Brave New
World. I found that the latter has a much different "edge", so to
speak, that stems mainly from how the author chose to convey their
criticism of authortarian government. Zamyatin is directly influenced
by the newfound Soviet Union and this results in a large emphasis placed
on the actual struggle against the United State. It is not dissimilar
to Orwell's Animal Farm in this regard, however is not as overt
in its criticism and also does not have the benefit of hindsight.
Throughout the novel Zamyatin cuts around his core criticism of the idea
that free will lays opposite hapiness, never outright saying it.
It was really great to read over a week or two because of the episodic
nature. It consists of 40 chapters, each a daily entry in D-503's log.
I think that only reading one a day would be too hard, for me at least,
especially once you get to the end! It is a little slow in places once
you get to middle of the story it picks up and I found it impossible to
put down.
I would recommend it to anyone. It is quite a fine piece of literature.
I saw this novel come up in a couple of other people's recommmended, and
I figured I would give it a shot. I had high hopes. All the reviews I
saw praised his writing, and not wanting to spoil it by reading too much
of the Wikipedia article, I decided to buy it.
The first seventy or so pages were amazing. Murakami is a next-level
talented writer. He is able to conjure images so precisely that you can
almost step through the pages into the world of Watanabe (the
protagonist). Although I am not particularaly fond of love stories, I
knew that however bad it could be, I would stomach if not for the
beautiful writing.
Interestingly enough, Norwegian Wood is not one of his
surrealist works despite the near fantasy scenarios that occur. I am
willing to suspend my disbelief to an extent, but it eventually got to
the point where the novel came entirely unglued from decent reality.
Watanabe is basically stuck in love between his dead best friend's
girlfriend and a classmate. So far I was willing to accept this
premise. He's already not in a good mental so naturally he mopes around
quite a bit. He has a friend, Nagasawa, who is a dissolute hedonist
that takes him to pick up girls. Initially I found the way that
Murakami talked candidly about sex really fitting to develop Nagasawa's
character. However the way that he portray's Watanabe is too
unrealistic to the point of it being problematic.
Watanabe goes to celebrate Naoko's (primary love interest) birthday. She
breaks down and starts crying, so of course the only course of action
Watanabe can take in this scenario is to ... have sex with her.
Really? This is our valiant protagonist coming to the rescue? Raping
his dead best friend's girlfriend? Even worse is that Murakami writes
it out to the point of being smut, giving no attention to the fact that Naoko
was unequivocally raped.
I won't bother with the rest of the plot as I think the smuttiness
overshadows all other aspects of the book. The worst part is with the
handling of Reiko. To make a long story short, she also was raped, but
by a thirteen year old girl. But making this absolutely unforgivable is
Murakami etching out every. single. detail. It was quite literally
smut. How this book entered publication I do not, and doubt I ever will,
know. Naturally coming to the end of the novel, what else would a
mentally broken woman want after the death of her roomate (Naoko. Reiko
and Naoko were roommates at the sanatorium)? Murakami says ... to have
sex with her boyfriend. I was basically just moving my eyes over the
pages at this point but holy moly, I couldn't believe it. Who in their
right mind would imagine this?
The best way to describe Norwegian Wood is Catcher in the
Rye except its smut and a love triangle. It feels almost like a
fanfic with lots of unnecessary sex glued into the plot. Any hope for
serious discussion say around suicide is obliterated by all the female
characters being steam-pressed into one dimensional paper dolls for
Watanabe to take advantage of.
It's a real shame considering Murakami is an extremely talented writer,
but do not read this book. I don't think I could even get rid of it
in good faith knowing that someone else might read it.
Pretty good read. Nothing phenomenal, but I still found it to be
enjoyable. The premise of the novel is that the basic structure of the
universe is a quantum graph with a diamond like structure. They do an
experiment to create a different kind of vacuum, assuming it to be more
unstable than our own, however it turns out that the "novo-vacuum" is
more stable and it quickly begins to eat away at the universe. Fast
forward much to the future and people are trying to either stop the
expansion or completely destroy it. Enter the first conflict: can we
destroy something we do not understand? The answer of course turns out
to be no, however the stakes justify dragging the conflict out. The
vacuum originated from an experiment, provided there was no way of
knowing that it would violate the previously accepted laws of quantum
mechanics, and it is perfectly reasonable to not want to make the same
mistake.
The beginning was well done, however it felt to me like the novel quickly
got bogged down in the physics. I probably don't know enough to
appreciate what was being said, but to me it often read like a jumble
of technical terms for no other reason than to sound like something was
being said. I definitely am not the best point of reference but it made
the more technical elements of the story confusing nonetheless.
The pacing was decently done, and the romantic subplots and tension
actually contributed to the plot and fleshed out the characters. It got
somewhat tiresome though, when the main character was inevitably torn
between an old love and a new one. I think so much more could have been
done, or not done (!), and the romance was squandered.
A part of the novel I felt was very well done was the metaphor of
Schild's ladder (the mathematical technique) for life. Schild's ladder
is a technique for moving a vector along a curve while maintaining
its direction. The catch is that the path you take will alter the direction
of the final vector little by little, and even if you start at the same
point and end at the same destination, your experiences will inevitably
shape you. Therefore the only way to keep hold of your identity is to
improve on it every day.
The actual delivery of the story, from the protagonist's father to him
as a gentle reassurance, could have been tragically fumbled, but Egan
pulls it off. While the tone was patronizing, it was perfectly at home
in the context. Furthermore, Egan does a good job of "supporting", if
you will, his thesis with the subplot of the tension between the
protagonist and his childhood love. They eventually reconcile that even
though they started in the same direction, they are no longer the same.
I think that calling it bittersweet would be an overstatement, but it comes
to a sufficiently amicable resolution that the whole scenario is tied up
nicely.
Although Egan leaves some loose ends, I don't think that anything would,
or could, be had from a sequel. I think that for the length of novel
that Egan covers a lot of ground both with regards to the plot and with
the philosophical themes he ponders. My only complaint is that there
was substantial suspension of disbelief, albeit quite welcome, that any
group of people could be so focused and centered around math and
physics. It's an interesting view of the future but while this context
could be nothing more than a side-note or tangential observation, it
sadly offers an explanation for the lack of variety in the characters.
In an age where you have complete control over your body's physical
responses to your emotions it is not entirely surprising that people
would opt for a more placid and monotone demeanor. This would also
explain the very rational and stoic natures of the characters, the cast
made up entirely of scientists, but it makes for a boring novel.
Interestingly, in my opinion really only the romantic subplots were hurt
by this. Most other aspects still carried their weight, but I just
could not be affected by the low stakes of the relationships.
The physics/math that are covered in the book were pretty interesting.
I would recommend it if you can get it for cheap. I found it dense in
parts, but if you can get through them it is not a terribly difficult
read.
I finished this book about two weeks
ago so some details may have escaped me.
Part I
It got off to a slow start, but it was
for the better. The outline of each of
the characters really helps to introduce
them instead of leaving their
characterization for later and
abandoning the reader in medias
res. Something I personally found
confusing initially, but is really just
a cultural issue, is the wide variety of
nicknames that the characters are
referred to by. The translation that I
was reading had a character list that I
found quite useful, however once you get
into the story it is a non-issue. The
ending of the first chapter is quite
sweet in an almost childish way. He
receives the letter from Lise and while
their age difference is fairly severe
(even Ivan remarks on this!), what makes
it so sweet is Alyosha's renewed faith
and encouragement as a result of seeing
Zosima's prophecy start to come true.
Part II
This is where Dostoevsky starts to
really get into the more philiosophical
style that continues throughtout. While
there was some of this in Crime and
Punishment, a large portion of the
novel is taken up by these discussions,
or more often monologues.
Just a small note, I found the story of
the Grand Inquisitor quite tedious,
yet it serves to juxtapose the
following tales of Zosima so it is not
entirely for naught.
A major theme explored throughout the
novel is the existence/role of God in
our lives. On the one hand, Alyosha is
entirely faithful, but time and time
again he is challenged for this by his
father, his brothers, even Kolya.
I found that Dostoevsky pretty clearly
favors the existence of God by
associating unbelief either with extreme
hedonism and sensualism in his brother
Ivan or in adolescent egoism in Kolya.
There is a lot of foreshadowing in these
books whether it be in Smerdyakov's
words or in Zosima's dying speech.
Something I picked up on is the reversal
of Zosima's retelling of his friend's
murder story. In it he discovers that
an acquaintance that he has developed a
friendship with murdered a former lover
and framed one of her servants, notably
a drunk, who was then blamed.
Part II is where the action picks up,
yet at the same time feels the slowest
of the novel.
Part III
This part is very plot heavy, for good
reason too as Dostoevsky delays much of
it until now. Many themes are
reminiscent of Crime and
Punishment especially with regards
to Grushenka's character mirroring Sofia
in a lot of ways. I suppose it isn't too
far fetched to say that Dmitri mirrors
Rodya fairly closely. He shares the same
reaction that Rodya had to killing Alyona
Ivanovna when he injured their servant
Grigori in that he spent time in shock
confirming that their victim is dead. The
language Dostoevsky uses is also very
similar with regards to the emphasis on
the pooling blood and the disorientation
that the murderer experiences.
The meeting and subsequent party at the
hotel is where the redemption of Dmitri
and Grushenka really begins. However just
as Dmitri triumphs and gains her love, his
life ends and this inner despair takes hold
of him until the end of the night. It is
much easier for a man to die when he has
nothing to lose and this is because
of the disconnect
between his conscious desire to win
Grushenka over and his subconscious desire
for her to reject him When he traveled
to the hotel he wasn't looking for her
love, he was really hoping that she would
reject him and he would be able to let go
of his life. But after acquiring his
object of desire he again does not know
what to do with it. He is wholly
incapable of staying in a
state of happiness or unhappiness, he
longs not necessarily for his ruin, but
more for the rise and fall of his life to
the utmost extreme.
Grushenka is somewhat similar, however
after meeting with Alyosha she begins on a
path of redemption, and by her separation
from Dmitri because of his imprisionment
she is able to better regulate herself and
by this life herself from her former
hedonism.
Part IV
I really, really liked the subplot with
Kolya. It was a nice break from the
heavy and seemingly hopeless plot that is
coming to a head to a more wholesome and
yet more philosophical narrative. While
Kolya is obviously an amalgamation of each
of the brother's traits, his redemption
foreshadows the brothers restoration in
the aftermath of the death of their
father. He is militaristic and cruel like
Dmitri, sharing the same fits of energy,
yet shares the same philisophical and
melancholic disposition of Ivan. These
are the traits that are the most
pronouced and which set him apart the most
from Alyosha. Ivan himself serves as the
primary mirror of his father and continues
the strugle between the brothers and their
sensualist tendencies after his father's
death. While Ivan is removed from the
spotlight for much of parts III and IV, he
still undergoes a profound transformation
with regards to his relationship to his
former materialism. It is my opinion that
Koyla serves as a placeholder for the
transformation that Ivan undergoes in his
travels and shows how Alyosha's kindness
has acted on Ivan, even though he does not
show it.
Overall this book was an unforgetable
read. I just could not put it down, save
for the story of the Grand Inquisitor.
I'll admit that it was tough not to take a
tea break in between. It has a happy(ish)
ending, which honestly suprised me but the
triumph of the brothers over their
unfortunate upbringings was very
rewarding. Dostoevsky's style is very
well adapted to a longer form than say
Crime and Punishment and I think
that is what makes The Brothers Karamazov
his magnum opus. I would
recommend it any day of the week, but some
may not like the longer and more
philosophical style.
This book took way too long for me to finish reading. I can't
say that it was mind-blowing, but it was still an enjoyable read.
It was an interesting take on the stream of consciousness style in that
although it was meandering, it did not have the same linearity that
is more normally associated with the style. Martel has a tendency to
switch between the more immersive past Pi and the more contemplative
current Pi in a way that hurts the narrative. Often past Pi will
interject to say that a detail will be more important in the future, but
this really flattens the story out. While I understand making the
themes unambiguous via a simpler plot, it is a huge detriment to the
novel as a whole when the plot is broken down too much. This makes the
plot develop just a bit too smoothly so that there aren't as many
smaller moments of realization, mainly the ending. While the
current day sections really did add to the story, having Pi say "this
will be useful later" feels like too much.
The ending and quick frame narrative of the Japanese investigators
simply feels tacked on. I didn't think too much of it, as the story had
to end somehow, but what really peeved me was the investigators
commentary on the plot. I just couldn't believe it. The last bit of
nuance gone. Utterly demolished. I don't know how I would have written
it, but I certainly would not have explained the allegory outright.
Personally I thought it took too long to get to the meat of the plot.
While it really isn't the point of the novel, there was just too much
soliloquizing for my taste. Pi's monologues feel too repetitive and
Martel's argument with regards to religion doesn't develop with the
plot. I think this comes down to the truly miniscule character
development that Pi undergoes. Pi's character stays constant
throughout, his carefree attitude maintains him through ups and downs.
Even in the depths of despair he still has an uncanny knack for hope.
I don't hold it against Martel as he is portraying Pi as the emblem of
hope in a higher reality, yet it makes Life of Pi feel more
like a self-help book on hope than a full fledged novel.
Its definitely on the lighter side as far as novels go, but the actual
quality of the writing is high, even if the plot is more straightforward
than Martel puts on. Good beach/travel read.
I wanted to read my emails using mail because it's nice and
native for my system. I found it really, really confusing so here's my
stack just to make it easier on others. I don't know enought to
describe it all, but I've managed to kludge it together. The Freebsd Handbook
page on email was definitely the most helpful for sending mail.
For receiving mail I worked off of this guide.
So for delivering mail I used the default MTA (dma). The only
configuration needs to happen in /etc/dma/dma.conf for the
server address, port etc, and /etc/dma/auth.conf for user info.
I wont go into detail as the man page is quite well done. The main
issue I had was with the SSL. I don't know exactly what was going wrong
but it had something to do with STARTTLS.
So an issue with this is that when you send mail it is forwarded first
through the MTA then through your server so you effectively leak your
host username and host IP. To strip the headers I used this handy
script.
/^((Resent-)?From|To|Cc|Date|Return-Path|Message-ID):/ OK /./ IGNORE
This removes all headers except for the ones listed. Include it in your /etc/postfix/main.cf with the line
header_checks = regexp:/etc/postfix/maps/header_checks
Now receiving mail was a bit trickier. For this I used fetchmail. I'm planning on adding something so that it runs in the background and will check for mail every fifteen minutes or so. If you are planning on using just Mail(1) then you need to use a mail processor. procmail(1) provides formail(1) which does the trick. In your .fetchmailrc add
poll YOUR.DOMAIN proto IMAP # can also be POP3 user USER pass PASS keep ssl fetchall mda "formail -c >> /YOUR/MAILBOX"
I guess it wasn't so bad after all but this caused me a lot of angst. Hope it helps!
Such a great film! I really liked the non-linear storytelling: how the
scenes were not necessarily in chronological order. I think that this
aspect was pulled off quite well. Flashbacks often feel awkward even in
conventional films and thus it would be expected that because of this
the plot would suffer. Yet the writers pulled it off very well.
The main "narrative" element of the film comes not from the events
themselves, but the characters' (really only Tom and Summer) development
is clearly shown in order. Obviously neither Tom nor Summer were
unchanged after their relationship. A digression, however they
certainly do not have a conventional relationship. Summer, and Tom
assents, doesn't really requite Tom's want/need for a clear deliniation
between friendship and a more serious relationship. In Tom's own words
too!
This is no way to treat your friend! Kissing in the copy room? Holding hands in IKEA? Shower sex? Come on! Friends my balls!
Summer's apparent emotional carelessness competing against Tom's
overbearing, but truthfully just over-expectant and naive, view of love
is very ironic in the end, as Summer ends up falling in love, just as
Tom said he believed in at their first real meeting after karaoke.
A very interesting tidbit that ties the climax to the eventual downfall
of their relationship is the disregard for conventional labels of the
relationship. They both say, Tom at the end (seen at the beginning of
the film) and Summer towards the middle, that they don't care what
other people may say, they just care that they are happy.
I don't know. Who cares? I'm happy aren't you happy?
Yet both times they are lying and the other can see through it. Tom
nervously clings to Summer with religious conviction and Summer waves
Tom's doubts away in the car.
I would argue that Tom is not the main character, but Summer is. Tom
simply does not change throughout the film. Even after he is rejected
by Summer, his supposed soulmate, he still manages to fall for Autumn at
the end! He learned quite literally nothing! Summer on the other hand
saw that she had a chance at love afterwards when she met her husband
and thought that Tom was right. Throughout Summer changes,
much to Tom's chagrin, and her love waxes and wanes along with her own
personal development. Tom stays the same gullible sucker he always was.
It's nice that the film ends on a good note though, (an American film,
what did you expect?) I think that although it would still be good, it
would be too open to leave Tom single. Now the audience knows that
Tom is just back at it!
One positive effect is that he gets out of the rut of working for the
card company, however I think that this could be attributed to any major
emotional shock not necessarily Summer herself.
Overall I really liked it. As much as I gripe, Tom is still fairly
likable and Summer is as well. Summer is a bit cruel, however she is
upfront so the fault ultimately falls on Tom for not acknowledging it.
This was sort of a break from my usual domain but I think the film was
quite nice.
I'm a firm believer in New Year's resolutions. Though they are mocked by many, I feel that they offer a nice starting point to effect a genuine change on one's life. It's sad that more people don't take them seriously or, even still, seriously overestimate themselves and their will power, and becuase of this the effect is lost. Anyways moping aside, here are mine.
I fear that the second one may ruin this
blog T_T. Joking aside, I
suppose I should elaborate, more for
myself, but also so that the terms are
clear. I realize now that this has
become an impomptu contract between
myself and the ether to which you (the
reader) are to keep me accountable. Anyways,
enough philosphizing, here is each point
broken down.
The first one is simple. I will not be
mean. This means, for example: no rude
comments, no demeaning jokes, no haughty
silence, etc., etc.
The second one is a little more nuanced,
however I think the explanation is
simple enough. Complaining is just
criticism without any positive
resolution. I think there is also a
component of timeliness to it as well.
Complaining takes place well after the
fact and offers no hope of a positive
outcome due to the window of opportunity
passing. Being upset about stubbing your
toe 5 seconds is a lot different than
being upset over a stubbed toe 5 hours
later.
No cursing is the simplest of all. No
words that couldn't pass in a 2nd grade
class.
The last one is the first, I suppose, to
be focused on a good habit instead of
righting a bad. It is also a tad
vague. When I write write, I mean it in
the more broad sense of creating out of
original thought. In this vane I would
consider writing code allowable, however
not LeetCode or as a solution for say a
problem set. No GeeksForGeeks either!
I think visual art and music would also
qualify, if I were so inclined, as I
sometimes am.
And of course I will need some gentle
persuasion, so for that I have come up
with a punishment system. Being nice
will carry a penalty of ten pushups for
each time I break it. On second
thought, if I apologize in a timely
manner I think that the tax should be
reduced to five. Complaining will be
five and cursing will be a flat five.
Finally, I hate to put myself under the
gun for the last one, yet I think that
writing (again in the figurative sense)
is developed as many things through
practice so for each missed day twenty
pushups and ten pullups will do. For
the rest as well after forty pushups
they will overflow into pullups at a
conversion rate of one pullup to every
two pushups (five to ten).
By the time this is published it will be
New Year's Eve (albeit quite early) so
just in time. I hope you got something
out of this although it's really for my
sake so I can keep myself true to these
goals.
Happy New Year's!
Out of spite for rofi, I decided to ditch it's window switcher and add a
script to use my own dmenu knockoff. xprop and xdotool come in handy
here, and plenty of sed too!
It was a real pain to clean up the xprop data but hitting it with sed
enough did the trick. The real issue was getting the windows in the
right order. xprop returns two relevant variables from the root
variable: _NET_CLIENT_LIST and
_NET_CLIENT_LIST_STACKING. Initially I didn't notice the
difference between them and _NET_CLIENT_LIST did the trick.
However, to get rofi like functionality, where the most recent window is
at the "top" or "leftmost" position, I needed to use
_NET_CLIENT_LIST_STACKING. But...it is in reverse order
(newest at the end). If I were using any actual programming
language this would be trivial, however as it was a shell script, I was
left without a clue. I don't know? I feel that this is somewhat akin
to reversing a red black tree. Regardless, I had to consult
StackOverflow. I was hoping to avoid using a loop or temporary files,
but luckily I came across rev. I never would've guessed that a
utility to reverse text would be standard, but every so often I come
across something like that will just crack me up. Sadly a loop was
inevitable, however I think that approach is faily novel. The input is
first reversed, then for each space delimited word it is added to a new
variable and is reversed individually. Not quite as satisfiying as
using a ternary or walrus assignment, but still neat! Heres the script
for all of the txm users out there :)
#!/bin/sh RAW=$(xprop -root | \ grep '_NET_CLIENT_LIST_STACKING(WINDOW): window id #' | \ sed 's/_NET_CLIENT_LIST_STACKING(WINDOW): window id # //g' | \ tr ',' ' ' | \ rev) NEXT="" for w in $RAW; do NEXT="$NEXT $(echo $w | rev)" done RAW=$NEXT OUT="" for WIN in $RAW; do OUT="$OUT $(( $(xprop -id $WIN | \ grep '_NET_WM_DESKTOP(CARDINAL) =' | \ sed 's/_NET_WM_DESKTOP(CARDINAL) = //g') + 1)).$(xprop -id $WIN | \ grep 'WM_CLASS(STRING) =' | \ sed 's/WM_CLASS(STRING) = //g' | \ sed 's/"//g' | cut -d ',' -f 1)" done SEL=$(txm $OUT) xdotool set_desktop $(( $(echo $SEL | cut -d '.' -f 1) - 1 ))
I think situations like this really make me appreciate the Unix
philosophy more and more. Do one thing and do it well! I find it
really satisfiying to be able to shape my desktop one program at a time.
Still chugging through Karamazov. Some new books in the mail
as well: Norwegian Wood by Haruki Murakami and Schild's
Ladder by Greg Egan. I'm more excited for Schild's Ladder as
Murakami is out of my normal literary world (Sci-Fi lol) but I'm really
looking forward to it.
I've official thrown the towel in with Graph Theory. It would
just be vain to even say that I understand what is going on. After some
more reading I think I may be up to it, but it was just too far of a
jump. I picked up a real analysis textbook and a linear
algebra/differential equations one off of thriftbooks and I think they
will be more manageable.
I decided to just use git :'(. Gone are the happy days of just using
scp to move data up to the server. It just got to the point that I had
too many devices to keep track of unfinished posts.
However, this provides the perfect opportunity for a little CI/CD pipeline!
My thinking is this: currently there is a cron job that will build the
site at midnight whether there is new data or not. However, now that
the files are all tracked in git, when there are changes the commit hash
will change. Therefore, the cron job can run more frequently and updates
propogate faster.
The plan is to compare the current commit hash (in refs/heads/master)
against the hash saved from the last run. If they differ, pull the
changes and rebuild. Here's the script.
#!/bin/sh if ! `diff /home/git/blog.git/refs/heads/master /root/bloghead.old`; then cd /root/blog git pull ./build.sh cp .git/refs/heads/master /root/bloghead.old fi
I think it's a fairly elegant solution for a simple problem. Maybe it is a bit overblown to call it CI/CD ;)
I find that there is a certain zen that
is found in writing on paper. Provided,
I prefer the ease of editing of digital
media however word processors like MS
Word (they're all the same, really) for
some reason make it hard for me to
write. Maybe it is a psychological block
from writing so much for school in that
way or maybe it is something more
trivial, however the block remains.
There is something about plain white
text on a black background that just
erases all friction. Word et al. integrate
the process of editing too closely with
the actual writing. How are you
supposed to draft if the computer is
flagging spelling errors, grammar
errors, even stylistic errors? I find
it especially stunts more creative
writing (such as this) with the
overbearing spell checking.
On the topic of the stylistic
supervision, AI absolutely butchers any
premonition of "style". No matter the
agent/model/whatever you use, it
will choose the path of least
resistance. And of course it does this
by design. The input will trickle down
the many dimensional rivers and troughs
of the weights until it comes out the
other side, a stream of "average".
Asking the AI to "polish" or "fix" is
the same as putting your writing
through a wood chipper to be made into
particle board. Truthfully, I don't
care, to each his own, however I fear
that the over-adoption of AI in writing
tools will push writers to never
fully develop their own style,
constrained to a careful
approximation of "proper" English
writing.
Anyways, I digress (a bit too much I
suppose). How do I write? The exact
layout depends on whether I am on my
desktop or laptop (or Eee PC, more on
that later) in terms of how I layout my
tools. For the actual writing I use vi,
nvi specifically. I shall not lie, I
only started using nvi specifically
because of it is the default for
FreeBSD. However, I have come to love
its simplicity, more specifically its
lack of syntax highlighting or colors
altogether. I've grown to love it and
now use it across my systems, FreeBSD or
not. For spellchecking I use aspell.
Something I found myself doing often was
using the browser like a spell checker
and looking to see what my search engine
had to say. Honestly this was slow and
thankfully aspell has an interactive
mode. I added
alias spell="aspell -a"
to my shell's rc file and called it
done. Now I keep a window (or tmux pane)
open with it for whatever word I need to
spell. Also, aspell can check entire
files so that makes it easy once I am
all done to fix any typos. Another
tool that I've recently picked up on is dict. I
think I will eventually write a wrapper
script so that it can run interactively,
however for now it is fine to just pipe
the output to less.
A little on the Eee PC. I own a little
Eee PC 701 (Wikipedia article for reference)
and no other piece of tech brings me the
same joy that writing on it does. The
keyboard is cramped, I'll admit, and my
large hands do not help my cause either;
yet I love typing on it. The touchpad is
useless, and Xorg drains the battery, so
the best alternative, and honestly the
better choice, is to use tmux. I have
one window with whatever I am writing,
then another with two panes split
between apsell and either w3m, to find
links, reference info, etc. or dict.
I am not one to swoon over material
design, but there is something to be
said for the small size of the machine.
It sits quite comfortably on my lap and
its screen is just big enough to fit
seventy-two columns of text. Using the
touchpad is near impossible, greatly
decreasing the opportunity to get
distracted, and the prohibitively small
disk and memory size (however mine is
upgraded to 2GB of RAM) completely
prevent running a modern browser.
Leaving only one thing left to
do...write! The wireless card is really
great. Just enough to get a scp link
up to the server to upload posts.
Friction in all the right parts =)
I'm reading The Brother Karamazov
right now and will write about it when
I'm finished. Part I down, three more to
go!
Absolutely recommend this movie. You can see the maturity in
Tarkovksky's direction and a refinement in the more dynamic scenes. Of
course the film is partially shot in black and white but it is more
tasteful than in Solaris. The cool blue lighting was merely a fixture of
the source. It tied into the emotion, however somewhat tangentially. It
is predictable, however I think necessary to juxatpose the Zone and the
regular world. The long, panning shots are more meaningful as well. The
montage (collage, maybe?) of submerged objects and alternation between
the sepia and color filter works quite well together, but the
transistion is very clear and there is a clear boundary between dream
and reality.
The nature shots are phenomenal as well and Tarkovsky's vision shines
through exceptionally well. The exact nature of the Zone is never
explored in depth, however I don't think that necessarily impacts the
overall message/plot. The Zone very obviously is used as a foil that the
rest of the cast interacts with. Unlike Solaris, where the essences of the
visitors, the ocean, and the space station itself are intertwined with the
novel's science fiction nature, Stalker only uses science
fiction elements to convey a deepr, more philosophical message.
A bit of an aside, but I was absolutely
delighted with the railcar scene. I don't know how exactly it was shot,
but instead of the unsigntly overlay method, it looks as if it was
actually shot in motion, and it looks good. Albeit not Marvel, but it
doesn't distract from the main change from the black and white to color
film.
Overall a great movie but much more philosophical than science fiction.
Its an interesting mix and could be either more or less approachable
depending on your background. I would recommend it for anybody though.
Really great movie, but quite long (2:47) and very brooding. I read the
book around two years ago and enjoyed it a lot and I had a free evening
so why not? Consistently ranked in the top ten science fiction films and
top five Russian films I thought it would be a good introduction to
Russian film. I didn't know what to expect going into it but with an open
mind and an open schedule I pulled up the Internet Archive (English
subbed. Low quality but watchable. The sub font is kinda annoying
but I couldn't find the version I watched. Sorry.) and started watching.
The first thing I noticed was the beginning of the film differed from
the novel. I have to say though it is a good introduction and eases you
into the film and Tarkovsky's style. The shots of the pond and the
garden are especially beautiful.
The only major change that I would make is the traveling and SFX. I'll
just be honest. It was 1972. The special effects are bad. The scene with
Burton in the car to symbolize the long journey to Solaris is grating.
Tolerable, but with better CGI I think that a remake with shots from a
spaceship or of space would greatly enhance the film and help the
pacing.
The film was exceptionally close to the novel apart from the beginning
due to the close work between Tarkovsky and Lem. From the Wikipedia
article Lem wanted the film to be a direct adaptation of his work but of
course Tarkovsky wanted more freedom. I liked how faithful the film was
and how well Tarkovsky did within the narrative constraints. The film
focuses more upon Kris's personal struggle with the loss of Hari and the
more technical (sci-fi) elements are lost, but I think it's honestly for
the better. The film makes a great science fiction novel into a great
romance (drama, perhaps?) film. I think that this combines the best of
both world and the only barrier to entry is a tolerance for esoteric
film.
I was most moved by Hari's simulcra's (apparition) own personal conflict and her struggles
inherited from Kris's memories, but also her constant questioning of her
own reality. It is, in my opinion, more interesting to see her eventual
return to suicide in the form of Sartorius' neutrino beam, paralleling
her initial suicide by lethal injection, than to see Kris regress
mentally and unprocess his grief.
Overall I would recommend, unless you have no attention span ;)
I was bored and I had heard that Scott Pilgrim vs. the World was a good
movie. It was with a few gripes here or there but I think that it did an
extremely faithful rendition of the original comic series. I liked it so
much in fact that I read the comic series (freely available in PDF form
on the Internet Archive) in its entireity over the last
two days. After reading that, I can report that the comic is much better
than the movie (shock).
While the script was obviously adapted to fit the plot in a feature
length film, the locus of Scott's character development (his
relationship with Ramona) severely suffered in the process. The first
instance that I noticed a difference was the first direct interaction
between Scott and Ramona at the party. In the comic although Scott is
awkward, there is still a somewhat positive response from Ramona. In the
movie however she is completely unaffected and her actions in their next
conversation when she delivers his package come completely out of left
field. It makes no logical sense why Ramona would agree to Scott's
offers to hang out if she were not at least a bit interested but the
movie glosses over this subtlety and I think that the beginning of the
movie suffers. The later conflict between Knives and Ramona also seems
unfounded as I think that the movie does not well reflect how much time
passed between Scott being romantically involved with them
simultaneously.
The biggest gripe I have however is with the casting. Michael Cera is
insufferabe. Scott in the comics is undoubtably awkward but not to the
extent that Cera portrays him as. The pacman factoid was almost too
much. I just about turned the movie off out of sheer embaressment. The
lack of backstory certainly doesn't help flesh out his issues with
maintaining relationships, but Cera just can't convey the depth of
emotions and conflict that Scott has in the comics. He lacks some inate
sex appeal that Scott posses in the comics. In the comics, while still a
loser, Scott is in a band, he has a certain naive charm. Cera manages to
butcher all of this and twists his character into a sophmoric bastard
that has near no redeeming qualities.
The ending is butchered as well. In the comics, although Scott comes
back from the dead, it doesn't serve as the main way that he is redeemed
from his past errors. When the movie allows Scott to roll back time it
condenses the gradual change that Scott has made for the better into one
singular event with the main cause of this being Gideon's own actions.
This isolates Scott's change as one made for himself, not for Ramona
like in the comics.
I would reccommend the comics first, and only then the movie as a
substitute.
Recently I've been trying to get organized and be more productive
(starting of course with this but please ignore the irony) and I do love
my calendar. Calcurse just wasn't cutting for integration and it didn't
give as nice of a display as I wanted for something that I think of as
very visual. Its hard for me to juggle tasks/appointments with just
numbers and having a block chart with them is really helpful.
It was on a wild hair that I decided to move my laptop to Elementary OS
and boy was I shocked. All the things that normally ruin my day such as
connecting a bluetooth keyboard or (heaven forbid) printing something
just went away. They just work. No other distro that I have ever touched
has come close to the ease of use and seamlessness that comes from using
Elementary OS.
I've already talked about the calendar and mail, but it's really the
little things that make it so easy to use. Take for example media keys.
They just work. Just like in Windows or Mac all you do is press the
buttons and things work. No fiddling with ibus or MPRIS. Another thing
is power management. Even easier than Windows. Just a drop down in the
task bar. Select one of three power modes. Just works. The night light,
often a bug riddled mess with the scheduling, worked without any
configuration. I turned it on. It worked.
Really though, all these good things are a symptom of a rare disease that
seems to afflict the eOS dev team. Actually caring about UX. Do I think
that UX/UI is overated in general? Absolutely. But in the Linux desktop
space you either have GNOME developers that are on a completely
different planet than users or are told to just "roll-your-own" by Arch
i3 suckless power users. After rolling my own for about a year now, I
can safely say that I've lived that life and am over it. While I'll
never go back to Linux on the desktop, the laptop is a different story.
I hate to admit it but truth be told I'm mainly just reading emails or
doing some lightweight writing on the laptop. No need for tiling and dev
tools. The laptop is just too dynamic of a platform to try to cover all
of the bases with a custom config. Everytime that I would go out and
connect to a new network or use a new printer I would waste anywhere
from 5-10 minutes trying to get the damn thing to connect much less
work.
I really hope that the eOS team stays on it. Out of all the desktop
focused distros that have come and gone eOS has had serious sticking
power. The one downside is that the reliance on Flatpaks makes it a
little slower than my tastes, then again I'm coming from a pretty
spartan setup so I think it comes down to how well your setup works now.
Total fever dream but if eOS was based on FreeBSD then Flatpaks wouldn't
be necessary ;). Also we'd be riding flying pigs to work. Not the worst
scenario if you ask me.
I got my first RISC-V board! It is a Milk-V Duo 256M. It's a unique
board because of the SoC. It has two RISC-V cores, an ARM core, and a
8051 microcontroller. It by default runs Linux on the bigger RISC-V
core and a RTOS on the smaller of the two, FreeRTOS at the moment but
from the documentation it sounds like they are planning on adding
suppport for more options.
Setting it up with their flavor of Linux was relatively painless. The
only qualm is that it is based on musl which makes compiling annoying.
Otherwise I would say it is a pretty solid starting point. It is an
embedded distro so of course it will be lacking, but the memory usage
was quite low and it would %100 be able to run a lightweight web server
or other type of device.
The specs and price point are a nice departure from the trend with
SBCs like the Raspberry Pi that are now just low-end desktop computers.
Raspberry PIs aren't all that great for desktop use and most would be
better off buying a used optiplex or other office computer and just
putting Linux on that instead. I bought mine for $15 which is higher
than the MSRP of $12, but with tarrifs and shipping it was much cheaper
to buy used domestically. I would highly recommend using the UART debug
interface. I already had a convertor on hand but it is much, much,
easier to just plug the wires in and not worry about network
configuration. Plus, on FreeBSD cu(1) makes it super easy to
connect. On Linux I don't know how you would get the console open. I
think you need to download a program such as minicom or putty.
I'm hoping to get FreeBSD working on it but that is a long term project.
So far I've only had time to download the provided Linux distro. I want
to get U-Boot then OpenSBI working and then worry about drivers, etc.
So far I would recommend the board as a lowcost way to get exposure to
RISC-V. It's also great because if you ever get tired of RISC-V you can
always use the ARM core or even play around with the 8051.
It was a slog through the first chapter however it's slowly picking up. It took
me about two weeks of on and off effort to finish however that was with
spending an hour or two (or three) doing exercises for each section of
material. I fell into a rhythym of reading a section at night then
doing exercises the next. Graph theory is definitely not for the faint of heart but in
my opinion it is much more intuitive because of the strong connection
with the visual representations of graphs. This along with the
connection to number theory makes the content conceptually within reach
with knowledge of set theory. It is beneficial to have experience with
number theory but I have not found any number theory conecpts farther
away than a StackOverflow search. Inifinite graphs really hurt my brain
though. This is probably where number theory comes into play but the
book focuses on finite graphs so it is not a real issue. There's some linear algebra as well (eigenvalues, etc) because of
the representation of edges as elements in a matrix, however this hasn't
gotten in the way of anything so far and I'm not expecting it too.
It is a widely used text so
explanations are readily available as well. The applications are very
easily translated to computer science especially in the context of
distributed systems which I've been studying recently. Overall a good
read and really approachable. All I need to do now is keep up the
effort!
Re: Palm... I'm already not using it! I'm tempted to remove the
inital post however just for posterity's sake I'll leave it up. I was
so hopeful as well, but it turned into too much work to enter events.
Too much friction. Now I appreciate why most people just ask Siri to
remind them.
Note: I just reread my post from two weeks ago and I said very
similar things. Oops.
I really liked it.
I learned Go about a year ago just for the fun of it. Figured I should
probably drag my skills out of the stone age and into the brave new
world of the 21st century. I had some experience with PHP but never did
a whole lot beyond some basic database work. I had a hackathon last
week and we needed a backend. I did some basic and I mean very basic
web server things with Go but I heard some good things about Gin
(DuckDuckGo search) and it has support for JSON.
I'm onboard with JSON but I'm so used to programming in C that I never
realized that it really isn't that hard. Gin is 100% a game changer.
Receiving and returning JSON takes close to no effort beyond defining
the JSON structs. I had some difficulty in figuring out nested JSON and
arrays but it wasn't anything a StackOverflow search couldn't fix.
The official example for a RESTful API was really helpful.
The one thing that had me stumped for a bit was connecting it with the
frontend. I guess that javascript fetch uses CORS so to actually get
data from the backend I needed to use CORS. It is really not hard to
add on but I don't think I did it the right way. All you need to do is
import github.com/gin-contrib/cors and call the router to use CORS.
There are settings to only allow certain origins but allowing all worked
fine.
I've gotten into the habit of not using my time as efficiently as I should. I'm writing this too late instead of sleeping. This could've been done so much earlier. Anyways, I have a Palm Zire thats gone unused. I never did much with it except play with it once or twice but it may well be what I need. The flip phone isn't very condusive to note taking and calendar stuff so I think the Palm will help me keep a focused to-do list so I'm not at loose ends. I'm writing this down so that I stay commited to using it. All the sync software is depreciated, but there are still drivers for FreeBSD at least. I might write some software to sync with the Palm. I'll update in a week with how its going!
Its been a while! I've kinda gone down a wormhole of cryptography recently,
and its really frustrating but also really rewarding. I've always relied
on libraries for encryption in previous projects, and I don't think that
this will necessarily change, however I think that cryptography
libraries make it much more complicated than it need be (at least from a
C/C++ perspective). One of the downsides of relying on libraries is that
you don't have good options outside RSA, ECC, and AES. There are so many
more ciphers out there that could be perfect for your application but
aren't in libraries. For projects that need high security I totally get
using a library, but otherwise it seems kinda overkill.
On a slightly related note, I've also started reading Graph Theory by
Bondy and Murty, and talk about a dense book! So far I've liked it a
lot and I've found it fairly intuitive. Its really nice that graph
theory relies heavily on the embeddings (pictures) of graphs so there
are plenty of visual example for all sorts of problems. The applications
are super, super, relevant as well. You can apply the general ideas to
all sorts of things like social networks, dependency graphs, even
detective stories! I'm only up to section 1.3 out of chapter one after a
week so its looking like I'll be working on this for a while.
I've been thinking of somehow making a PoW algorithm out of generating
isomorphisms but I don't know how it would be done. Graph theory is ripe
ground for cryptography.
With a little more time on my hands I decided what better project than writing my own shell? Initially I thought it was going to be a battle just to get programs to execute, but actually it's not. You basically fork, exec, then in the parent wait for the process to complete. OK so I had a MVP. What's next. What about suspending processes? This would prove to be much, much harder than I anticipated. All you do is pass the signal on to the process right? Wrong. Each process needs their own process group (pgrp) so that signals are not mixed. So now each process is in their own group. Now stdin is messed up. So you have to give the process control of the terminal with tcsetpgrp (man 3 tcsetpgrp). But now you have to take input back when the process completes. I've glossed over the details of my actually journey because (1) I forgot the many convoluted things I tried with signal handlers and (2) it took a while. Basically exec calls will reset the SIGINT and SIGTSTP handlers (and maybe others, those are the relevant ones though) so signal handlers won't work. It only took me a couple hours to figure this one out... Thats it for now. Source can be found on GitLab, and status update in the future after I implement some more things. On the way to POSIX maybe? Anyways the most immediate thing on the agenda is environment variables!
I think that ARM (or some other RISC) is going to be the way forward
for the near/mid future. x86 is too bloated and attempts at power
effiency are like trying to fit a square peg in a round hole. A reduced
instruction set computer (RISC) isn't going to use as much power as a complex
ISC like x86. Hardware optimization can go a long way and I think that
is a large part of the sucess of ARM. RISC-V is just not as mature as
ARM and I think that comparing them at this stage is not productive in
the actual argument between the two instruction sets. If you're interested,
here is a study on the power efficiency of x86
vs. ARM vs. RSIC-V. The ARM chip is very comparable to the x86 chip
that they chose and they go neck and neck in most of the tests. I think
that a fault of this study is that the RISC-V SOC that they chose was
severely underpowered, however as noted in the conclusion,
RISC-V architecture implementations are still in a relatively
nascent stage compared to their more established counterparts. As RISC-V
continues to evolve and undergo optimization, further enhancements can
be anticipated in both performance and energy efficiency in the
future.
I think that this sums it up pretty nicely. Anyways, on the consumer
front the RISC-V space is pretty sparse. The market leader seems to be
Milk-V however their boards are not (as of July 2025) supported by the
Linux kernel and I think that this hurts the performance in tests like
Geek Bench. They have plans for mainline support in the Linux kernel by
Q4 2026 so I am still hopeful that RISC-V can become more popular. Also
from Milk-V their Titan board looks promising with an alleged 64 cores
but there has not been much discussion online about it as far as I can
tell.
Personally I think that I am going to buy an OrionO6 from Radxa in the
next year or so because (1) I need a new PC, (2) it's fairly
inexpensive, (3) I can hop on the ARM bandwagon, and (4) it won't suck
up as much power. Right now I have a AMD FX-6100 that used to heat up my
bedroom before I started using powerd.
Quick digression: how to set up powerd.
In your /etc/rc.conf set:
powerd_enable="YES"
The next step depends on your personal preference and whether you are using a laptop or desktop computer. For my desktop I use adaptive and I used minimum for my laptop when it was on battery power.
# for laptop powerd_flags="-a adaptive -b minimum" # for desktop powerd_flags="-a hiadaptive"
hiadaptive favors higher frequencies and will stay at a higher frequency
for longer. I don't personally find it more useful than regular
adaptive, however it really depends on the use case.
This reduced my coretemps from around 35C to room temperature. Its truly
amazing what its done. It even showed up on my power bill! My power
compay shows graphs with usage levels and I saw a difference between
before and after using powerd.
Anyways, back to ARM. The O6 is really promising. The GeekBench scores
place it at 4x faster than my current desktop and about 25% slower than
Apple M1 performance for only $330 for the 16GB version! I can only
expect performance to get better as drivers mature so I anticipate that
it will eventually reach scores at or just under the M1 for a third of
the price. It is marketed as a "AI" PC but I think it would be a great
fit for a capable home workstation.
I think that energy usage should be a bigger concern going forward. We
are getting more and more powerful devices however the software is
making it so that we see energy usage at or worse than previous
hardware. Especially today with energy becoming more of a concern with
regards to climate change, geopolitical conflict, etc. I think that
developers, both hardware and software, and consumers need to be more
mindful about how much energy they are using. A react app is going to
use easily 1000x more power than what could have been a CLI. It doesn't
really matter because of the current AI hype-train and just general
wastefulness in society. Sadly the U.S and the rest of the Western world
has fallen behind in terms of technical innovation so all the real
progress happening is in China. I doubt that any amount of funding could
restart silicon manufacturing and even if/when it happens rumor has it
(i.e. I don't want to find the article) that American made chips are 25%
more expensive than Taiwanese ones. I suspect that the purpose of
tariffs are to level the playing field but that will only handicap
manufacturing gains. No pain no gain, right?
From now on the posts are going to be less formal. I had some mental
model of what a blog should be (looking at you Hacker News...) and it
was really keeping me from writing. I wanted each blog post to be nice
and contained and provide some sort of intellectual value. But then I
realized, its my blog and I can do whatever I want. So here we are. I
still want to maintain some formality so that posts don't read like faux
corporate garbage or like Twitter/Reddit. I suppose that this really
means that the content not the style of posts will change. Anyways, I'm
not one to go back and rewrite things so earlier posts will have to
stand on their own.
I'd been putting off learning tmux because I have been using tiling
window managers for a while, and whats the point of using a multiplexer
in a tiling window manager? Well, when you have a remote system. I
found myself (embarrassingly) opening multiple terminals and
authenticating on my server each time. It really wouldn't have bugged
me except that I found myself doing this almost every time I had to do
something remotely. There were two of options for terminal multiplexers
that were common: screen and tmux. screen is the simpler of the two,
however it doesn't have as many features like the built in status bar
and being able to split windows in half horizontally or vertically like
a tiling window manager. I was leaning more towards screen initially
because I had used it before, but after about a day of using I got tired
of only having one shell per window. This could only lead to one thing...tmux!
Its kind of a headache trying to learn the keybindings. tmux is genuinely
the first program I've used in a while that has keybindings that give vi a
run for it's money. I took a look at the man page and it seems like its
almost the opposite of vi in terms of ergonomics. The most common
commands, like splitting windows, use keys like " or % and there seems to
be a bit of feature creep with features like sessions. It really is a
GNU type program. I would say the learning curve is definitely steeper
than screen, however it pays off to split the windows, plus tmux can do
anything that screen can. The only downside is that tmux is less
standard than screen, however that's not really an issue nowadays as both
can be easily installed from standard repositories.
Speaking of vi, when I'm writing prose it drives me nuts that I can't
use the ( or ) commands because I'm not used to using two spaces after a
period. Supposedly two spaces is a artifact from the days of typewriters
so that the period would stand out from the rest of the text. I don't
have a source so do with it what you will. I didn't learn to type with it
and it hasn't been standard for ages, but vi is the one program that is
holding on to it. I don't know if its worth making myself seem older so
that I can use those sweet, sweet motion commands. I'll give it a try in
the meantime.
I think that the idea that bloat is harmless is not sustainable. If you load a bloated site that loads 8 Mb of ads and other junk along with it it will inherently consume 400x more data than a static site that is only 20Kb. The bloat sites will go through 1Gb of data in 125 sites, over 30 days, thats about 4 sites per day. The more minimal sites would take around 50,000 to consume 1Gb of data, or 1700 sites per day, well more than humanly possible. While I cannot quantify the environmental impact, the economic impact would be huge. Just off of numbers from the last time I checked, a 1Gb/month phone plan in the U.S. runs you around $15/month. On the other hand, an unlimited plan costs upwards of $50/month. A 3x difference, or $400 per year difference. I find it ironic that many websites that advocate for climate change and cutting personal use take a whole 5Mb just to put some text on my screen. 5Mb doesn't seem like a lot util you write in plaintext. 5Mb = 5 million characters = a whole lot of text.
This is not the be-all-end-all list of TUI mail clients available for *nix.
This is just meant to be a light-weight guide so that it is easier to pick
through the many options available. Mail has been around for a long time
and this longevity has made it so there are more mail clients than minutes
in the day. The ones that I have chosen to look at are aerc, alpine/pine,
mailx, and mutt.
aerc is the most modern of the five and feels most similar to mutt. It uses
vi-like keybinds for folder and message navigation. The configuration is
very easy and there is a form that you complete on the first run. I like
this as you can get up and running quick, however this becomes an issue
once you have to change details, and then you are better off just learning
the config file anyways. The configuration style itself is nothing
special.
alpine/pine is an older client and it shows. The interface feels more
dated than aerc or mutt, however I found it more intuitive than mutt and
much more than aerc. Alpine is aimed more at novices and as such has all
the keybinds displayed on screen. I'll be honest, I sort of rolled my eyes
at it the first time I used it. However I'm not a huge email user so not
having to check the man pages for the keybind to reply or change
folders or move mail etc. is valuable. Ultimately what was a
dealbreaker for me was that the folder support is not perfect. It is
definitely usable, however for whatever reason the folders were not
pulled down correctly and there was a sort of double image next to each
folder that would not show anything. I don't know how to fix it and
didn't bother so it may or may not be a non issue. Alpine was a bit more
effort to set up with SSL owing to the fact that it hails from so long
ago. It was not a huge effort to get ssl set up, however the
configuration is more verbose than the mutt or aerc.
mutt feels very much like a combination of aerc and alpine, although it
uses movement keys like vi it also displays some keybinds for email
specific commands. This works really nicely and makes it easy for vi
knowledge to transfer to it without having to learn a whole new set of
keys. The configuration is similar to aerc, however there is no wizard
to create it so you are left to rely on external examples. This turned
out to not be an issue as simple configs are easy to come by.
mailx is the simplest of the four and is the least customizable. It is
native to FreeBSD but is easily installed on most other systems. By far
the most lightweight and is the perfect choice for reading system mail.
The interface is similar to ex with simple one letter commands. It is
not a complete mail client in itself and for a desktop needs a program
to deliver the mail like fetchmail and a program like sendmail for
outgoing mail. I have not tried configuring sendmail, only fetchmail,
and it worked without a hitch.
I tend to lean towards programs that are simpler and have a lower
install size/less dependencies. The winner for simplicity is by far
mailx, however with this you have to do more heavy lifting yourself.
Then comes alpine, then mutt, then aerc. My personal choice is mutt.
I've used all of theses and mutt is the only one that I can still
remember how to use after a week. aerc is too complicated, alpine is
just clunkier, and I can't be bothered with mailx. Anyways, that about
wraps it up. Maybe I'll get mailx set up and see how that holds up.
I am finally Linux free! I have a desktop that is running FreeBSD and a
laptop that has always been confined to Linux, most recently Void Linux,
however the most recent release of FreeBSD (14.3) has finally made it
possible for me to use my laptop. I was waiting until the rtw89 drivers
got support for the RTL8852BE chip thats in my laptop. Although the
speeds are still pretty dismal, the best I saw on speedtest.net was 15mb/s
up/down, the connection has been much more stable than NetworkManager on
Void. It was probably something with musl that was causing the WiFi to
lose connection from the AP every fifteen minutes or so. Nothing crazy,
just a little inconvenient. The FreeBSD drivers have proven much more
reliable. It looks like I'll be stuck with wpa_supplicant, its good
enough for now.
Contrary to what I expected, the drivers worked right away. The install
went flawlessly and I was quickly greeted with a login prompt. The real
issues began with Xorg. Turns out my laptop does not have an external
graphics card and is just using integrated graphics. I wasn't especially
suprised however this turned into a nightmare for getting the Xorg
config right. It took me several hours to find the right drivers and
configuration files to get Xorg to start. I would share my config
however I don't think I would be able to properly explain it without
adding more noise to the already confusing mess that is graphics
drivers. Anyways, after much travail I did manage to get the graphics
card working after much travail I did manage to get the graphics card
working.
In terms of battery usage, I haven't been able to test it to see how it
stacks up against Linux. I am using powerd to control the CPU frequency
and this has been great so far at extending battery life and more
imporantly making it run much cooler. There seems to be some material
out there documenting how to increase battery life however it will
definitly be more involved than installing tlp on Linux which was
practically set-and-forget. Once I get the chance I'll nail down some
more concrete numbers and methods.
Sound was another thing that gave me more trouble than expected. Getting
pulseaudio installed and using the speakers was no issue at all. The
real battle is in getting the headphone jack to work. No matter what
I've tried, audio just doesn't want to come out of the headphone jack.
Its not the end of the world, but not something that I expected.
A little known feature of most shells is that there is a command line
editing mode so that you can use the command line with the same keybinds
as vi or emacs. I never thought much of this before I started using
pretty much only vi for my day-to-day editing but now I find it
inconvienent to have to mash arrow keys for shell history.
Right now im split between using tcsh on FreeBSD and bash on Void Linux,
but luckily since the keybinds are derived from vi there isn't any
difference in the actual usage, just in the configuration. With tcsh you
just add
bindkey -v
to your .tcshrc or add
set -o v
to your .bashrc. Now you can use vi (or emacs) to navigate your history
or edit the command line. A helpful feature, in bash at least, is that your prompt will
change with whatever number you are using for motion commands.
I'm reallly a sucker for the vi keybinds wherever they may pop up. Even
in leetcode they have them and they don't go unnoticed.
Continuing on my journey into productivity tools the next program that I wanted to
make was a agenda/todo list. Of course with Xaw.
The first major roadbump that I encountered was getting text boxes for input to
work. The program had to have a feature to insert new events so I really
couldn't skip this. Even after looking at the documentation I couldn't make
heads or tails out of how to get it to work so I took a look at the source code
for xedit and it was
enough to get some simple text boxes working.
Another feature that was a must have was a scroll bar for the output window.
There was just no way I could excuse an infinitely growing window. This wasn't
so bad at first but how it interacted with it's children proved much much more
difficult to debug than expected.
If the container box and the viewport did not have the same width it would just
decide to not render. If the viewport did not have it's width updated every time
its children were re-rendered it would shrink down, which is great, until you
try to add more contents and the viewport is far too tiny.
I settled on a linked list for all the posts and individual box widgets with
contained controls so that you could for example delete an individual post.
However for some reason this caused the parent box that was directly a child of
the viewport (the scrolling widget) to grow horizontally and this would cause
all the widgets inside the box to disappear unless the flag allowHoriz
was set, but that would in turn cause a horizontal scroll bar which was quite
ugly. In addition to the ugly scroll bar, by having extra wrapper boxes around
the insides the scroll just didn't work! After a hour or two (or three) of
trying to fit a square peg in a round hole I decided to just have a label
on the inside and modify the contents to display events.
This finally got me the results desired and I'm fairly happy with how it turned
out. Email for the source.
I'm a big fan of the Pomodoro method. For those who don't know, its a
method of time management where you work for 20-30 minutes then take a
short break for 5-10 minutes. After repeating this work-break cycle four
times you take a long break. The most common intervals I've seen are 25
minutes of work and 5 minutes of rest with a long break of 35 minutes so
that everything wraps up into a nice 2.5 hour block.
The most important aspect of the technique is the timer. While there are
plenty of good apps for mobile that do this, there are not a lot of
options when it comes to desktop. There were essentially three options
that I saw.
While just using whatever JS app that someone farms advertising revenue
off of was a real option, I don't always have/need a browser open when
I'm using my desktop and because it would be in the browser it would be
hard to leave it on top of my other windows.
I did not want to download a 70MB timer. Simple as that. I mean it's a
timer, does it really need to look that good?
The terminal options looked good, however they were definitely limited
by the constraints of the terminal. Because the clock has to run
asynchronously from user input that pauses or otherwise interacts with
the program input buffering is really not condusive to a good user
experience.
While a solution would be to run a daemon for the timer, is that not
hammering a screw? I don't think its necessary for a timer to be
multithreaded or require IPC.
This lead me on a search for a simple X11 pomodoro app. Even Qt would
have been fine. Alas, it seems that somehow pomodoro timers attract the
type of users that change their config files all day. Maybe a pomodoro
to help them concentrate on retheming hyprland and neovim for the second
time today. The problem looked simple enough, so rolling my own was
really the only option that was going to leave me satisfied.
This led me down the rabbit hole of X11 development. I use xcalc quite a
bit and this led me to Xaw (X athena widgets). Xaw is a libarary of
widgets that you can use to build apps on top of Xt, which lets you
build apps on top of X11 (with Xlib and XCB). The wikipedia article does
a great job of explaining the hierarchy and relationship of libararies
like Xaw and Xm more modern ones like GTK and Qt to X11. Its interesting
to note the "GUI Wars" between Motif and OpenLook and how it mirrors the
seemingly never ending debates between text-editors, browsers,
programming languages, etc. Xaw is noresource intensive and looks good
enough for a simple timer so it was a no brainer to pick it.
Ok, so I have a library picked out, now its time to get maybe a example
project and go off of that right? Nope. The most advanced program with
source that wasn't a full blown app was a hello world. So looks like the
docs will do most of the heavy lifting. Except that some functions are
only docuented in HPUX in a man page archive. Thankfully although the
docs are scattered, the coverage is wide enough that with a little
persistence you can figure out whats going on.
I won't drag about the details but here are some things that I picked up
that might help you if you decide to make something with Xaw.
Thats it for this article. If you're interested, email me for the source.
No major spoilers but some
characters will be referenced.
Nothing outside of the first 10
minutes though.
I recently decided to watch Dr.
Strangelove off of a
recommendation from a friend.
Apparently this movie is up
there with films like
Citizen Kane in the
greats of American film. It's a
very approachable film lasting
just under 100 minutes (1:38)
and is set in Cold War America.
It is definitely more relevant
than ever and the insanity of
the whole situation is a little
frightening especiallly the
parallels between Gen. Ripper
and RFK Jr. While it is a tad
crude with the many references
to "precious bodily fluids" it
does feel eerily familiar to
a certain someone's thoughts on
Autism... The plot really shines
in moments like these where it
is so close to reality that there
are moments where you forget that
its a comedy.
No other film that I have
watched has done such a good job
of capturing all the various
stereotypes and really the state
of life of the sixties.
Although outdated and WASPy, the
film really captures the essence
of what it was like in the
1960's in the "room where it
happens". The film has it all,
the ditsy secretary, the
acedemic (Dr. Strangelove), the
suburban middle aged man (Gen.
Turgidson), the texan (Major
Kong), and the upper middle
class "soft?", I don't exactly
know what to call it, guy (Pres.
Muffley). From talking to some
folks that were around back then,
I got the sense that they lived,
not exactly in constant fear, but
more aware of the effects of total
war and had to come to terms
with their mortality in a way
that is lost on us today.
Between their fathers
and maybe mothers serving in WWII and
conflicts like the Cuban Missile
Crisis, these issues were
perpetually at the forefront
of people's minds. I hope that
we do not have to go through
something like WWII again, but
facing those issues definitely
make a huge positive change in
how you live your life and
sadly war seems to be the only
way that people will come to
terms with them
While the film is still relevant
even today, I think that it
would be hasty to draw direct
connections between the nuclear
crisis and say Trump's tarrifs
or threats of war. The world has
changed tremendously in the last
sixty years and I don't know if
the dynamics at play then are
even remotely comparable to
today. Then they had only two
superpowers, the U.S. and
U.S.S.R. but now with China
being the main threat to the
U.S.'s power but with Russia
still being "in the game"
there's somewhat of a awkward
"love" triangle between them and
Europe and the rest of the world
stuck in the middle. Yikes!
All in all, its a great movie I
would whole-heartily recommend
it. I would say more but I don't
want to spoil it.
wmx is a cute little window manager that has changed my mind on floating
window managers and has really captured my heart. Heres the quick notes, then a longer
review below.
type - floating
installation - from source
configuration - through source or symlinks
keybinds - kind of
resource usage - 20kb (irrelavant)
I was expecting a really dated experience however due to the design
choices it has really stood the test of time. I wouldn't go as far as to
call it timeless, however it still passes as semi-modern because of the
lack of skeumorphism. Personally skeumorphism was a cool concept, but it
has not aged well.
A distinctive part of the window manager is that the window titles are
positioned vertically on the left side of the window. This actually
works really well when you have a lot of windows overlapping. On the average
laptop/desktop screen, most windows tend to get crowded
vertically instead of horizontally, so veritical titles work a lot
better at identifiying windows than horizontal ones. A great feature that
I find lacking in other floating window manager is a good implementation
of virtual workspaces. Something that bugs me with window managers is
that they are reliant on a external bar to identify the current
workspace. Even window managers like dwm don't display something
indicating which workspace is selected. The way that wmx implements it
is a digit in the top right corner that appears when you change
workspace and disappears after a delay. This is the perfect touch to
make the barless experience work. Of course if you aren't a fan you can
disable it in Config.h
I was a little intimidated at first after the initial build by the lack
of documentation on configuring it, however, the source code is one of
if not the best examples of self documenting code. Config.h (the main
way of configuring wmx) is well structured and comments lay out every
paramater that could be configured. It is truly a shining example of
what code should be. I don't feel that I need to go into much detail of
building and installing it, the README is more than enough to get you
started.
I don't feel that I need to go into more detail concerning configuration
as the source does a better job than I could. If you want to download
it, the source can be found here.
Thanks for reading!
I've noticed that I've been spending too much time on hacker news and youtube so I looked into some options for when my self restraint isn't enough. the first would be to add some sort of extension for the browser but these are too easy to get around, just a simple right click and delete extension. I opted to go for a more robust solution. In /etc/hosts there are some ips bound to hostnames like 127.0.0.1 to localhost. although this is useful for setting hostnames, it can also be used to block certain sites. The format is
ip-address hostname 127.0.0.1 localhost
If you put 127.0.0.1 (localhost) as the ip and any domain you want to block as the hostname, all traffic will be rerouted to localhost and will be rejected unless you are running a http server locally. Could be used to remind yourself if you go to those sites out of habit. Anyways heres a list of social media domains that could be time drains.
127.0.0.1 news.ycombinator.com 127.0.0.1 www.reddit.com 127.0.0.1 old.reddit.com 127.0.0.1 youtube.com 127.0.0.1 www.youtube.com 127.0.0.1 www.instagram.com 127.0.0.1 x.com 127.0.0.1 ifunny.co 127.0.0.1 www.tumblr.com 127.0.0.1 bsky.app 127.0.0.1 mastodon.social 127.0.0.1 tenor.com 127.0.0.1 www.facebook.com
Another application could be for adblocking with minimal browsers like
surf.
On a different note, I'm probably going to redesign the site, I'll try
to keep the css simple and light on network but its hard to get a
balance between design and size. Also maybe a media dump?
I use xterm because its simple, lightweight, and comes default with
many distros. Xterm is a terminal emulator simple as that. Just a no
frills terminal emulator. Although there is no gpu acceleration like in
Kitty or Alacritty, it doesn't really matter. A terminal emulator's job
is to display text on your screen not play games. In my experience with
all three i haven't noticed a difference performance wise between them.
side note for tiling window managers. Why use a terminal emulator with
tabs/tiling if you're going to use it in a twm anyways?
The installed size is about a fourth of Alacritty or Kitty and it has
about half as many dependencies as Kitty, and a tenth of Alacritty.
Kitty and xterm both share many dependencies with the default X11
libraries, however Alacritty has significantly more dependencies to
install because it is built on rust. Kitty also depends on python, for
better or worse. I do not have any definite numbers on memory usage of
Alacritty or Kitty, however the memory usage of xterm is trivial, using
about 16kb of memory.
The best however, is that xterm is the default for most distros' X11
package. Ultimate ease of use. The main downside of using xterm is that
background transparency is not well implemented (external tool) and blur
is not possible. The default theme is also pretty ugly, but it is not
any more difficult to change than any other emulator. There are decades
worth of .xresources to choose from. Just remember to merge the changes
to the x resources database. Besides eyecandy, xterm is a great option
if you are looking for low memory/storage footprint, simplicity, and
ease of use.
Foreword: When I was looking for the DNS entries for DKIM, SPF, and DMARC I
didn't find any info online about how to do it for FreeDNS, so I thought
I would share what I found worked.
This post will only cover setting up the DNS entries for email
verification, NOT the server side configuration. That will be more
specific to whatever SMTP server you use. More advanced configuration
options will not be covered, this is just a basic overview. The guide I
used: [set up postfix + dovecot with DKIM, SPF, and DMARC]
On my quest to set up a mail server I came across DKIM in the tutorials
I found, but I put it off because it required messing with your DNS
entries. However when sending to any other email service with spam
protection (basically all of them) the mail would go straight to junk
and a warning would come up complainging that it couldn't verify the
authenticity of the message (what DKIM does). Having your mail go
straight to junk defeats the point of having it and telling people to
check their spam folder is annoying and might not always be possible. So
I bit the bullet and set it up.
When going to add DNS entries for you subdomain that have underscores in
them (required for DKIM and DMARC) FreeDNS will not let you and you
will have to contact support to enable it for you. Don't let this
discourage you! the support is super friendly and if you don't have a
history of abuse they will unlock it for you.
SPF:
Just a TXT entry. Select TXT from the dropdown. For the subdomain use
whatever the subdomain for the A (or MX) entry that you use. Now the
destination will be:
"v=spf1 a:[YOUR FULL DOMAIN NAME] -all"
This basically declares that the entry is a SPF entry and says that all
mail should come from the DNS entry. Use a for an A entry, mx for a MX
entry, etc.
DKIM:
Also a TXT entry. For the subdomain it will be
default._domainkey.[YOUR SUBDOMAIN]
provided the marker for you DKIM key is default. Only use the subdomain because when the entry is created the rest of the domain will be appended to the name. The destination will be
"v=DKIM1; h=sha256; k=rsa; p=[INSERT YOUR KEY]"
It is almost certain that your key will be too long to hold in a single
set of quotation marks, so you can break the key up into two or three
separate blocks. The hash and algorithim can be adjusted, however this
should cover the most common combination.
DMARC:
DMARC is not immediately important, however by having it you make your
mail server look less sketchy and you are notified when mail fails DKIM
and SPF checks. You may as well do it while you are setting up the other
two. Another TXT entry. This time the subdomain is
_dmarc.[YOUR SUBDOMAIN]
And the destination is
"v=DMARC1;p=quarantine;pct=100;rua=mailto:[YOUR EMAIL]"
This will put messages that fail SPF and DKIM into the "junk" or "spam"
folder of the recipient and mail 100% of the reports to the specified
address. When testing I recommend setting p to none so that your mail
will go through, however after you confirm that it is working setting
it to quarantine or reject would be safer.
Hope you got some value from this. Thanks for reading!
I never realized how terrible it is to set up a mail server. talk about a
headache. Email was a mess as is before encryption, however what makes it so bad
is that the old ports and services are still used on top of the new encrypted
channels.
Anyways, I decided to set up Postfix and Dovecot on the server to do some small
email hosting. It didn't seem to difficult and I looked up a tutorial and got to
work. Getting plaintext mail was trivial, however thats not really great for any
real usage. Most tutorials I saw recommended setting up DKIM alongside
encyrption, but I decided to save that headache for another day. Dovecot and
IMAP/IMAPS was relatively easy to setup, pretty much just copy paste some
configuration and fill in SSL keys, but the real issues came from Postfix. I was
initially testing the server using BSD mailx, but that came to be the source
of a fair bit of confusion. It wasn't until deep into the process that i
realized it was prefixing my hostname onto the target domain and the fix didn't
seem easy so I had to abandon that. Moving onto aerc I was finally able
to connect to the server but wasn't able to send any mail. This was because nowhere
in the tutorials did they explain that SMTPS had to be configured alongside
SMTPd. So I changed the configuration thinking that SMTPS was a drop in
replacement with encryption. Not that easy. Turns out that SMTP is needed
between servers (why?) and SMTPS submission needs a seperate port as well.
Just a side note, but using a SMTP/IMAP mail server uses five ports for what
could seemingly be done in two. Im probably not smart enough to think of a
better solution but just my two cents.
Thats the end of this post. Look for more soon!
For the new site I decided what better way then to make a static site generator! how it works is you have a file about.txt that has your about section, a directory posts with the posts in seperate files, and a directory templates with a template for the home page and post sections. The go executable basically just fills in the posts and links them back to the home page. My previous page was just not a whole lot of fun because I had to manually copy over each post and fill in a template, now I can make the computer do the boring work. I might release the source soon, but its not ready for the public yet. Look for more posts soon!