This gem was last updated on the 30.01.2024 (dd.mm.yyyy notation), at 13:39:46 o'clock.

The HardwareInformation Project

The above image has been partially auto-generated by cfdg (context free design grammar). The cfdg gallery can be seen at: https://www.contextfreeart.org/gallery/search.php?t=new&num=25

You can re-use the above image and change / re-shape it in any way, shape or form, under a CC BY-SA 4.0, if you would like to. (I should improve the image and remove the edgy blur effects, but it is just some logo so that this gem also has a logo. I did not want to invest too much time into this logo.)

The CC BY-SA licence can be read here: https://creativecommons.org/licenses/by-sa/4.0/

Requiring the HardwareInformation gem

You can require this gem via:

require 'hardware_information'

HardwareInformation.report

This toplevel API will report what hardware has been found on the given computer system.

Colour support

By default class HardwareInformation will try to show colours, if used from the commandline.

If this is unwanted, you can pass any of the following flags to disable colour support:

--disable-colours
--disable-colors
--no-colours
--no-colors

Example screenshot of the output generated by class Hardwareinformation

Contact information and mandatory 2FA (no longer) coming up in 2022 / 2023

If your creative mind has ideas and specific suggestions to make this gem more useful in general, feel free to drop me an email at any time, via:

shevy@inbox.lt

Before that email I used an email account at Google gmail, but in 2021 I decided to slowly abandon gmail, for various reasons. In order to limit the explanation here, allow me to just briefly state that I do not feel as if I want to promote any Google service anymore when the user becomes the end product (such as via data collection by upstream services, including other proxy-services). My feeling is that this is a hugely flawed business model to begin with, and I no longer wish to support this in any way, even if only indirectly so, such as by using services of companies that try to promote this flawed model.

In regards to responding to emails: please keep in mind that responding may take some time, depending on the amount of work I may have at that moment. So it is not that emails are ignored; it is more that I have not (yet) found the time to read and reply. This means there may be a delay of days, weeks and in some instances also months. There is, unfortunately, not much I can do when I need to prioritise my time investment, but I try to consider all feedback as an opportunity to improve my projects nonetheless.

In 2022 rubygems.org decided to make 2FA mandatory for every gem owner eventually:

see https://blog.rubygems.org/2022/06/13/making-packages-more-secure.html

Mandatory 2FA will eventually be extended to all rubygems.org developers and maintainers. As I can not use 2FA, for reasons I will skip explaining here, this means that my projects will eventually be removed, as I no longer have any control over my projects hosted on rubygems.org (because I can not use 2FA).

At that point, I no longer have any control what is done to my projects since whoever is controlling the gems ecosystem took away our control here. I am not sure at which point ruby became corporate-controlled - that was not the case several years ago, so something has changed.

Ruby also only allows 2FA users to participate on the issue tracker these days:

https://bugs.ruby-lang.org/issues/18800

But this has been reverted some months ago, so it is no longer applicable. Suffice to say that I do not think that we should only be allowed to interact on the world wide web when some 'authority' authenticated us, such as via mandatory 2FA, so I hope this won't come back again.

Fighting spam is a noble goal, but when it also means you lock out real human people then this is definitely NOT a good situation to be had.