bits 0x33 - Calender Week 51, 2023

I’m exhausted.
Mostly I have to get some paperworks done. Collecting x from here, y from there, go back to get z, fill a formular, emails, emails, emails, then send a letter to XXX. But I finally got it done by Friday so I can sit done and do something fun/productive.

Deutsche Bank
If I had the choice I won’t fucking use Deutsche Bank anymore. The Deutsche Bank pretty much summarizes all the bads about Germany, yes I’m talking about bureaucracy and digitalization which doesn’t exists. Plus I had some bad experience with their clerk.

cost vs gain
There was a project that my Prof and I spent some good hours on in the hope that it may become my master thesis. But then the problem haunts:

What’s this good for?

Yeah, as simple as that. We have a hammer (a design that trades off some security to make syscalls faster), but we can never find a nail that justify the cost (and the additional complexity).

In the end this topic is … well, dropped. Actually it’s nevertheless justified as a good amount of work in the scope of a student thesis, but it is not a good feeling when you spend your life on something knowing that this will be thrown away the moment you conclude the project.

I’m starting with something new. On the good side, the new one is equally interesting to me.

There is no limit to the HACKS

HideM: Protecting the Contents of Userspace Memory in the Face of Disclosure Vulnerabilities

Using split TLB to have execute-only memory. That’s really smart and I’m amazed.

UX
people talk about the superiority of UNIX systems. But they talk as if “User Experience” is not a thing.

People design (very good) tools with bad UI/UX, and, if you dare complaining about it it’s your fault because you don’t read the (un)friendly manual and it’s your problem that you can’t live in the commandline 24/7.

I had the need to convert a markdown file to html.

  • I first tried my vim plugin, everything looks fine but I simply can’t “export” it to HTML. I read the issues, only to find this “feature”1 is NOT supported.
  • I tried md2html but its syntax support is very limited; tables are broken; footnotes are not there, let alone the math support!
  • I tried pandoc and, for fucks sake it’s composed of 225 haskell packages and takes 534.9 MB of disk2! And it didn’t cover my needs either! (a little better than md2html but still..) And it even complains about my markdown syntax because I put some bold text **like this** in the beginning and it mistook that for a bad yaml front matter!
  • You know what fucking works? My blog! Yes, I need to create a new (hugo) post, copy paste the markdown, copy paste the images and parse the url, then render the blog and save the HTML from browser. But for something semi-formal that I need to share with people, I had to take the time to strip my blog themes and metadata. I soon gave up.
  • Yeah, in the end vs code + a markdown plugin did the job. Two clicks and it’s done.

What gives!

either the kernel or the Firefox is broken
I know element sucks, but when element breaks firefox it’s FF’s fault! This happened to me for more than 10 times. Like, I’m typing in a chat, and it just freezes. I have to pkill firefox and restart and lose all text I typed. There is not even a coredump: I suppose it’s not registered as a “crush”.


  1. why should this be a feature in the first place! I’m looking at a rendered webpage in my browser and I want to save what I see into a local html file. THIS CAN’T BE DONE because of the plugin uses nodejs to render stuffs dynamically. ↩︎

  2. on archlinux with pacman. ↩︎

[+] click to leave a comment [+]
the comment system on this blog works via email. The button
below will generate a mailto: link based on this page's url 
and invoke your email client - please edit the comment there!

[optional] even better, encrypt the email with my public key

- don't modify the subject field
- specify a nickname, otherwise your comment will be shown as   
  anonymous
- your email address will not be disclosed
- you agree that the comment is to be made public.
- to take down a comment, send the request via email.

        
>> SEND COMMENT <<
[BITS] - the weekly archive -
bits 0x54 - Week 35~?, 2024 (WIP)
bits 0x53 - Week 28~35, 2024
bits 0x52 - Week 17~27, 2024 [VOID]
bits 0x51 - Calender Week 17, 2024
bits 0x50 - Calender Week 16, 2024
bits 0x49 - Calender Week 15, 2024
bits 0x48 - Calender Week 14, 2024
bits 0x47 - Calender Week 13, 2024
bits 0x46 - Calender Week 12, 2024
bits 0x45 - Calender Week 11, 2024
bits 0x44 - Calender Week 10, 2024
bits 0x43 - Calender Week 09, 2024 [VOID]
bits 0x42 - Calender Week 08, 2024 [VA]
bits 0x41 - Calender Week 07, 2024 [VOID]
bits 0x40 - Calender Week 06, 2024 [VOID]
bits 0x39 - Calender Week 05, 2024
bits 0x38 - Calender Week 04, 2024
bits 0x37 - Calender Week 03, 2024
bits 0x36 - Calender Week 02, 2024 [VA]
bits 0x35 - Calender Week 01, 2024
bits 0x34 - Calender Week 52, 2023
bits 0x33 - Calender Week 51, 2023
bits 0x32 - Calender Week 50, 2023 [VOID]
bits 0x31 - Calender Week 49, 2023
bits 0x30 - Calender Week 48, 2023
bits 0x2f - Calender Week 47, 2023
bits 0x2e - Calender Week 46, 2023
bits 0x2d - Calender Week 45, 2023
bits 0x2c - Calender Week 44, 2023
bits 0x2b - Calender Week 43, 2023
bits 0x2a - Calender Week 42, 2023