fluix

Location: Waterloo, ON, Canada

Remote: Yes

Willing to relocate: No

Technologies: Python, Django, Go, HTML, CSS, (and a bit of C, C#, and Rust)

Résumé/CV: https://guikal.org/resume.c79b71d3.pdf

Email: steven@guikal.org

Website: https://guikal.org

Blog & Projects: https://fluix.one

Undergraduate computer engineering student at the University of Waterloo looking for a full-time co-op placement/internship for 3-4 months starting in September.

I have several years of system administrator experience with Debian, Alpine, and Arch, and web development experience with Django and Go, alongside personal and volunteer experience in a broader array of technical topics. I like to say I’m gradually working towards the lower levels of the programming stack (embedded systems, hardware) relative to my current work.

Cybersecurity is another interest of mine. I've competed in a handful of CTFs and placed highly in Canadian and international cybersecurity competitions. My previous work term was as a security research and development student at BlackBerry.

As mentioned, I'm still exploring the landscape in terms of different roles and companies, so don't hesitate to reach out :)

Could you describe what you found difficult? I'm pretty new to packaging on Alpine, but found it to be easy to get into, only requiring a bit more effort than the AUR.

I've found packaging for Alpine has been similarly easy. There is a review process in the sense that you file an MR instead of committing directly, but my experience has been really quick and easy. Also, not everyone with commit access does this, but psykose would also fix minor issues like indentation without requesting changes and doing the whole back and forth. I really appreciated it and noticed the changes for next time.

The community and main repositories have some stability guarantees but that doesn't stop you from orphaning the package.

Pages hosted on github pages also show the unicorn 503 page. However, https://pages.github.com/?(null) loads.

This appears to impact Github pages as well. <username>.github.io pages show the unicorn 503 page.

> We're having a really bad day.

> The Unicorns have taken over. We're doing our best to get them under control and get GitHub back up and running.

Don't have a good resource of my own either, but I think I would prefer more descriptiveness. Reading the various options you've written gives me totally different ideas of the image in my mind so, especially if it's important to the website, more descriptiveness seems appropriate for higher accuracy.

I find it particularly interesting that they post this as if it's a discussion to be had with the community yet they've already gotten permission[1] from developers by asking them beforehand, in private.

[1]: https://github.com/audacity/audacity/discussions/932#discuss... (comments from developers themselves also exist further down in the thread)

> [...] there's no guarantee that RDRAND won't revert to the -1 behavior after the check runs, perhaps after a VM migration or resume from suspend or what-not.

Author here. This is true and is an issue with some CPUs (breaking RDRAND after resume), but every call to RDRAND is guarded[1] by a check that it works.

[1]: https://github.com/json-c/json-c/blob/041cef434afe0d0c6da8b6...

Edit: Ah, I just realized you stated "after the check runs" and you're correct, there's no way that can be guaranteed.

Edit 2: Well, if RDRAND returns a value json-c can't use (-1) it won't be used.

Author here. Not particularly sure myself, even systemd says it only does so because it does things early in the boot process[1]. Using it for it's purpose here is probably alright, but the odd part is prioritizing it[2] over /dev/urandom.

[1]: https://github.com/systemd/systemd/blob/301e7cd047c8d07715d5... [2]: https://github.com/json-c/json-c/blob/31f1ab2be1142d982fc9b8...

Author here. I believe it's kept because at the end of the day, they _must_ get a valid value form it; however, the chances of that loop having to run more than once are astronomically low.