Closed seanpm2001 closed 2 years ago
π Days until 2 year GitHub :octocat: anniversary: UNDETERMINED
(as of 2022 January 1st at 00:12:00 am to 11:59:59 pm)
:octocat: GitHub consecutive day count: 587
Count revised and updated on July 16th 2021 via DuckDuckGo (As of 2022 January 1st at 00:12:00 am to 11:59:59 pm)
π§ Linux desktop consecutive day count: 542
(as of 2022 January 1st at 00:12:00 am to 11:59:59)
πͺ Windows 10 with GitHub consecutive day count: 45
(as of 2021 December 31st at 00:12:00 am to 11:59:59)
π§ Ubuntu 20.04 with GitHub consecutive day count: 542
(as of 2022 January 1st at 00:12:00 am to 11:59:59)
:atom: Total amount of original GitHub repositories: 1,624+o
(as of 2022 January 1st at 00:12:00 am to 11:59:59 pm)
I have noted that GitHub rounds up the total number of each statistic, so when something reaches 50 after the kilo point (once it reaches 1000) it rounds up to the next kilo, so 1050 would be 1100, 1150 would be 1200, and so on.
:atom: o=organizations, total number of non-fork organization repositories: 115
as of 2022 January 1st 00:12:00 am to 11:59:59 pm)
Organization repo count guide
Org repo (non-fork) count
Snap repos: 29 (formula: Org:Seanpm2001-snapcraft minus current.unforked minus 4) (verified count, as of July 21st 2021)
.github.io: 79 (80 when including seanpm2001/seanpm2001/github.io/) (formula: org:Seanpm2001-GitHub-Pages-Collection minus current.unforked minus 4) Verified count (as of July 9th 2021) unverified count (as of July 26th 2021)
Count verification needs to be re-checked - July 13th 2021 ((X1 Count verification needs to be re-checked - July 14th 2021 X2:: Count verification needs to be re-checked - July 15th 2021 X3:: Count verification needs to be re-checked - July 16th 2021 X4:: Count verification needs to be re-checked - July 17th 2021 X5)) No new data for this range, update count verification when ready
:electron: Repositories created so far this month: 0+o
(as of 2022 January 1st at 00:12:00 am to 11:59:59 pm)
:shipit: Organization count: 760
(as of 2022 January 1st at 00:12:00 am to 11:59:59 pm)
:electron: Organizations created so far this month: 0
(as of 2022 January 1st at 00:12:00 am to 11:59:59 pm)
I had an OK day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage, and the amount of work I am behind in is just piling up.
I have lots planned, but I just continue to fall behind. Today, I learnt of a syntax error in almost every C++ and C script I have written, which is the end of line character. I am so used to Python that I forgot that newlines are required. Every script in a language like this should have ";
replaced with \n";
I am still working on getting caught up, and there is another possible power outage event that can happen tomorrow.
I am working on transitioning the labeling of commits again, changing README.md - Didn't play
to README.md - No data
as I want it to be more professional. I am slowly starting to do this as of 2021 November 23rd. I am also looking for ways to make my daily desktop screenshots more interesting.
I have a new standard for issue archival today (2021 November 19th) now finally including labels, dates, and users.
I am in the adoption process of the GNU philosophy, and I am still currently trying to find my opinion on the "Linux" vs "GNU/Linux" debate.
I now have a new set of standards to how projects are written. For example, 2 workflows are mandatory in every project: super-lint
and makefile
. CodeQL-analysis
is an optional must-have as well, but isn't available in all projects.
I have a system for workflows now being established. I use them to test if my software is working correctly, and what needs to be fixed. I am still very new to this, and I am learning the process. It is unlikely I will master the entire system by myself. Currently, if a project has JavaScript functionality, I will include workflows for various JavaScript environments, such as Grunt, Gulp, Node, Webpack, Deno, and others. This way, I can test to make sure cross-platform compliant JavaScript source code is being made. The super linter is used as a catch-all to lint any/all programming languages present. The makefile workflow is for testing the makefile at the root of every modern repository, and also other makefiles that maybe included.
Actions:
super-lint.yml
makefile.yml
Daylight savings time came into effect on Sunday 2021 November 7th at 2:00 am (when the time went back to 1 am) for users outside of North America/The United States, please factor that if I say 1 pm, I mean 12 pm. Yes, I hate this system too, it is ridiculous that it is still being used.
This section has been collapsed for readability. Click/tap here to expand/collapse this section.
Click/tap here to expand/collapse older entries
Click/tap here to expand/collapse this section
...Lets not go any further until you reach 200k
TODO: Translate status file into multiple languages using Bing Translate or DeepL proposed {2021:AugustsuguA:1202}
TODO: MIME and magic number for ScreenTeX, TeX support
All times are UTC-7 (PDT/Pacific Time)
You may need special rendering support for the <dropdown>
HTML tag being used in this document
Majority language is: English (EN_US) / Markdown / HTML5
Minority languages include: Russian (RU)
(To be translated: Esperanto
, Spanish
, Hindi
, Vietnamese
, Japanese
, Khmer
, etc.
)
Encoding: UTF-8
(with some Emojis, and some Unicode 13.0 characters, such as πͺ)
File type: Markdown document (*.md, *.mkd, *.mdown, *.markdown)
Line count (including blank lines and compiler line): 3,843
π Days until 2 year GitHub :octocat: anniversary: UNDETERMINED
(as of 2022 January 1st at 00:12:00 am to 11:59:59 pm)
:octocat: GitHub consecutive day count: 588
Count revised and updated on July 16th 2021 via DuckDuckGo (As of 2022 January 2nd at 00:12:00 am to 11:59:59 pm)
π§ Linux desktop consecutive day count: 543
(as of 2022 January 2nd at 00:12:00 am to 11:59:59)
πͺ Windows 10 with GitHub consecutive day count: 45
(as of 2021 December 31st at 00:12:00 am to 11:59:59)
π§ Ubuntu 20.04 with GitHub consecutive day count: 543
(as of 2022 January 2nd at 00:12:00 am to 11:59:59)
:atom: Total amount of original GitHub repositories: 1,627+o
(as of 2022 January 2nd at 00:12:00 am to 11:59:59 pm)
I have noted that GitHub rounds up the total number of each statistic, so when something reaches 50 after the kilo point (once it reaches 1000) it rounds up to the next kilo, so 1050 would be 1100, 1150 would be 1200, and so on.
:atom: o=organizations, total number of non-fork organization repositories: 115
as of 2022 January 2nd 00:12:00 am to 11:59:59 pm)
Organization repo count guide
Org repo (non-fork) count
Snap repos: 29 (formula: Org:Seanpm2001-snapcraft minus current.unforked minus 4) (verified count, as of July 21st 2021)
.github.io: 79 (80 when including seanpm2001/seanpm2001/github.io/) (formula: org:Seanpm2001-GitHub-Pages-Collection minus current.unforked minus 4) Verified count (as of July 9th 2021) unverified count (as of July 26th 2021)
Count verification needs to be re-checked - July 13th 2021 ((X1 Count verification needs to be re-checked - July 14th 2021 X2:: Count verification needs to be re-checked - July 15th 2021 X3:: Count verification needs to be re-checked - July 16th 2021 X4:: Count verification needs to be re-checked - July 17th 2021 X5)) No new data for this range, update count verification when ready
:electron: Repositories created so far this month: 3+o
(as of 2022 January 2nd at 00:12:00 am to 11:59:59 pm)
:shipit: Organization count: 760
(as of 2022 January 2nd at 00:12:00 am to 11:59:59 pm)
:electron: Organizations created so far this month: 0
(as of 2022 January 2nd at 00:12:00 am to 11:59:59 pm)
I had an OK day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
The power outage didn't occur today, but it happened the next day in the morning. I have recently organized all my GitHub daily Monday to Sunday tasks into my main GitHub daily program, as they originally were, but due to how much is going on, it is causing severe RAM and SWAP issues, since there are nearly 300 tabs in this one profile.
I got caught up on my journaling today, but continued to fall behind on GitHub work. I archived my profile repo further, and did some other template work, but it was mostly an unproductive day.
For Marine Biology, my aquarium is still dirty, but we got a new plecostamus to help out. I am considering giving away some goldfish.
So far this year, the mistake of writing 2021 instead of 2022 has been extremely minimal.
I am working on transitioning the labeling of commits again, changing README.md - Didn't play
to README.md - No data
as I want it to be more professional. I am slowly starting to do this as of 2021 November 23rd. I am also looking for ways to make my daily desktop screenshots more interesting.
I have a new standard for issue archival today (2021 November 19th) now finally including labels, dates, and users.
I am in the adoption process of the GNU philosophy, and I am still currently trying to find my opinion on the "Linux" vs "GNU/Linux" debate.
I now have a new set of standards to how projects are written. For example, 2 workflows are mandatory in every project: super-lint
and makefile
. CodeQL-analysis
is an optional must-have as well, but isn't available in all projects.
I have a system for workflows now being established. I use them to test if my software is working correctly, and what needs to be fixed. I am still very new to this, and I am learning the process. It is unlikely I will master the entire system by myself. Currently, if a project has JavaScript functionality, I will include workflows for various JavaScript environments, such as Grunt, Gulp, Node, Webpack, Deno, and others. This way, I can test to make sure cross-platform compliant JavaScript source code is being made. The super linter is used as a catch-all to lint any/all programming languages present. The makefile workflow is for testing the makefile at the root of every modern repository, and also other makefiles that maybe included.
Actions:
super-lint.yml
makefile.yml
Daylight savings time came into effect on Sunday 2021 November 7th at 2:00 am (when the time went back to 1 am) for users outside of North America/The United States, please factor that if I say 1 pm, I mean 12 pm. Yes, I hate this system too, it is ridiculous that it is still being used.
This section has been collapsed for readability. Click/tap here to expand/collapse this section.
Click/tap here to expand/collapse older entries
Click/tap here to expand/collapse this section
...Lets not go any further until you reach 200k
TODO: Translate status file into multiple languages using Bing Translate or DeepL proposed {2021:AugustsuguA:1202}
TODO: MIME and magic number for ScreenTeX, TeX support
All times are UTC-7 (PDT/Pacific Time)
You may need special rendering support for the <dropdown>
HTML tag being used in this document
Majority language is: English (EN_US) / Markdown / HTML5
Minority languages include: Russian (RU)
(To be translated: Esperanto
, Spanish
, Hindi
, Vietnamese
, Japanese
, Khmer
, etc.
)
Encoding: UTF-8
(with some Emojis, and some Unicode 13.0 characters, such as πͺ)
File type: Markdown document (*.md, *.mkd, *.mdown, *.markdown)
Line count (including blank lines and compiler line): 3,858
π Days until 2 year GitHub :octocat: anniversary: 141
(as of 2022 January 3rd at 00:12:00 am to 11:59:59 pm)
:octocat: GitHub consecutive day count: 589
Count revised and updated on July 16th 2021 via DuckDuckGo (As of 2022 January 3rd at 00:12:00 am to 11:59:59 pm)
π§ Linux desktop consecutive day count: 544
(as of 2022 January 3rd at 00:12:00 am to 11:59:59)
πͺ Windows 10 with GitHub consecutive day count: 45
(as of 2021 December 31st at 00:12:00 am to 11:59:59)
π§ Ubuntu 20.04 with GitHub consecutive day count: 544
(as of 2022 January 3rd at 00:12:00 am to 11:59:59)
:atom: Total amount of original GitHub repositories: 1,629+o
(as of 2022 January 3rd at 00:12:00 am to 11:59:59 pm)
I have noted that GitHub rounds up the total number of each statistic, so when something reaches 50 after the kilo point (once it reaches 1000) it rounds up to the next kilo, so 1050 would be 1100, 1150 would be 1200, and so on.
:atom: o=organizations, total number of non-fork organization repositories: 115
as of 2022 January 2nd 00:12:00 am to 11:59:59 pm)
Organization repo count guide
Org repo (non-fork) count
Snap repos: 29 (formula: Org:Seanpm2001-snapcraft minus current.unforked minus 4) (verified count, as of July 21st 2021)
.github.io: 79 (80 when including seanpm2001/seanpm2001/github.io/) (formula: org:Seanpm2001-GitHub-Pages-Collection minus current.unforked minus 4) Verified count (as of July 9th 2021) unverified count (as of July 26th 2021)
Count verification needs to be re-checked - July 13th 2021 ((X1 Count verification needs to be re-checked - July 14th 2021 X2:: Count verification needs to be re-checked - July 15th 2021 X3:: Count verification needs to be re-checked - July 16th 2021 X4:: Count verification needs to be re-checked - July 17th 2021 X5)) No new data for this range, update count verification when ready
:electron: Repositories created so far this month: 5+o
(as of 2022 January 3rd at 00:12:00 am to 11:59:59 pm)
:shipit: Organization count: 760
(as of 2022 January 3rd at 00:12:00 am to 11:59:59 pm)
:electron: Organizations created so far this month: 0
(as of 2022 January 3rd at 00:12:00 am to 11:59:59 pm)
I had an OK day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date.
Today, I got to cleaning my desktop again. I now only keep 22 items on the desktop, the organization feels a lot better, and makes my system more responsive, because for some reason, the performance on Ubuntu depends on how many items are on your desktop (as 1 factor) for some reason. To keep the desktop unique, I am now changing the wallpaper on a daily basis.
Today, I also worked a bit on my V8 template, and finally got to changing my status on my GitHub profile from ποΈ Clippy
to ποΈ Python 4
which I came up with on the fly. I find it unique, as it gives a little mystique to some, such as "what does this person know about Python 4" but it can also be used jokingly. I wanted to change it, as it was obvious that Microsoft wasn't going to turn Clippy into an Emoji for GitHub, despite its announcement for another Microsoft product 5+ months ago. It is something I hardly spend time on.
I worked on 2 IDE projects today that I recently had the idea for. The first one, known as DIFFicult, is a Diff viewer and editor written in D, R, C, and Diff. I really liked the name, and wanted to experiment with Diff files. Despite the name being difficult
it is not difficult to use. The other project is an IDE known as Zag
which is an IDE for the Zig programming language. If you combine the 2 words, it is called zigzag
which is where the name comes from.
So far this year, the mistake of writing 2021 instead of 2022 has been extremely minimal.
I am working on transitioning the labeling of commits again, changing README.md - Didn't play
to README.md - No data
as I want it to be more professional. I am slowly starting to do this as of 2021 November 23rd. I am also looking for ways to make my daily desktop screenshots more interesting.
I have a new standard for issue archival today (2021 November 19th) now finally including labels, dates, and users.
I am in the adoption process of the GNU philosophy, and I am still currently trying to find my opinion on the "Linux" vs "GNU/Linux" debate.
I now have a new set of standards to how projects are written. For example, 2 workflows are mandatory in every project: super-lint
and makefile
. CodeQL-analysis
is an optional must-have as well, but isn't available in all projects.
I have a system for workflows now being established. I use them to test if my software is working correctly, and what needs to be fixed. I am still very new to this, and I am learning the process. It is unlikely I will master the entire system by myself. Currently, if a project has JavaScript functionality, I will include workflows for various JavaScript environments, such as Grunt, Gulp, Node, Webpack, Deno, and others. This way, I can test to make sure cross-platform compliant JavaScript source code is being made. The super linter is used as a catch-all to lint any/all programming languages present. The makefile workflow is for testing the makefile at the root of every modern repository, and also other makefiles that maybe included.
Actions:
super-lint.yml
makefile.yml
Daylight savings time came into effect on Sunday 2021 November 7th at 2:00 am (when the time went back to 1 am) for users outside of North America/The United States, please factor that if I say 1 pm, I mean 12 pm. Yes, I hate this system too, it is ridiculous that it is still being used.
This section has been collapsed for readability. Click/tap here to expand/collapse this section.
Click/tap here to expand/collapse older entries
Click/tap here to expand/collapse this section
...Lets not go any further until you reach 200k
TODO: Translate status file into multiple languages using Bing Translate or DeepL proposed {2021:AugustsuguA:1202}
TODO: MIME and magic number for ScreenTeX, TeX support
All times are UTC-7 (PDT/Pacific Time)
You may need special rendering support for the <dropdown>
HTML tag being used in this document
Majority language is: English (EN_US) / Markdown / HTML5
Minority languages include: Russian (RU)
(To be translated: Esperanto
, Spanish
, Hindi
, Vietnamese
, Japanese
, Khmer
, etc.
)
Encoding: UTF-8
(with some Emojis, and some Unicode 13.0 characters, such as πͺ)
File type: Markdown document (*.md, *.mkd, *.mdown, *.markdown)
Line count (including blank lines and compiler line): 3,877
π Days until 2 year GitHub :octocat: anniversary: 140
(as of 2022 January 4th at 00:12:00 am to 11:59:59 pm)
:octocat: GitHub consecutive day count: 590
(As of 2022 January 4th at 00:12:00 am to 11:59:59 pm)
π§ Linux desktop consecutive day count: 545
(as of 2022 January 4th at 00:12:00 am to 11:59:59)
πͺ Windows 10 with GitHub consecutive day count: 45
(as of 2021 December 31st at 00:12:00 am to 11:59:59)
π§ Ubuntu 20.04 with GitHub consecutive day count: 545
(as of 2022 January 4th at 00:12:00 am to 11:59:59)
:atom: Total amount of original GitHub repositories: 1,630+o
(as of 2022 January 4th at 00:12:00 am to 11:59:59 pm)
I have noted that GitHub rounds up the total number of each statistic, so when something reaches 50 after the kilo point (once it reaches 1000) it rounds up to the next kilo, so 1050 would be 1100, 1150 would be 1200, and so on.
:atom: o=organizations, total number of non-fork organization repositories: 115
as of 2022 January 4th 00:12:00 am to 11:59:59 pm)
Organization repo count guide
Org repo (non-fork) count
Snap repos: 29 (formula: Org:Seanpm2001-snapcraft minus current.unforked minus 4) (verified count, as of July 21st 2021)
.github.io: 79 (80 when including seanpm2001/seanpm2001/github.io/) (formula: org:Seanpm2001-GitHub-Pages-Collection minus current.unforked minus 4) Verified count (as of July 9th 2021) unverified count (as of July 26th 2021)
Count verification needs to be re-checked - July 13th 2021 ((X1 Count verification needs to be re-checked - July 14th 2021 X2:: Count verification needs to be re-checked - July 15th 2021 X3:: Count verification needs to be re-checked - July 16th 2021 X4:: Count verification needs to be re-checked - July 17th 2021 X5)) No new data for this range, update count verification when ready
:electron: Repositories created so far this month: 6+o
(as of 2022 January 4th at 00:12:00 am to 11:59:59 pm)
:shipit: Organization count: 760
(as of 2022 January 4th at 00:12:00 am to 11:59:59 pm)
:electron: Organizations created so far this month: 0
(as of 2022 January 4th at 00:12:00 am to 11:59:59 pm)
I had an OK day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date.
Today, I worked on continuing to try and catchup on repo archival work, and other catchup work, but still fell behind. I worked on the AdCap image repo project, along with sonme improvements to the DIFFicult IDE. I am trying to stay caught up, but I am still falling behind. Today, I did the usual work (minus most Git-image work) and I yet again skipped writing a status file (the notes for todays status were created on 2022 January 10th, and the post was written on 2022 January 12th)
So far this year, the mistake of writing 2021 instead of 2022 has been extremely minimal.
I am working on transitioning the labeling of commits again, changing README.md - Didn't play
to README.md - No data
as I want it to be more professional. I am slowly starting to do this as of 2021 November 23rd. I am also looking for ways to make my daily desktop screenshots more interesting.
I have a new standard for issue archival today (2021 November 19th) now finally including labels, dates, and users.
I am in the adoption process of the GNU philosophy, and I am still currently trying to find my opinion on the "Linux" vs "GNU/Linux" debate.
I now have a new set of standards to how projects are written. For example, 2 workflows are mandatory in every project: super-lint
and makefile
. CodeQL-analysis
is an optional must-have as well, but isn't available in all projects.
I have a system for workflows now being established. I use them to test if my software is working correctly, and what needs to be fixed. I am still very new to this, and I am learning the process. It is unlikely I will master the entire system by myself. Currently, if a project has JavaScript functionality, I will include workflows for various JavaScript environments, such as Grunt, Gulp, Node, Webpack, Deno, and others. This way, I can test to make sure cross-platform compliant JavaScript source code is being made. The super linter is used as a catch-all to lint any/all programming languages present. The makefile workflow is for testing the makefile at the root of every modern repository, and also other makefiles that maybe included.
Actions:
super-lint.yml
makefile.yml
Daylight savings time came into effect on Sunday 2021 November 7th at 2:00 am (when the time went back to 1 am) for users outside of North America/The United States, please factor that if I say 1 pm, I mean 12 pm. Yes, I hate this system too, it is ridiculous that it is still being used.
This section has been collapsed for readability. Click/tap here to expand/collapse this section.
Click/tap here to expand/collapse older entries
Click/tap here to expand/collapse this section
...Lets not go any further until you reach 200k
TODO: Translate status file into multiple languages using Bing Translate or DeepL proposed {2021:AugustsuguA:1202}
TODO: MIME and magic number for ScreenTeX, TeX support
All times are UTC-7 (PDT/Pacific Time)
You may need special rendering support for the <dropdown>
HTML tag being used in this document
Majority language is: English (EN_US) / Markdown / HTML5
Minority languages include: Russian (RU)
(To be translated: Esperanto
, Spanish
, Hindi
, Vietnamese
, Japanese
, Khmer
, etc.
)
Encoding: UTF-8
(with some Emojis, and some Unicode 13.0 characters, such as πͺ)
File type: Markdown document (*.md, *.mkd, *.mdown, *.markdown)
Line count (including blank lines and compiler line): 3,886
π Days until 2 year GitHub :octocat: anniversary: 139
(as of 2022 January 5th at 00:12:00 am to 11:59:59 pm)
:octocat: GitHub consecutive day count: 591
(As of 2022 January 5th at 00:12:00 am to 11:59:59 pm)
π§ Linux desktop consecutive day count: 546
(as of 2022 January 5th at 00:12:00 am to 11:59:59)
πͺ Windows 10 with GitHub consecutive day count: 45
(as of 2021 December 31st at 00:12:00 am to 11:59:59)
π§ Ubuntu 20.04 with GitHub consecutive day count: 546
(as of 2022 January 5th at 00:12:00 am to 11:59:59)
:atom: Total amount of original GitHub repositories: 1,655+o
(as of 2022 January 5th at 00:12:00 am to 11:59:59 pm)
I have noted that GitHub rounds up the total number of each statistic, so when something reaches 50 after the kilo point (once it reaches 1000) it rounds up to the next kilo, so 1050 would be 1100, 1150 would be 1200, and so on.
:atom: o=organizations, total number of non-fork organization repositories: 115
as of 2022 January 5th 00:12:00 am to 11:59:59 pm)
Organization repo count guide
Org repo (non-fork) count
Snap repos: 29 (formula: Org:Seanpm2001-snapcraft minus current.unforked minus 4) (verified count, as of July 21st 2021)
.github.io: 79 (80 when including seanpm2001/seanpm2001/github.io/) (formula: org:Seanpm2001-GitHub-Pages-Collection minus current.unforked minus 4) Verified count (as of July 9th 2021) unverified count (as of July 26th 2021)
Count verification needs to be re-checked - July 13th 2021 ((X1 Count verification needs to be re-checked - July 14th 2021 X2:: Count verification needs to be re-checked - July 15th 2021 X3:: Count verification needs to be re-checked - July 16th 2021 X4:: Count verification needs to be re-checked - July 17th 2021 X5)) No new data for this range, update count verification when ready
:electron: Repositories created so far this month: 31+o
(as of 2022 January 5th at 00:12:00 am to 11:59:59 pm)
:shipit: Organization count: 770
(as of 2022 January 5th at 00:12:00 am to 11:59:59 pm)
:electron: Organizations created so far this month: 10
(as of 2022 January 5th at 00:12:00 am to 11:59:59 pm)
I had a good day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date.
Today, I worked on GitHub organizations, and fell behind even further. I still have 8 days worth of organization work planned for when I get more caught up, I just really wanted to do it today.
Today, I started work on the BlazeOS operating system project, which has a similar scope to the WacOS operating system project. The major difference being WacOS is for Apple (company) emulation, and BlazeOS is for Amazon.com (company) emulation.
Early in the morning, I also started work on 2 additional projects: a new IDE known as Easy-E, another one I made for the brand name. Its name was inspired by the stage name of the former rapper Eazy-E. I have no affiliation with him though. I also began work on standardizing a new markup language I began defining last night that I am currently calling DroppedText-lang or DroTeX. It is a simple language for file categorization.
I tried harder to get caught up today, and still fell behind, including the status post that I skipped again today (not even writing the notes for it until 2022 January 10th, and not finalizing it until 2022 January 12th)
So far this year, the mistake of writing 2021 instead of 2022 has been extremely minimal.
I am working on transitioning the labeling of commits again, changing README.md - Didn't play
to README.md - No data
as I want it to be more professional. I am slowly starting to do this as of 2021 November 23rd. I am also looking for ways to make my daily desktop screenshots more interesting.
I have a new standard for issue archival today (2021 November 19th) now finally including labels, dates, and users.
I am in the adoption process of the GNU philosophy, and I am still currently trying to find my opinion on the "Linux" vs "GNU/Linux" debate.
I now have a new set of standards to how projects are written. For example, 2 workflows are mandatory in every project: super-lint
and makefile
. CodeQL-analysis
is an optional must-have as well, but isn't available in all projects.
I have a system for workflows now being established. I use them to test if my software is working correctly, and what needs to be fixed. I am still very new to this, and I am learning the process. It is unlikely I will master the entire system by myself. Currently, if a project has JavaScript functionality, I will include workflows for various JavaScript environments, such as Grunt, Gulp, Node, Webpack, Deno, and others. This way, I can test to make sure cross-platform compliant JavaScript source code is being made. The super linter is used as a catch-all to lint any/all programming languages present. The makefile workflow is for testing the makefile at the root of every modern repository, and also other makefiles that maybe included.
Actions:
super-lint.yml
makefile.yml
Daylight savings time came into effect on Sunday 2021 November 7th at 2:00 am (when the time went back to 1 am) for users outside of North America/The United States, please factor that if I say 1 pm, I mean 12 pm. Yes, I hate this system too, it is ridiculous that it is still being used.
This section has been collapsed for readability. Click/tap here to expand/collapse this section.
Click/tap here to expand/collapse older entries
Click/tap here to expand/collapse this section
...Lets not go any further until you reach 200k
TODO: Translate status file into multiple languages using Bing Translate or DeepL proposed {2021:AugustsuguA:1202}
TODO: MIME and magic number for ScreenTeX, TeX support
All times are UTC-7 (PDT/Pacific Time)
You may need special rendering support for the <dropdown>
HTML tag being used in this document
Majority language is: English (EN_US) / Markdown / HTML5
Minority languages include: Russian (RU)
(To be translated: Esperanto
, Spanish
, Hindi
, Vietnamese
, Japanese
, Khmer
, etc.
)
Encoding: UTF-8
(with some Emojis, and some Unicode 13.0 characters, such as πͺ)
File type: Markdown document (*.md, *.mkd, *.mdown, *.markdown)
Line count (including blank lines and compiler line): 3,910
π Days until 2 year GitHub :octocat: anniversary: 138
(as of 2022 January 6th at 00:12:00 am to 11:59:59 pm)
:octocat: GitHub consecutive day count: 592
(As of 2022 January 6th at 00:12:00 am to 11:59:59 pm)
π§ Linux desktop consecutive day count: 547
(as of 2022 January 6th at 00:12:00 am to 11:59:59)
πͺ Windows 10 with GitHub consecutive day count: 45
(as of 2021 July 9th at 00:12:00 am to 11:59:59)
π§ Ubuntu 20.04 with GitHub consecutive day count: 547
(as of 2022 January 6th at 00:12:00 am to 11:59:59)
:atom: Total amount of original GitHub repositories: 1,658+o
(as of 2022 January 6th at 00:12:00 am to 11:59:59 pm)
I have noted that GitHub rounds up the total number of each statistic, so when something reaches 50 after the kilo point (once it reaches 1000) it rounds up to the next kilo, so 1050 would be 1100, 1150 would be 1200, and so on.
:atom: o=organizations, total number of non-fork organization repositories: 115
as of 2022 January 6th 00:12:00 am to 11:59:59 pm)
Organization repo count guide
Org repo (non-fork) count
Snap repos: 29 (formula: Org:Seanpm2001-snapcraft minus current.unforked minus 4) (verified count, as of July 21st 2021)
.github.io: 79 (80 when including seanpm2001/seanpm2001/github.io/) (formula: org:Seanpm2001-GitHub-Pages-Collection minus current.unforked minus 4) Verified count (as of July 9th 2021) unverified count (as of July 26th 2021)
Count verification needs to be re-checked - July 13th 2021 ((X1 Count verification needs to be re-checked - July 14th 2021 X2:: Count verification needs to be re-checked - July 15th 2021 X3:: Count verification needs to be re-checked - July 16th 2021 X4:: Count verification needs to be re-checked - July 17th 2021 X5)) No new data for this range, update count verification when ready
:electron: Repositories created so far this month: 34+o
(as of 2022 January 6th at 00:12:00 am to 11:59:59 pm)
:shipit: Organization count: 770
(as of 2022 January 6th at 00:12:00 am to 11:59:59 pm)
:electron: Organizations created so far this month: 10
(as of 2022 January 6th at 00:12:00 am to 11:59:59 pm)
I had a good day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date.
Today, I worked on a massive update to the WacOS operating system project, where I did a massive README.md
file update, modernized the project, and archived some pull requests and other data. I tried to get more caught up today, but didn't make much progress. I also did the usual reduced work today.
My repository Its-time-to-cut-WideVine-DRM has received significant attention in the past month, it is now likely to stay my most popular project for a while, and it has been gaining 2-3 stars a day. Unfortunately, I may have thwarted the progress today. I went to check the traffic, as I was really curious as to why everyone was flocking here. I found that there were 16 searches for a CDM key (a key used to crack the WideVine DRM scheme) I had to put out a notice about it, as it could lead to this project becoming a danger to legal threats and attacks by G##gle. Plus, I can't just let people waste their time searching for something that doesn't exist, so I made a file that notes that the key doesn't exist in this project, and never will. I then linked to search queries for searching for a CDM key on your own, but didn't link to an individual project.
So far this year, the mistake of writing 2021 instead of 2022 has been extremely minimal.
I am working on transitioning the labeling of commits again, changing README.md - Didn't play
to README.md - No data
as I want it to be more professional. I am slowly starting to do this as of 2021 November 23rd. I am also looking for ways to make my daily desktop screenshots more interesting.
I have a new standard for issue archival today (2021 November 19th) now finally including labels, dates, and users.
I am in the adoption process of the GNU philosophy, and I am still currently trying to find my opinion on the "Linux" vs "GNU/Linux" debate.
I now have a new set of standards to how projects are written. For example, 2 workflows are mandatory in every project: super-lint
and makefile
. CodeQL-analysis
is an optional must-have as well, but isn't available in all projects.
I have a system for workflows now being established. I use them to test if my software is working correctly, and what needs to be fixed. I am still very new to this, and I am learning the process. It is unlikely I will master the entire system by myself. Currently, if a project has JavaScript functionality, I will include workflows for various JavaScript environments, such as Grunt, Gulp, Node, Webpack, Deno, and others. This way, I can test to make sure cross-platform compliant JavaScript source code is being made. The super linter is used as a catch-all to lint any/all programming languages present. The makefile workflow is for testing the makefile at the root of every modern repository, and also other makefiles that maybe included.
Actions:
super-lint.yml
makefile.yml
Daylight savings time came into effect on Sunday 2021 November 7th at 2:00 am (when the time went back to 1 am) for users outside of North America/The United States, please factor that if I say 1 pm, I mean 12 pm. Yes, I hate this system too, it is ridiculous that it is still being used.
This section has been collapsed for readability. Click/tap here to expand/collapse this section.
Click/tap here to expand/collapse older entries
Click/tap here to expand/collapse this section
...Lets not go any further until you reach 200k
TODO: Translate status file into multiple languages using Bing Translate or DeepL proposed {2021:AugustsuguA:1202}
TODO: MIME and magic number for ScreenTeX, TeX support
All times are UTC-7 (PDT/Pacific Time)
You may need special rendering support for the <dropdown>
HTML tag being used in this document
Majority language is: English (EN_US) / Markdown / HTML5
Minority languages include: Russian (RU)
(To be translated: Esperanto
, Spanish
, Hindi
, Vietnamese
, Japanese
, Khmer
, etc.
)
Encoding: UTF-8
(with some Emojis, and some Unicode 13.0 characters, such as πͺ)
File type: Markdown document (*.md, *.mkd, *.mdown, *.markdown)
Line count (including blank lines and compiler line): 3,920
π Days until 2 year GitHub :octocat: anniversary: 137
(as of 2022 January 7th at 00:12:00 am to 11:59:59 pm)
:octocat: GitHub consecutive day count: 593
(As of 2022 January 7th at 00:12:00 am to 11:59:59 pm)
π§ Linux desktop consecutive day count: 548
(as of 2022 January 7th at 00:12:00 am to 11:59:59)
πͺ Windows 10 with GitHub consecutive day count: 45
(as of 2021 July 9th at 00:12:00 am to 11:59:59)
π§ Ubuntu 20.04 with GitHub consecutive day count: 548
(as of 2022 January 7th at 00:12:00 am to 11:59:59)
:atom: Total amount of original GitHub repositories: 1,664+o
(as of 2022 January 7th at 00:12:00 am to 11:59:59 pm)
I have noted that GitHub rounds up the total number of each statistic, so when something reaches 50 after the kilo point (once it reaches 1000) it rounds up to the next kilo, so 1050 would be 1100, 1150 would be 1200, and so on.
:atom: o=organizations, total number of non-fork organization repositories: 115
as of 2022 January 7th 00:12:00 am to 11:59:59 pm)
Organization repo count guide
Org repo (non-fork) count
Snap repos: 29 (formula: Org:Seanpm2001-snapcraft minus current.unforked minus 4) (verified count, as of July 21st 2021)
.github.io: 79 (80 when including seanpm2001/seanpm2001/github.io/) (formula: org:Seanpm2001-GitHub-Pages-Collection minus current.unforked minus 4) Verified count (as of July 9th 2021) unverified count (as of July 26th 2021)
Count verification needs to be re-checked - July 13th 2021 ((X1 Count verification needs to be re-checked - July 14th 2021 X2:: Count verification needs to be re-checked - July 15th 2021 X3:: Count verification needs to be re-checked - July 16th 2021 X4:: Count verification needs to be re-checked - July 17th 2021 X5)) No new data for this range, update count verification when ready
:electron: Repositories created so far this month: 40+o
(as of 2022 January 7th at 00:12:00 am to 11:59:59 pm)
:shipit: Organization count: 770
(as of 2022 January 7th at 00:12:00 am to 11:59:59 pm)
:electron: Organizations created so far this month: 10
(as of 2022 January 7th at 00:12:00 am to 11:59:59 pm)
I had a poor day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date.
Today, I worked on the normal Git-image work, along with some work to my GitHub profile. In the evening I tried to get caught up, but I got to experience something new tonight, which used a lot of time. I got to set up my new Raspberry Pi 4. I spent lots of time on this, and wrote a blog for it. I continued to fall behind, and I stayed up really late trying to catch up, but didn't get too far. I was dealing with low productivity today.
So far this year, the mistake of writing 2021 instead of 2022 has been extremely minimal.
I am working on transitioning the labeling of commits again, changing README.md - Didn't play
to README.md - No data
as I want it to be more professional. I am slowly starting to do this as of 2021 November 23rd. I am also looking for ways to make my daily desktop screenshots more interesting.
I have a new standard for issue archival today (2021 November 19th) now finally including labels, dates, and users.
I am in the adoption process of the GNU philosophy, and I am still currently trying to find my opinion on the "Linux" vs "GNU/Linux" debate.
I now have a new set of standards to how projects are written. For example, 2 workflows are mandatory in every project: super-lint
and makefile
. CodeQL-analysis
is an optional must-have as well, but isn't available in all projects.
I have a system for workflows now being established. I use them to test if my software is working correctly, and what needs to be fixed. I am still very new to this, and I am learning the process. It is unlikely I will master the entire system by myself. Currently, if a project has JavaScript functionality, I will include workflows for various JavaScript environments, such as Grunt, Gulp, Node, Webpack, Deno, and others. This way, I can test to make sure cross-platform compliant JavaScript source code is being made. The super linter is used as a catch-all to lint any/all programming languages present. The makefile workflow is for testing the makefile at the root of every modern repository, and also other makefiles that maybe included.
Actions:
super-lint.yml
makefile.yml
Daylight savings time came into effect on Sunday 2021 November 7th at 2:00 am (when the time went back to 1 am) for users outside of North America/The United States, please factor that if I say 1 pm, I mean 12 pm. Yes, I hate this system too, it is ridiculous that it is still being used.
This section has been collapsed for readability. Click/tap here to expand/collapse this section.
Click/tap here to expand/collapse older entries
Click/tap here to expand/collapse this section
...Lets not go any further until you reach 200k
TODO: Translate status file into multiple languages using Bing Translate or DeepL proposed {2021:AugustsuguA:1202}
TODO: MIME and magic number for ScreenTeX, TeX support
All times are UTC-7 (PDT/Pacific Time)
You may need special rendering support for the <dropdown>
HTML tag being used in this document
Majority language is: English (EN_US) / Markdown / HTML5
Minority languages include: Russian (RU)
(To be translated: Esperanto
, Spanish
, Hindi
, Vietnamese
, Japanese
, Khmer
, etc.
)
Encoding: UTF-8
(with some Emojis, and some Unicode 13.0 characters, such as πͺ)
File type: Markdown document (*.md, *.mkd, *.mdown, *.markdown)
Line count (including blank lines and compiler line): 3,936
π Days until 2 year GitHub :octocat: anniversary: 135
(as of 2022 January 8th at 00:12:00 am to 11:59:59 pm)
:octocat: GitHub consecutive day count: 594
(As of 2022 January 8th at 00:12:00 am to 11:59:59 pm)
π§ Linux desktop consecutive day count: 549
(as of 2022 January 8th at 00:12:00 am to 11:59:59)
πͺ Windows 10 with GitHub consecutive day count: 45
(as of 2021 July 9th at 00:12:00 am to 11:59:59)
π§ Ubuntu 20.04 with GitHub consecutive day count: 549
(as of 2022 January 8th at 00:12:00 am to 11:59:59)
:atom: Total amount of original GitHub repositories: 1,665+o
(as of 2022 January 8th at 00:12:00 am to 11:59:59 pm)
I have noted that GitHub rounds up the total number of each statistic, so when something reaches 50 after the kilo point (once it reaches 1000) it rounds up to the next kilo, so 1050 would be 1100, 1150 would be 1200, and so on.
:atom: o=organizations, total number of non-fork organization repositories: 115
as of 2022 January 8th 00:12:00 am to 11:59:59 pm)
Organization repo count guide
Org repo (non-fork) count
Snap repos: 29 (formula: Org:Seanpm2001-snapcraft minus current.unforked minus 4) (verified count, as of July 21st 2021)
.github.io: 79 (80 when including seanpm2001/seanpm2001/github.io/) (formula: org:Seanpm2001-GitHub-Pages-Collection minus current.unforked minus 4) Verified count (as of July 9th 2021) unverified count (as of July 26th 2021)
Count verification needs to be re-checked - July 13th 2021 ((X1 Count verification needs to be re-checked - July 14th 2021 X2:: Count verification needs to be re-checked - July 15th 2021 X3:: Count verification needs to be re-checked - July 16th 2021 X4:: Count verification needs to be re-checked - July 17th 2021 X5)) No new data for this range, update count verification when ready
:electron: Repositories created so far this month: 41+o
(as of 2022 January 8th at 00:12:00 am to 11:59:59 pm)
:shipit: Organization count: 770
(as of 2022 January 8th at 00:12:00 am to 11:59:59 pm)
:electron: Organizations created so far this month: 10
(as of 2022 January 8th at 00:12:00 am to 11:59:59 pm)
I had a decent day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date.
Today, I worked on the BlazeOS operating system project a lot. I wrote a ton of ideas down, including the IgniteBook platform, which is a subsystem to emulate the Amazon Kindle Fire. I began work on a MOBI file reader called Mobi Dick (named after the book) and I also included a copy of the book as one of the 10 default books for the platform (since it is public domain and it is a classic) I made some project language files, created the Blazed CafΓ© Java UI library, created the ePubStation EPUB file reader, and created the bPage animation library.
With all this progress on 1 task, I fell behind further on my catchup process. I also continued to setup my Raspberry Pi today, and worked additionally on trying to get more caught up.
So far this year, the mistake of writing 2021 instead of 2022 has been extremely minimal.
I am working on transitioning the labeling of commits again, changing README.md - Didn't play
to README.md - No data
as I want it to be more professional. I am slowly starting to do this as of 2021 November 23rd. I am also looking for ways to make my daily desktop screenshots more interesting.
I have a new standard for issue archival today (2021 November 19th) now finally including labels, dates, and users.
I am in the adoption process of the GNU philosophy, and I am still currently trying to find my opinion on the "Linux" vs "GNU/Linux" debate.
I now have a new set of standards to how projects are written. For example, 2 workflows are mandatory in every project: super-lint
and makefile
. CodeQL-analysis
is an optional must-have as well, but isn't available in all projects.
I have a system for workflows now being established. I use them to test if my software is working correctly, and what needs to be fixed. I am still very new to this, and I am learning the process. It is unlikely I will master the entire system by myself. Currently, if a project has JavaScript functionality, I will include workflows for various JavaScript environments, such as Grunt, Gulp, Node, Webpack, Deno, and others. This way, I can test to make sure cross-platform compliant JavaScript source code is being made. The super linter is used as a catch-all to lint any/all programming languages present. The makefile workflow is for testing the makefile at the root of every modern repository, and also other makefiles that maybe included.
Actions:
super-lint.yml
makefile.yml
Daylight savings time came into effect on Sunday 2021 November 7th at 2:00 am (when the time went back to 1 am) for users outside of North America/The United States, please factor that if I say 1 pm, I mean 12 pm. Yes, I hate this system too, it is ridiculous that it is still being used.
This section has been collapsed for readability. Click/tap here to expand/collapse this section.
Click/tap here to expand/collapse older entries
Click/tap here to expand/collapse this section
...Lets not go any further until you reach 200k
TODO: Translate status file into multiple languages using Bing Translate or DeepL proposed {2021:AugustsuguA:1202}
TODO: MIME and magic number for ScreenTeX, TeX support
All times are UTC-7 (PDT/Pacific Time)
You may need special rendering support for the <dropdown>
HTML tag being used in this document
Majority language is: English (EN_US) / Markdown / HTML5
Minority languages include: Russian (RU)
(To be translated: Esperanto
, Spanish
, Hindi
, Vietnamese
, Japanese
, Khmer
, etc.
)
Encoding: UTF-8
(with some Emojis, and some Unicode 13.0 characters, such as πͺ)
File type: Markdown document (*.md, *.mkd, *.mdown, *.markdown)
Line count (including blank lines and compiler line): 3,904
π Days until 2 year GitHub :octocat: anniversary: 134
(as of 2022 January 9th at 00:12:00 am to 11:59:59 pm)
:octocat: GitHub consecutive day count: 595
(As of 2022 January 9th at 00:12:00 am to 11:59:59 pm)
π§ Linux desktop consecutive day count: 550
(as of 2022 January 9th at 00:12:00 am to 11:59:59)
πͺ Windows 10 with GitHub consecutive day count: 45
(as of 2021 July 9th at 00:12:00 am to 11:59:59)
π§ Ubuntu 20.04 with GitHub consecutive day count: 550
(as of 2022 January 9th at 00:12:00 am to 11:59:59)
:atom: Total amount of original GitHub repositories: 1,665+o
(as of 2022 January 9th at 00:12:00 am to 11:59:59 pm)
I have noted that GitHub rounds up the total number of each statistic, so when something reaches 50 after the kilo point (once it reaches 1000) it rounds up to the next kilo, so 1050 would be 1100, 1150 would be 1200, and so on.
:atom: o=organizations, total number of non-fork organization repositories: 115
as of 2022 January 9th 00:12:00 am to 11:59:59 pm)
Organization repo count guide
Org repo (non-fork) count
Snap repos: 29 (formula: Org:Seanpm2001-snapcraft minus current.unforked minus 4) (verified count, as of July 21st 2021)
.github.io: 79 (80 when including seanpm2001/seanpm2001/github.io/) (formula: org:Seanpm2001-GitHub-Pages-Collection minus current.unforked minus 4) Verified count (as of July 9th 2021) unverified count (as of July 26th 2021)
Count verification needs to be re-checked - July 13th 2021 ((X1 Count verification needs to be re-checked - July 14th 2021 X2:: Count verification needs to be re-checked - July 15th 2021 X3:: Count verification needs to be re-checked - July 16th 2021 X4:: Count verification needs to be re-checked - July 17th 2021 X5)) No new data for this range, update count verification when ready
:electron: Repositories created so far this month: 53+o
(as of 2022 January 9th at 00:12:00 am to 11:59:59 pm)
:shipit: Organization count: 770
(as of 2022 January 9th at 00:12:00 am to 11:59:59 pm)
:electron: Organizations created so far this month: 10
(as of 2022 January 9th at 00:12:00 am to 11:59:59 pm)
I had a good day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date.
Today, I worked on the BlazeOS operating system project a lot. I made separate copies of all the sub-projects into their own 10 repositories. I also created 2 repositories that I have plans for that are still held off. I continued to fall behind today.
I did not use my Raspberry Pi at all today. I also have begun to deal with severe down key issues on my laptop, which is the start of the very end of this keyboard (it has been getting significantly worse)
So far this year, the mistake of writing 2021 instead of 2022 has been extremely minimal.
I am working on transitioning the labeling of commits again, changing README.md - Didn't play
to README.md - No data
as I want it to be more professional. I am slowly starting to do this as of 2021 November 23rd. I am also looking for ways to make my daily desktop screenshots more interesting.
I have a new standard for issue archival today (2021 November 19th) now finally including labels, dates, and users.
I am in the adoption process of the GNU philosophy, and I am still currently trying to find my opinion on the "Linux" vs "GNU/Linux" debate.
I now have a new set of standards to how projects are written. For example, 2 workflows are mandatory in every project: super-lint
and makefile
. CodeQL-analysis
is an optional must-have as well, but isn't available in all projects.
I have a system for workflows now being established. I use them to test if my software is working correctly, and what needs to be fixed. I am still very new to this, and I am learning the process. It is unlikely I will master the entire system by myself. Currently, if a project has JavaScript functionality, I will include workflows for various JavaScript environments, such as Grunt, Gulp, Node, Webpack, Deno, and others. This way, I can test to make sure cross-platform compliant JavaScript source code is being made. The super linter is used as a catch-all to lint any/all programming languages present. The makefile workflow is for testing the makefile at the root of every modern repository, and also other makefiles that maybe included.
Actions:
super-lint.yml
makefile.yml
Daylight savings time came into effect on Sunday 2021 November 7th at 2:00 am (when the time went back to 1 am) for users outside of North America/The United States, please factor that if I say 1 pm, I mean 12 pm. Yes, I hate this system too, it is ridiculous that it is still being used.
This section has been collapsed for readability. Click/tap here to expand/collapse this section.
Click/tap here to expand/collapse older entries
Click/tap here to expand/collapse this section
...Lets not go any further until you reach 200k
TODO: Translate status file into multiple languages using Bing Translate or DeepL proposed {2021:AugustsuguA:1202}
TODO: MIME and magic number for ScreenTeX, TeX support
All times are UTC-7 (PDT/Pacific Time)
You may need special rendering support for the <dropdown>
HTML tag being used in this document
Majority language is: English (EN_US) / Markdown / HTML5
Minority languages include: Russian (RU)
(To be translated: Esperanto
, Spanish
, Hindi
, Vietnamese
, Japanese
, Khmer
, etc.
)
Encoding: UTF-8
(with some Emojis, and some Unicode 13.0 characters, such as πͺ)
File type: Markdown document (*.md, *.mkd, *.mdown, *.markdown)
Line count (including blank lines and compiler line): 3,929
π Days until 2 year GitHub :octocat: anniversary: 133
(as of 2022 January 10th at 00:12:00 am to 11:59:59 pm)
:octocat: GitHub consecutive day count: 596
(As of 2022 January 10th at 00:12:00 am to 11:59:59 pm)
π§ Linux desktop consecutive day count: 551
(as of 2022 January 10th at 00:12:00 am to 11:59:59)
πͺ Windows 10 with GitHub consecutive day count: 45
(as of 2021 July 9th at 00:12:00 am to 11:59:59)
π§ Ubuntu 20.04 with GitHub consecutive day count: 551
(as of 2022 January 10th at 00:12:00 am to 11:59:59)
:atom: Total amount of original GitHub repositories: 1,667+o
(as of 2022 January 10th at 00:12:00 am to 11:59:59 pm)
I have noted that GitHub rounds up the total number of each statistic, so when something reaches 50 after the kilo point (once it reaches 1000) it rounds up to the next kilo, so 1050 would be 1100, 1150 would be 1200, and so on.
:atom: o=organizations, total number of non-fork organization repositories: 115
as of 2022 January 10th 00:12:00 am to 11:59:59 pm)
Organization repo count guide
Org repo (non-fork) count
Snap repos: 29 (formula: Org:Seanpm2001-snapcraft minus current.unforked minus 4) (verified count, as of July 21st 2021)
.github.io: 79 (80 when including seanpm2001/seanpm2001/github.io/) (formula: org:Seanpm2001-GitHub-Pages-Collection minus current.unforked minus 4) Verified count (as of July 9th 2021) unverified count (as of July 26th 2021)
Count verification needs to be re-checked - July 13th 2021 ((X1 Count verification needs to be re-checked - July 14th 2021 X2:: Count verification needs to be re-checked - July 15th 2021 X3:: Count verification needs to be re-checked - July 16th 2021 X4:: Count verification needs to be re-checked - July 17th 2021 X5)) No new data for this range, update count verification when ready
:electron: Repositories created so far this month: 55+o
(as of 2022 January 10th at 00:12:00 am to 11:59:59 pm)
:shipit: Organization count: 770
(as of 2022 January 10th at 00:12:00 am to 11:59:59 pm)
:electron: Organizations created so far this month: 10
(as of 2022 January 10th at 00:12:00 am to 11:59:59 pm)
I had a difficult day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date.
Today, I worked on trying to take better care of myself, as I have been struggling with self care lately. I have been also dealing with immense keyboard difficulties and failures. This laptop is finally going.
Today on GitHub, I worked on the DeGoogle-your-Life source project, the BlazeOS project, the GOI project, and the WacOS project. I was just trying to stay caught up on these, and get them more up to date.
I had several appointments today, and afterwards, I spent time trying to get caught up, as I am currently 14 days behind on work. I skipped Tree World uploads today, as I didn't have enough storage or time.
I have started to use my own file formats in notes lately, such as DroTeX and URLL. They are really useful formats. I am not ready to admit that I have a problem yet, as I don't see it as a problem (the 14 days of work and the 2000+ projects) as part of appointment discussion, I have a new set bedtime and mental health, maximum of 10 minutes of screen time after 11:00 pm, go to bed immediately after (It didn't work out every day this week)
So far this year, the mistake of writing 2021 instead of 2022 has been extremely minimal.
I am working on transitioning the labeling of commits again, changing README.md - Didn't play
to README.md - No data
as I want it to be more professional. I am slowly starting to do this as of 2021 November 23rd. I am also looking for ways to make my daily desktop screenshots more interesting.
I have a new standard for issue archival today (2021 November 19th) now finally including labels, dates, and users.
I am in the adoption process of the GNU philosophy, and I am still currently trying to find my opinion on the "Linux" vs "GNU/Linux" debate.
I now have a new set of standards to how projects are written. For example, 2 workflows are mandatory in every project: super-lint
and makefile
. CodeQL-analysis
is an optional must-have as well, but isn't available in all projects.
I have a system for workflows now being established. I use them to test if my software is working correctly, and what needs to be fixed. I am still very new to this, and I am learning the process. It is unlikely I will master the entire system by myself. Currently, if a project has JavaScript functionality, I will include workflows for various JavaScript environments, such as Grunt, Gulp, Node, Webpack, Deno, and others. This way, I can test to make sure cross-platform compliant JavaScript source code is being made. The super linter is used as a catch-all to lint any/all programming languages present. The makefile workflow is for testing the makefile at the root of every modern repository, and also other makefiles that maybe included.
Actions:
super-lint.yml
makefile.yml
Daylight savings time came into effect on Sunday 2021 November 7th at 2:00 am (when the time went back to 1 am) for users outside of North America/The United States, please factor that if I say 1 pm, I mean 12 pm. Yes, I hate this system too, it is ridiculous that it is still being used.
This section has been collapsed for readability. Click/tap here to expand/collapse this section.
Click/tap here to expand/collapse older entries
Click/tap here to expand/collapse this section
...Lets not go any further until you reach 200k
TODO: Translate status file into multiple languages using Bing Translate or DeepL proposed {2021:AugustsuguA:1202}
TODO: MIME and magic number for ScreenTeX, TeX support
All times are UTC-7 (PDT/Pacific Time)
You may need special rendering support for the <dropdown>
HTML tag being used in this document
Majority language is: English (EN_US) / Markdown / HTML5
Minority languages include: Russian (RU)
(To be translated: Esperanto
, Spanish
, Hindi
, Vietnamese
, Japanese
, Khmer
, etc.
)
Encoding: UTF-8
(with some Emojis, and some Unicode 13.0 characters, such as πͺ)
File type: Markdown document (*.md, *.mkd, *.mdown, *.markdown)
Line count (including blank lines and compiler line): 3,949
π Days until 2 year GitHub :octocat: anniversary: 132
(as of 2022 January 11th at 00:12:00 am to 11:59:59 pm)
:octocat: GitHub consecutive day count: 597
(As of 2022 January 11th at 00:12:00 am to 11:59:59 pm)
π§ Linux desktop consecutive day count: 552
(as of 2022 January 11th at 00:12:00 am to 11:59:59)
πͺ Windows 10 with GitHub consecutive day count: 45
(as of 2021 July 9th at 00:12:00 am to 11:59:59)
π§ Ubuntu 20.04 with GitHub consecutive day count: 552
(as of 2022 January 11th at 00:12:00 am to 11:59:59)
:atom: Total amount of original GitHub repositories: 1,668+o/1680+o
(as of 2022 January 11th at 00:12:00 am to 11:59:59 pm)
I have noted that GitHub rounds up the total number of each statistic, so when something reaches 50 after the kilo point (once it reaches 1000) it rounds up to the next kilo, so 1050 would be 1100, 1150 would be 1200, and so on.
:atom: o=organizations, total number of non-fork organization repositories: 115
as of 2022 January 11th 00:12:00 am to 11:59:59 pm)
Organization repo count guide
Org repo (non-fork) count
Snap repos: 29 (formula: Org:Seanpm2001-snapcraft minus current.unforked minus 4) (verified count, as of July 21st 2021)
.github.io: 79 (80 when including seanpm2001/seanpm2001/github.io/) (formula: org:Seanpm2001-GitHub-Pages-Collection minus current.unforked minus 4) Verified count (as of July 9th 2021) unverified count (as of July 26th 2021)
Count verification needs to be re-checked - July 13th 2021 ((X1 Count verification needs to be re-checked - July 14th 2021 X2:: Count verification needs to be re-checked - July 15th 2021 X3:: Count verification needs to be re-checked - July 16th 2021 X4:: Count verification needs to be re-checked - July 17th 2021 X5)) No new data for this range, update count verification when ready
:electron: Repositories created so far this month: 56+o
(as of 2022 January 11th at 00:12:00 am to 11:59:59 pm)
:shipit: Organization count: 770
(as of 2022 January 11th at 00:12:00 am to 11:59:59 pm)
:electron: Organizations created so far this month: 10
(as of 2022 January 11th at 00:12:00 am to 11:59:59 pm)
I had a difficult day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date.
Today, I worked on my V8 template a bit, creating a branch for monthly tree world projects. This is the start of a plan to branch out for smaller project types. I did some catchup work today, but spent a very long amount of time playing the video game Tree World, as I was addicted today. I partially resumed Git-image work. Today, I also worked on the Boom Bay video game project, as I recently had some ideas for it, and I have been having a growing itch to program in LISP/Scheme, despite a damaged keyboard.
Today, I also worked briefly on the Team8Collection project, and my audio database. At the end of the day, I started a small project to archive a small project I found when cleaning my laptop, an un-uploaded Robot project that has work put into it. It was dubbed My robot friend
but for originality, I added ARCHIVE_
to the original name. It is written in C++11 and Scratch 2.
I have started to use my own file formats in notes lately, such as DroTeX and URLL. They are really useful formats, also, so far this year, the mistake of writing 2021 instead of 2022 has been extremely minimal.
I am working on transitioning the labeling of commits again, changing README.md - Didn't play
to README.md - No data
as I want it to be more professional. I am slowly starting to do this as of 2021 November 23rd. I am also looking for ways to make my daily desktop screenshots more interesting.
I have a new standard for issue archival today (2021 November 19th) now finally including labels, dates, and users.
I am in the adoption process of the GNU philosophy, and I am still currently trying to find my opinion on the "Linux" vs "GNU/Linux" debate.
I now have a new set of standards to how projects are written. For example, 2 workflows are mandatory in every project: super-lint
and makefile
. CodeQL-analysis
is an optional must-have as well, but isn't available in all projects.
I have a system for workflows now being established. I use them to test if my software is working correctly, and what needs to be fixed. I am still very new to this, and I am learning the process. It is unlikely I will master the entire system by myself. Currently, if a project has JavaScript functionality, I will include workflows for various JavaScript environments, such as Grunt, Gulp, Node, Webpack, Deno, and others. This way, I can test to make sure cross-platform compliant JavaScript source code is being made. The super linter is used as a catch-all to lint any/all programming languages present. The makefile workflow is for testing the makefile at the root of every modern repository, and also other makefiles that maybe included.
Actions:
super-lint.yml
makefile.yml
Daylight savings time came into effect on Sunday 2021 November 7th at 2:00 am (when the time went back to 1 am) for users outside of North America/The United States, please factor that if I say 1 pm, I mean 12 pm. Yes, I hate this system too, it is ridiculous that it is still being used.
This section has been collapsed for readability. Click/tap here to expand/collapse this section.
Click/tap here to expand/collapse older entries
Click/tap here to expand/collapse this section
...Lets not go any further until you reach 200k
TODO: Translate status file into multiple languages using Bing Translate or DeepL proposed {2021:AugustsuguA:1202}
TODO: MIME and magic number for ScreenTeX, TeX support
All times are UTC-7 (PDT/Pacific Time)
You may need special rendering support for the <dropdown>
HTML tag being used in this document
Majority language is: English (EN_US) / Markdown / HTML5
Minority languages include: Russian (RU)
(To be translated: Esperanto
, Spanish
, Hindi
, Vietnamese
, Japanese
, Khmer
, etc.
)
Encoding: UTF-8
(with some Emojis, and some Unicode 13.0 characters, such as πͺ)
File type: Markdown document (*.md, *.mkd, *.mdown, *.markdown)
Line count (including blank lines and compiler line): 3,959
π Days until 2 year GitHub :octocat: anniversary: 131
(as of 2022 January 12th at 00:12:00 am to 11:59:59 pm)
:octocat: GitHub consecutive day count: 598
(As of 2022 January 12th at 00:12:00 am to 11:59:59 pm)
π§ Linux desktop consecutive day count: 553
(as of 2022 January 12th at 00:12:00 am to 11:59:59)
πͺ Windows 10 with GitHub consecutive day count: 45
(as of 2021 July 9th at 00:12:00 am to 11:59:59)
π§ Ubuntu 20.04 with GitHub consecutive day count: 553
(as of 2022 January 12th at 00:12:00 am to 11:59:59)
:atom: Total amount of original GitHub repositories: 1,669+o/1681+o
(as of 2022 January 12th at 00:12:00 am to 11:59:59 pm)
I have noted that GitHub rounds up the total number of each statistic, so when something reaches 50 after the kilo point (once it reaches 1000) it rounds up to the next kilo, so 1050 would be 1100, 1150 would be 1200, and so on.
:atom: o=organizations, total number of non-fork organization repositories: 115
as of 2022 January 12th 00:12:00 am to 11:59:59 pm)
Organization repo count guide
Org repo (non-fork) count
Snap repos: 29 (formula: Org:Seanpm2001-snapcraft minus current.unforked minus 4) (verified count, as of July 21st 2021)
.github.io: 79 (80 when including seanpm2001/seanpm2001/github.io/) (formula: org:Seanpm2001-GitHub-Pages-Collection minus current.unforked minus 4) Verified count (as of July 9th 2021) unverified count (as of July 26th 2021)
Count verification needs to be re-checked - July 13th 2021 ((X1 Count verification needs to be re-checked - July 14th 2021 X2:: Count verification needs to be re-checked - July 15th 2021 X3:: Count verification needs to be re-checked - July 16th 2021 X4:: Count verification needs to be re-checked - July 17th 2021 X5)) No new data for this range, update count verification when ready
:electron: Repositories created so far this month: 57+o
(as of 2022 January 12th at 00:12:00 am to 11:59:59 pm)
:shipit: Organization count: 770
(as of 2022 January 12th at 00:12:00 am to 11:59:59 pm)
:electron: Organizations created so far this month: 10
(as of 2022 January 12th at 00:12:00 am to 11:59:59 pm)
I had a difficult day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date.
Today, I worked on various tasks, including catching up on status files. I completed the status posts for January 1st to January 5th, and wrote notes for the January 7th and 12th entries. I got caught up on activity file work, and did lots of file sorting, and clearing already-backed-up unneeded files from my laptop, as I am low on space. I plan on doing a hard drive backup later on this weekend. I tried to force myself to have an earlier bedtime tonight, but it failed.
I also finalized the upload and configuration of the miniature robot project I found last night. Now knowing that it contains Scratch data, I found some scrathics (Graphics made in Scratch) and made a repository for my scrathics. I got my audio database up to date, along with a few other projects, did some work on the AudiBass manager software project, and did the usual (but limited) Git-image work.
I have started to use my own file formats in notes lately, such as DroTeX and URLL. They are really useful formats, also, so far this year, the mistake of writing 2021 instead of 2022 has been extremely minimal.
I am working on transitioning the labeling of commits again, changing README.md - Didn't play
to README.md - No data
as I want it to be more professional. I am slowly starting to do this as of 2021 November 23rd. I am also looking for ways to make my daily desktop screenshots more interesting.
I have a new standard for issue archival today (2021 November 19th) now finally including labels, dates, and users.
I am in the adoption process of the GNU philosophy, and I am still currently trying to find my opinion on the "Linux" vs "GNU/Linux" debate.
I now have a new set of standards to how projects are written. For example, 2 workflows are mandatory in every project: super-lint
and makefile
. CodeQL-analysis
is an optional must-have as well, but isn't available in all projects.
I have a system for workflows now being established. I use them to test if my software is working correctly, and what needs to be fixed. I am still very new to this, and I am learning the process. It is unlikely I will master the entire system by myself. Currently, if a project has JavaScript functionality, I will include workflows for various JavaScript environments, such as Grunt, Gulp, Node, Webpack, Deno, and others. This way, I can test to make sure cross-platform compliant JavaScript source code is being made. The super linter is used as a catch-all to lint any/all programming languages present. The makefile workflow is for testing the makefile at the root of every modern repository, and also other makefiles that maybe included.
Actions:
super-lint.yml
makefile.yml
Daylight savings time came into effect on Sunday 2021 November 7th at 2:00 am (when the time went back to 1 am) for users outside of North America/The United States, please factor that if I say 1 pm, I mean 12 pm. Yes, I hate this system too, it is ridiculous that it is still being used.
This section has been collapsed for readability. Click/tap here to expand/collapse this section.
Click/tap here to expand/collapse older entries
Click/tap here to expand/collapse this section
...Lets not go any further until you reach 200k
TODO: Translate status file into multiple languages using Bing Translate or DeepL proposed {2021:AugustsuguA:1202}
TODO: MIME and magic number for ScreenTeX, TeX support
All times are UTC-7 (PDT/Pacific Time)
You may need special rendering support for the <dropdown>
HTML tag being used in this document
Majority language is: English (EN_US) / Markdown / HTML5
Minority languages include: Russian (RU)
(To be translated: Esperanto
, Spanish
, Hindi
, Vietnamese
, Japanese
, Khmer
, etc.
)
Encoding: UTF-8
(with some Emojis, and some Unicode 13.0 characters, such as πͺ)
File type: Markdown document (*.md, *.mkd, *.mdown, *.markdown)
Line count (including blank lines and compiler line): 3,975
π Days until 2 year GitHub :octocat: anniversary: 130
(as of 2022 January 13th at 00:12:00 am to 11:59:59 pm)
:octocat: GitHub consecutive day count: 599
(As of 2022 January 13th at 00:12:00 am to 11:59:59 pm)
π§ Linux desktop consecutive day count: 554
(as of 2022 January 13th at 00:12:00 am to 11:59:59)
πͺ Windows 10 with GitHub consecutive day count: 45
(as of 2020 July 9th at 00:12:00 am to 11:59:59)
π§ Ubuntu 20.04 with GitHub consecutive day count: 554
(as of 2022 January 13th at 00:12:00 am to 11:59:59)
:atom: Total amount of original GitHub repositories: 1,669+o/1681+o
(as of 2022 January 13th at 00:12:00 am to 11:59:59 pm)
I have noted that GitHub rounds up the total number of each statistic, so when something reaches 50 after the kilo point (once it reaches 1000) it rounds up to the next kilo, so 1050 would be 1100, 1150 would be 1200, and so on.
:atom: o=organizations, total number of non-fork organization repositories: 115
as of 2022 January 13th 00:12:00 am to 11:59:59 pm)
Organization repo count guide
Org repo (non-fork) count
Snap repos: 29 (formula: Org:Seanpm2001-snapcraft minus current.unforked minus 4) (verified count, as of July 21st 2021)
.github.io: 79 (80 when including seanpm2001/seanpm2001/github.io/) (formula: org:Seanpm2001-GitHub-Pages-Collection minus current.unforked minus 4) Verified count (as of July 9th 2021) unverified count (as of July 26th 2021)
Count verification needs to be re-checked - July 13th 2021 ((X1 Count verification needs to be re-checked - July 14th 2021 X2:: Count verification needs to be re-checked - July 15th 2021 X3:: Count verification needs to be re-checked - July 16th 2021 X4:: Count verification needs to be re-checked - July 17th 2021 X5)) No new data for this range, update count verification when ready
:electron: Repositories created so far this month: 57+o
(as of 2022 January 13th at 00:12:00 am to 11:59:59 pm)
:shipit: Organization count: 770
(as of 2022 January 13th at 00:12:00 am to 11:59:59 pm)
:electron: Organizations created so far this month: 10
(as of 2022 January 13th at 00:12:00 am to 11:59:59 pm)
I had a better day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date.
Today, I worked on various tasks, including catching up on status files, which I made significant progress on. My laptops keyboard has been on a severe decline, for whatever reason, only the numberpad remains the biggest issue [0-9] which includes parentheses, asterisk, exclamation point, at sign, pound sign, dollar sign, percent sign, carot marker, and ampersand. It has really been difficult, and I plan to switch over to the Raspberry Pi soon to get this laptops keyboard fixed for a second time. The number keys have been repeating a lot, pressing 2 to 3 times per press, and it has been a tedious problem to mitigate.
Today, I spent a lot of time working on WacOS, specifically Man pages (manual pages) for the project. I also worked on the usual Git-image projects today, along with my Raspberry Pi blog.
I also finalized the upload and configuration of the miniature robot project I found last night. Now knowing that it contains Scratch data, I found some scrathics (Graphics made in Scratch) and made a repository for my scrathics. I got my audio database up to date, along with a few other projects, did some work on the AudiBass manager software project, and did the usual (but limited) Git-image work.
I have started to use my own file formats in notes lately, such as DroTeX and URLL. They are really useful formats, also, so far this year, the mistake of writing 2021 instead of 2022 has been extremely minimal.
I am working on transitioning the labeling of commits again, changing README.md - Didn't play
to README.md - No data
as I want it to be more professional. I am slowly starting to do this as of 2021 November 23rd. I am also looking for ways to make my daily desktop screenshots more interesting.
I have a new standard for issue archival today (2021 November 19th) now finally including labels, dates, and users.
I am in the adoption process of the GNU philosophy, and I am still currently trying to find my opinion on the "Linux" vs "GNU/Linux" debate.
I now have a new set of standards to how projects are written. For example, 2 workflows are mandatory in every project: super-lint
and makefile
. CodeQL-analysis
is an optional must-have as well, but isn't available in all projects.
I have a system for workflows now being established. I use them to test if my software is working correctly, and what needs to be fixed. I am still very new to this, and I am learning the process. It is unlikely I will master the entire system by myself. Currently, if a project has JavaScript functionality, I will include workflows for various JavaScript environments, such as Grunt, Gulp, Node, Webpack, Deno, and others. This way, I can test to make sure cross-platform compliant JavaScript source code is being made. The super linter is used as a catch-all to lint any/all programming languages present. The makefile workflow is for testing the makefile at the root of every modern repository, and also other makefiles that maybe included.
Actions:
super-lint.yml
makefile.yml
Daylight savings time came into effect on Sunday 2021 November 7th at 2:00 am (when the time went back to 1 am) for users outside of North America/The United States, please factor that if I say 1 pm, I mean 12 pm. Yes, I hate this system too, it is ridiculous that it is still being used.
This section has been collapsed for readability. Click/tap here to expand/collapse this section.
Click/tap here to expand/collapse older entries
Click/tap here to expand/collapse this section
...Lets not go any further until you reach 200k
TODO: Translate status file into multiple languages using Bing Translate or DeepL proposed {2021:AugustsuguA:1202}
TODO: MIME and magic number for ScreenTeX, TeX support
All times are UTC-7 (PDT/Pacific Time)
You may need special rendering support for the <dropdown>
HTML tag being used in this document
Majority language is: English (EN_US) / Markdown / HTML5
Minority languages include: Russian (RU)
(To be translated: Esperanto
, Spanish
, Hindi
, Vietnamese
, Japanese
, Khmer
, etc.
)
Encoding: UTF-8
(with some Emojis, and some Unicode 13.0 characters, such as πͺ)
File type: Markdown document (*.md, *.mkd, *.mdown, *.markdown)
Line count (including blank lines and compiler line): 3,985
I had a decent day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date.
Today, I worked mainly on the WacOS project, along with basic Git-image work and daily Git-image work. I have still not gone back to normal.
Data has been moved on the 2022 February 8th revision. It was too difficult to maintain, and not worth maintaining. Data will need to be moved to subprojects. Data from 2022 January 13th and below contain all the uncut data.
The following major data was omitted:
Counters (commented out)
Language knowledge sections (Java, JavaScript, etc.)
All other subsections
The data was mostly being duplicated with little change, occupying unnecessary space. I have now gone back to the classic way of writing status posts. It should reduce the writing time per day from ~20+ minutes to <5 minutes.
I had a decent day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage on 2021 December 27th/28th, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date.
Today, I worked on various projects, mainly on bringing the Team8 Collection game project up to date. I also updated my Linux configuration repository, and did partial Git-image Part B work, along with daily Git-image part A work.
Data has been moved on the 2022 February 8th revision. It was too difficult to maintain, and not worth maintaining. Data will need to be moved to subprojects. Data from 2022 January 13th and below contain all the uncut data.
The following major data was omitted:
Counters (commented out)
Language knowledge sections (Java, JavaScript, etc.)
All other subsections
The data was mostly being duplicated with little change, occupying unnecessary space. I have now gone back to the classic way of writing status posts. It should reduce the writing time per day from ~20+ minutes to <5 minutes.
I had a poor day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage on 2021 December 27th/28th, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date.
Today, I worked on my anti-WideVine DRM article, and partial daily Git-image work. I did not get anything else done.
Data has been moved on the 2022 February 8th revision, which started with the 2022 January 14th entry post. It was too difficult to maintain, and not worth maintaining. Data will need to be moved to subprojects. Data from 2022 January 13th and below contain all the uncut data.
The following major data was omitted:
Counters (commented out)
Language knowledge sections (Java, JavaScript, etc.)
All other subsections
The data was mostly being duplicated with little change, occupying unnecessary space. I have now gone back to the classic way of writing status posts. It should reduce the writing time per day from ~20+ minutes to <5 minutes.
I had a decent day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage on 2021 December 27th/28th, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date.
Today, I worked on modernizing the BluPhone project, and doing the usual daily Git-image documentation like yesterday; partial, but not fully.
I created my modern Wikipedia account today, with plans for usage on all Wikimedia sister projects. It used a few hours of my time today, and was backed up to GitHub via my Wikipedia repository.
Data has been moved on the 2022 February 8th revision, which started with the 2022 January 14th entry post. It was too difficult to maintain, and not worth maintaining. Data will need to be moved to subprojects. Data from 2022 January 13th and below contain all the uncut data.
The following major data was omitted:
Counters (commented out)
Language knowledge sections (Java, JavaScript, etc.)
All other subsections
The data was mostly being duplicated with little change, occupying unnecessary space. I have now gone back to the classic way of writing status posts. It should reduce the writing time per day from ~20+ minutes to <5 minutes.
I had an OK day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage on 2021 December 27th/28th, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date.
Today, I worked on modernizing my Wikimedia source code project, along with further profile setup. I didn't do anything else today.
Data has been moved on the 2022 February 8th revision, which started with the 2022 January 14th entry post. It was too difficult to maintain, and not worth maintaining. Data will need to be moved to subprojects. Data from 2022 January 13th and below contain all the uncut data.
The following major data was omitted:
Counters (commented out)
Language knowledge sections (Java, JavaScript, etc.)
All other subsections
The data was mostly being duplicated with little change, occupying unnecessary space. I have now gone back to the classic way of writing status posts. It should reduce the writing time per day from ~20+ minutes to <5 minutes.
I had a pretty good day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage on 2021 December 27th/28th, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date.
Today, I worked on modernizing and updating my top DeGoogle article projects (DeGoogle-your-life
& Its-time-to-cut-WideVine-DRM
) and also to address some constructive criticism that was given that helped me improve the articles. I didn't receive the notification until just today, when someone else mentioned it to me, unfortunately I don't have a very good notification system in place.
I also worked further on my Wikimedia project, the usual shortened Git-image work, updates to my GitHub profile repository, and a few small changes to the Team8_Collection
project.
Data has been moved on the 2022 February 8th revision, which started with the 2022 January 14th entry post. It was too difficult to maintain, and not worth maintaining. Data will need to be moved to subprojects. Data from 2022 January 13th and below contain all the uncut data.
The following major data was omitted:
Counters (commented out)
Language knowledge sections (Java, JavaScript, etc.)
All other subsections
The data was mostly being duplicated with little change, occupying unnecessary space. I have now gone back to the classic way of writing status posts. It should reduce the writing time per day from ~20+ minutes to <5 minutes.
I had a poor day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage on 2021 December 27th/28th, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date.
Today, I worked on very limited amounts of Git-image work, and updates to my Raspberry Pi blog and Wikimedia source code. I also did several forks today, but that was about it.
Data has been moved on the 2022 February 8th revision, which started with the 2022 January 14th entry post. It was too difficult to maintain, and not worth maintaining. Data will need to be moved to subprojects. Data from 2022 January 13th and below contain all the uncut data.
The following major data was omitted:
Counters (commented out)
Language knowledge sections (Java, JavaScript, etc.)
All other subsections
The data was mostly being duplicated with little change, occupying unnecessary space. I have now gone back to the classic way of writing status posts. It should reduce the writing time per day from ~20+ minutes to <5 minutes.
I had an OK with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage on 2021 December 27th/28th, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date.
Today, I worked on the usual limited Git-image work, along with significant work on my Raspberry Pi and Wikimedia source code repositories. I also did an update to my URLL specification, defining version 2 of the specification. That was it for today.
Data has been moved on the 2022 February 8th revision, which started with the 2022 January 14th entry post. It was too difficult to maintain, and not worth maintaining. Data will need to be moved to subprojects. Data from 2022 January 13th and below contain all the uncut data.
The following major data was omitted:
Counters (commented out)
Language knowledge sections (Java, JavaScript, etc.)
All other subsections
The data was mostly being duplicated with little change, occupying unnecessary space. I have now gone back to the classic way of writing status posts. It should reduce the writing time per day from ~20+ minutes to <5 minutes.
I had a poor day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage on 2021 December 27th/28th, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date.
Today, I worked solely on my Wikimedia source code project. I am starting to experience severe issues with all the number keys on my laptop, and I have also been procrastinating today on many works. It wasn't the best development day for me.
Data has been moved on the 2022 February 8th revision, which started with the 2022 January 14th entry post. It was too difficult to maintain, and not worth maintaining. Data will need to be moved to subprojects. Data from 2022 January 13th and below contain all the uncut data.
The following major data was omitted:
Counters (commented out)
Language knowledge sections (Java, JavaScript, etc.)
All other subsections
The data was mostly being duplicated with little change, occupying unnecessary space. I have now gone back to the classic way of writing status posts. It should reduce the writing time per day from ~20+ minutes to <5 minutes.
I had an OK day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage on 2021 December 27th/28th, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date.
Today, I worked heavily on a loophole free camera privacy specification, my Raspberry Pi blog, and limited Git-image work. I did not do anything else today.
Data has been moved on the 2022 February 8th revision, which started with the 2022 January 14th entry post. It was too difficult to maintain, and not worth maintaining. Data will need to be moved to subprojects. Data from 2022 January 13th and below contain all the uncut data.
The following major data was omitted:
Counters (commented out)
Language knowledge sections (Java, JavaScript, etc.)
All other subsections
The data was mostly being duplicated with little change, occupying unnecessary space. I have now gone back to the classic way of writing status posts. It should reduce the writing time per day from ~20+ minutes to <5 minutes.
I had an OK day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage on 2021 December 27th/28th, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date. I have recently decided to stop this project, as I found it was eating up far too much time, and needed to be automated.
Today, I was mostly inactive on GitHub, internally, I was working very hard on getting caught up. I did not use my Raspberry Pi at all today due to a lack of time, and I finally found my fatal productivity mistake, which is that the all-contributors setup, data, and thread archival needs to be automated, and should not be done manually anymore. I only worked publicly on my GNOME System Monitor Git-image and Daily Desktop Screenshot projects.
Data has been moved on the 2022 February 8th revision, which started with the 2022 January 14th entry post. It was too difficult to maintain, and not worth maintaining. Data will need to be moved to subprojects. Data from 2022 January 13th and below contain all the uncut data.
The following major data was omitted:
Counters (commented out)
Language knowledge sections (Java, JavaScript, etc.)
All other subsections
The data was mostly being duplicated with little change, occupying unnecessary space. I have now gone back to the classic way of writing status posts. It should reduce the writing time per day from ~20+ minutes to <5 minutes.
I had an OK day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage on 2021 December 27th/28th, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date. I have recently decided to stop this project, as I found it was eating up far too much time, and needed to be automated.
Today, I was again mostly inactive on GitHub, internally, I was working very hard on getting caught up. I did not use my Raspberry Pi at all today due to a lack of time, and I only worked publicly on basic Git-image projects.
Data has been moved on the 2022 February 8th revision, which started with the 2022 January 14th entry post. It was too difficult to maintain, and not worth maintaining. Data will need to be moved to subprojects. Data from 2022 January 13th and below contain all the uncut data.
The following major data was omitted:
Counters (commented out)
Language knowledge sections (Java, JavaScript, etc.)
All other subsections
The data was mostly being duplicated with little change, occupying unnecessary space. I have now gone back to the classic way of writing status posts. It should reduce the writing time per day from ~20+ minutes to <5 minutes.
I had a pretty good day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage on 2021 December 27th/28th, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date. I have recently decided to stop this project, as I found it was eating up far too much time, and needed to be automated.
Today, I was more active on GitHub, working on a variety of projects, but procrastinating against getting completely caught up. I began to resume and finalize the extended Git-image work I had been holding off for weeks, and also worked on my video directory and camera privacy specification. I also created several new projects today, doing work with APK files, creating an experimental redirect page, publishing the StealthGeo font I have been working on for about a week, creating a root life archive repository titled SeansLifeArchive
and publishing the concept of the Document Version Control System for uOffice that I have had held off for a while, since I have been trying to get caught up. I didn't do anything else today.
Data has been moved on the 2022 February 8th revision, which started with the 2022 January 14th entry post. It was too difficult to maintain, and not worth maintaining. Data will need to be moved to subprojects. Data from 2022 January 13th and below contain all the uncut data.
The following major data was omitted:
Counters (commented out)
Language knowledge sections (Java, JavaScript, etc.)
All other subsections
The data was mostly being duplicated with little change, occupying unnecessary space. I have now gone back to the classic way of writing status posts. It should reduce the writing time per day from ~20+ minutes to <5 minutes.
I had an OK day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage on 2021 December 27th/28th, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date. I have recently decided to stop this project, as I found it was eating up far too much time, and needed to be automated.
Today, I was focused strongly on getting caught up on GitHub image snapshot uploads, and limited Git-image work. That was it for today.
Data has been moved on the 2022 February 8th revision, which started with the 2022 January 14th entry post. It was too difficult to maintain, and not worth maintaining. Data will need to be moved to subprojects. Data from 2022 January 13th and below contain all the uncut data.
The following major data was omitted:
Counters (commented out)
Language knowledge sections (Java, JavaScript, etc.)
All other subsections
The data was mostly being duplicated with little change, occupying unnecessary space. I have now gone back to the classic way of writing status posts. It should reduce the writing time per day from ~20+ minutes to <5 minutes.
I had an OK day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage on 2021 December 27th/28th, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date. I have recently decided to stop this project, as I found it was eating up far too much time, and needed to be automated.
Today, I was focused on several things again. I did limited Git-image work, and got caught up on battery documentation image uploads, worked heavily on my Raspberry Pi blog, and my first GitHub image repo. I also published the idea for the DeciCube
an experimental max density storage device ranging in the billions to trillions of dollars in cost, but with the ability to store over 500 thousand copies of the entire 2021 Internet on a single brick of data. This project is named so, as it can hold over a decillion bytes of data, and is in the shape of a giant cube. It is considered max density, as every Silicon atom is used for storage, with an estimated 108 atoms being needed per byte of data. I can't manufacture one myself, obviously, but max density storage devices have been an interest of mine for a couple years now, and this is the second practical example I have come up with. It requires meeting the limits of Moores Law to build, and there is no way to make it more compact until we can find out how to make atoms smaller, or something similar, if that is even possible (maybe there is something smaller in scale to an atom)
I had time to use my Raspberry Pi for audio conversion today, and I continuously tried to get caught up. I had one of my repositories hit 10K commits for the first time today (SeansLifeArchive_Images_GitHub
) and I dealt with further keyboard failures, with the 1
, 2
, 3
, and prnt scrn (F10)
keys failing. Today was also the climax of my CPU fan failure, the fan itself sounding like it was made from paper today. The next day (and as of writing this on 2022, Thursday, February 10th) it has had no further issues, and doesn't even go to a support assistant screen upon boot anymore... for now.
Data has been moved on the 2022 February 8th revision, which started with the 2022 January 14th entry post. It was too difficult to maintain, and not worth maintaining. Data will need to be moved to subprojects. Data from 2022 January 13th and below contain all the uncut data.
The following major data was omitted:
Counters (commented out)
Language knowledge sections (Java, JavaScript, etc.)
All other subsections
The data was mostly being duplicated with little change, occupying unnecessary space. I have now gone back to the classic way of writing status posts. It should reduce the writing time per day from ~20+ minutes to <5 minutes.
I had an OK day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage on 2021 December 27th/28th, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date. I have recently decided to stop this project, as I found it was eating up far too much time, and needed to be automated.
Today, I was focused on semi-limited Git-image work, preparing for next month, staying caught up, and making minor revisions to the DeciCube. That was it for today.
Data has been moved on the 2022 February 8th revision, which started with the 2022 January 14th entry post. It was too difficult to maintain, and not worth maintaining. Data will need to be moved to subprojects. Data from 2022 January 13th and below contain all the uncut data.
The following major data was omitted:
Counters (commented out)
Language knowledge sections (Java, JavaScript, etc.)
All other subsections
The data was mostly being duplicated with little change, occupying unnecessary space. I have now gone back to the classic way of writing status posts. It should reduce the writing time per day from ~20+ minutes to <5 minutes.
I had a poor day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage on 2021 December 27th/28th, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
I have been working on a super verbose task for over a week, which is setting up the all-contributors
bot and archiving the setup data, posts, and replies. It is one of the most verbose issue archival tasks I have worked on to date. I have recently decided to stop this project, as I found it was eating up far too much time, and needed to be automated.
Today, I was only able to do limited Git-image work, and that was it. I worked on other tasks in the background, but mostly procrastinated.
Data has been moved on the 2022 February 8th revision, which started with the 2022 January 14th entry post. It was too difficult to maintain, and not worth maintaining. Data will need to be moved to subprojects. Data from 2022 January 13th and below contain all the uncut data.
The following major data was omitted:
Counters (commented out)
Language knowledge sections (Java, JavaScript, etc.)
All other subsections
The data was mostly being duplicated with little change, occupying unnecessary space. I have now gone back to the classic way of writing status posts. It should reduce the writing time per day from ~20+ minutes to <5 minutes.
I had a poor day with development today. The month started disorganized, and I hope it gets better. I wanted to stay caught up until January 1st, but it all fell apart in a power outage on 2021 December 27th/28th, and the amount of work I am behind in is just piling up. I am still very far behind today. I have lots planned, but I just continue to fall behind.
Today I worked solely on my 2020 GitHub image repo, and forking several projects. That was pretty much it, I did work on getting caught up in the background.
Data has been moved on the 2022 February 8th revision, which started with the 2022 January 14th entry post. It was too difficult to maintain, and not worth maintaining. Data will need to be moved to subprojects. Data from 2022 January 13th and below contain all the uncut data.
The following major data was omitted:
Counters (commented out)
Language knowledge sections (Java, JavaScript, etc.)
All other subsections
The data was mostly being duplicated with little change, occupying unnecessary space. I have now gone back to the classic way of writing status posts. It should reduce the writing time per day from ~20+ minutes to <5 minutes.
Daily status - 2022 January
This is the daily status thread for 2022 January. Daily status posts will be put daily (or when I get to it) below this post.
I have really been falling behind this month. It is January 12th, and I haven't gotten a single entry completed yet (as of 5:26 pm) but I am working on it. I plan to try again tonight/this evening.
Click here to see last months (2021 December) daily status posts