Add arXiv data fetching functionality #179

Goziee-git · 2025-10-11T23:29:04Z

Fixes

Fixes Integrate arXiv as data source for academic commons quantification #178 by @Goziee-git

Description

Implements comprehensive arXiv data collection system to quantify open access academic papers in the commons.

Type of Change

New feature implementing data collection from the arXivopen access academic papers
Data source addition/modification

Changes Made

Added arXiv API integration for fetching academic paper metadata using the arXiv API as project requirement for automation of fetching new data sources.
Implemented data processing pipeline for arXiv submissions in the scripts/1-fetch/arxiv_fetch.py
Created filtering logic for open access and CC-licensed papers
Added arXiv data to quarterly reporting system

Testing

Static analysis passes (./dev/check.sh)
arXiv API integration tested with sample queries
Data processing validated with test dataset

Data Impact

New data source added (arXiv academic papers)
Report generation affected (new academic commons metrics)

Checklist

I have read and understood the Developer Certificate of Origin (DCO), below, which covers the contents of this pull request (PR).
My pull request doesn't include code or content generated with AI.
My pull request has a descriptive title (not a vague title like Update index.md).
My pull request targets the default branch of the repository (main or master).
My commit messages follow best practices.
My code follows the established code style of the repository.
I added or updated tests for the changes I made (if applicable).
I added or updated documentation (if applicable).
I tried running the project locally and verified that there are no
visible errors.

Developer Certificate of Origin

For the purposes of this DCO, "license" is equivalent to "license or public domain dedication," and "open source license" is equivalent to "open content license or public domain dedication."

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

TimidRobot

This is a great start.

I recommend also developing a data/report plan. For example:

It is not meaningful to get a count of a single language (though it is worth noting that other languages are not available).
Category codes converted to reporting (words and/or abbreviations instead of acronyms)

scripts/3-report/gcs_report.py

data/2025Q4/1-fetch/arxiv_1_count.csv

data/2025Q4/1-fetch/arxiv_2_count_by_category.csv

data/2025Q4/1-fetch/arxiv_2_count_by_language.csv

data/2025Q4/1-fetch/arxiv_3_count_by_country.csv

data/2025Q4/1-fetch/arxiv_3_count_by_year.csv

data/2025Q4/1-fetch/arxiv_4_count_by_author_count.csv

scripts/1-fetch/arxiv_fetch.py

Goziee-git · 2025-10-16T13:02:49Z

@Goziee-git please follow through on your first pull request (PR) before submitting any more:

Add OTL education CSV reader script #168

Depending on how that one goes, I might reopen this PR.

hello @TimidRobot as requested, I have made changes based on your review. Good work is emphasized over speed and I do hope my attempt to go full circle with other PR hasn't dented my chances of significantly contributing to the project. Thank you🙏🏼

TimidRobot · 2025-10-17T17:42:03Z

@Goziee-git ok, please focus on this PR

Goziee-git · 2025-10-20T21:09:46Z

This is a great start.

I recommend also developing a data/report plan. For example:

It is not meaningful to get a count of a single language (though it is worth noting that other languages are not available).

Category codes converted to reporting (words and/or abbreviations instead of acronyms)

@TimidRobot I have removed the query for languages as it returns only English. Also worthy of note here, the arxiv data source accepts papers in other languages but requires that the paper abstracts be submitted in English. so Impossible to get a good distribution of licenses as per language usage.

Also, as suggested. I converted the category codes to reporting words that a more user-friendly and readable using an external arxiv_category_map.yml, in data/2025Q4/1-fetch. I believe this should make updates repoducible and maintainable over time. The script now produces arxiv_2_count_by_category_report.csv and arxiv_2_count_by_category_report_agg.csv for better reporting. Also instead of dumping author count data previously, i implemented a Bucketing approach. in arxiv_4_count_by_author_bucket.csv to group author counts into meaningful ranges (1, 2-3, 4-6, 7-10, 11+). The script also generates a arxiv_provenance.json to record metadata for audit, reproducibility, and provenance

Goziee-git · 2025-10-20T21:25:57Z

Hello @TimidRobot, i observed from multiple results fetched previously that the script failed to fetch CC licenses that may be recorded as hyphenated variants like (CC-BY, CC-BY-NC, etc). I have implemented a compiled regex pattern that replaces the string matching for more robust license detection

I have also looked at some of the implementations in other PR to use the normalize_license_text() function for consistent license identification.

Please i'ld like to know what your thoughts are on these changes and work continuously on further improvements, Thanks.

scripts/3-report/gcs_report.py

scripts/1-fetch/arxiv_fetch.py

arxiv_fetch.py

TimidRobot · 2025-10-21T10:18:46Z

Also, as suggested. I converted the category codes to reporting words that a more user-friendly and readable using an external arxiv_category_map.yml, in data/2025Q4/1-fetch. I believe this should make updates repoducible and maintainable over time.

How was arxiv_category_map.yml created?
- If by script, it should probably go in dev/
Data that persists should go in data/ not a specific quarter directory

The script now produces arxiv_2_count_by_category_report.csv and arxiv_2_count_by_category_report_agg.csv for better reporting. Also instead of dumping author count data previously, i implemented a Bucketing approach. in arxiv_4_count_by_author_bucket.csv to group author counts into meaningful ranges (1, 2-3, 4-6, 7-10, 11+).

I'll look at data after outstanding comments are resolved.

The script also generates a arxiv_provenance.json to record metadata for audit, reproducibility, and provenance

I'll look at data after outstanding comments are resolved. That said, I'm not excited about adding JSON to the project.

TimidRobot · 2025-10-21T10:19:48Z

Hello @TimidRobot, i observed from multiple results fetched previously that the script failed to fetch CC licenses that may be recorded as hyphenated variants like (CC-BY, CC-BY-NC, etc). I have implemented a compiled regex pattern that replaces the string matching for more robust license detection

I have also looked at some of the implementations in other PR to use the normalize_license_text() function for consistent license identification.

Please i'ld like to know what your thoughts are on these changes and work continuously on further improvements, Thanks.

It's probably a good idea to create a function in the shared library eventually. Please leave that to last, however.

Refactor arxiv_fetch.py to use requests library for HTTP requests, implementing retry logic for better error handling. Update license extraction logic and CSV headers to remove PLAN_INDEX.

.gitignore

TimidRobot

I'm unable to test the script.

Command:

Output:

Traceback (most recent call last):
  File "/Users/timidrobot/git/creativecommons/quantifying/./scripts/1-fetch/arxiv_fetch.py", line 18, in <module>
    import feedparser
ModuleNotFoundError: No module named 'feedparser'

TimidRobot · 2025-10-22T15:27:58Z

scripts/1-fetch/arxiv_fetch.py

+    return session
+
+
+def normalize_license_text(raw_text: str) -> str:


Why does this function have types?

Why does this function have types?
@TimidRobot, the type hint in the normalize_license_text() helps to ensure consistency in the data-type expected since entries from the arxiv API can be returned in several data types. So this helps with processing and avoiding type errors. Normalizing the returned value as a string type i figured would also help to Prevents type-related bugs when the returned license identifier is used in dictionaries, CSV writing, or logging. Would you prefer a different approach or implementation here?

@Goziee-git I meant, "Why does this function alone have types?". It looks like you copied something without understanding it (you should never submit code you don't understand).

Type checking in Python still requires supporting tooling. For example:

File: test.py

def test_type(test: str) -> str: print(type(test)) test_type(1)

Command:

python3 ./test.py

Output:

<class 'int'>

Any new tooling should first be decided in an issue and then added in a dedicated pull request.

@Goziee-git I meant, "Why does this function alone have types?". It looks like you copied something without understanding it (you should never submit code you don't understand).

Type checking in Python still requires supporting tooling. For example:

File: test.py

def test_type(test: str) -> str: print(type(test)) test_type(1)

Command:

python3 ./test.py

Output:

<class 'int'>

Any new tooling should first be decided in an issue and then added in a dedicated pull request.

@TimidRobot, I have raised an issue #212 for the type check tooling specifically choosing the mypy python package. I have also read through its usage. The current implementation here only shows type hints and no specific implementation. With your permission, i'ld like that you review the issue and give your recommendations since the implementation here can only be concrete when the issue #212 is resolved.

Please remove the type hint. It can be added back when/if type hints are supported by the project.

Goziee-git · 2025-10-22T16:58:05Z

I'm unable to test the script.

Command:

Output:

Traceback (most recent call last):
  File "/Users/timidrobot/git/creativecommons/quantifying/./scripts/1-fetch/arxiv_fetch.py", line 18, in <module>
    import feedparser
ModuleNotFoundError: No module named 'feedparser'

@TimidRobot,I ran the project as directed by the project README which requires installing the dependencies first and then running the script from the root of the project using pipenv run. So from the interactive shell with (/Users/timidrobot/git/creativecommons/quantifying) as path the command should be ./scripts/1-fetch/arxiv_fetch.py with required args as desired.

I Think the ModuleNotFoundError is from the missing feedparser module in your pipfile. The arxiv_fetch.py script requires the feedparser module because The script queries ArXiv's API which returns RSS/Atom feeds containing paper metadata. feedparser converts this XML into structured Python objects, allowing the script to extract license information, categories, publication years, and author counts from each paper entry.

Without feedparser, the script can't process ArXiv's API responses. So i think you have to add the feedparser dep to your pipfile to run the script.

TimidRobot · 2025-10-23T11:15:22Z

Without feedparser, the script can't process ArXiv's API responses. So i think you have to add the feedparser dep to your pipfile to run the script.

@Goziee-git no, you need to include an updated Pipfile and Pipfile.lock in your pull request.

…ying into feature/arxiv

Goziee-git · 2025-10-23T20:48:09Z

Without feedparser, the script can't process ArXiv's API responses. So i think you have to add the feedparser dep to your pipfile to run the script.

@Goziee-git no, you need to include an updated Pipfile and Pipfile.lock in your pull request.

@TimidRobot, since this will require that i add a new dependency/tooling to the Pipefile and the Pipfile.lock would you prefer that i submit the updates for this here without raising an issue for it or otherwise

Babi-B · 2025-10-24T03:44:53Z

scripts/1-fetch/arxiv_fetch.py

+FILE_ARXIV_YEAR = shared.path_join(
+    PATHS["data_1-fetch"], "arxiv_3_count_by_year.csv"
+)
+FILE_ARXIV_AUTHOR = shared.path_join(
+    PATHS["data_1-fetch"], "arxiv_4_count_by_author_count.csv"
+)
+FILE_ARXIV_AUTHOR_BUCKET = shared.path_join(
+    PATHS["data_1-fetch"], "arxiv_4_count_by_author_bucket.csv"


Hi @Goziee-git!

I think you should order your constants

Hi @TimidRobot!

Given how large the constant list is, would you recommend a dictionary is used here?

For example (R43-R49),

FILE_ARXIV = { "count": shared.path_join(PATHS["data_1-fetch"], "arxiv_1_count.csv"), "category": shared.path_join(PATHS["data_1-fetch"], "arxiv_2_count_by_category.csv"), "category_report": shared.path_join(PATHS["data_1-fetch"], "arxiv_2_count_by_category_report.csv"), ... }

All related constants grouped in the same dictionary

The benefit of a dictionary is that it can be acted on programmatically. If that is helpful, a dictionary is a good idea. If not, I tend to prefer individual constants.

Hi @Goziee-git!

I think you should order your constants

Really, its a good practice to order constants, and i do have alot of constants. I agree with you that ordering them keeps the flow organised and conforms to proper coding practices. This script is still in development and will need all the insights i can get to make it best for longterm use. I appreciate this here @Babi-B, Thanks

Babi-B · 2025-10-24T03:54:37Z

dev/arxiv_category_converter.py

+    except Exception:
+        return {}


Hi @Goziee-git!

I have a question about this. Why do you choose to silently swallow up the exceptions? Would it not be better to log an error/warning so the user knows the mapping wasn't loaded?

This script is still in development and thanks @Babi-B for the notes here. I have looked into it carefully and have implemented changes to properly log exceptions instead of silently handling them.

Babi-B · 2025-10-24T04:05:21Z

dev/arxiv_category_converter.py

@@ -0,0 +1,73 @@
+#!/usr/bin/env python


Is this script meant to be imported purely as a module? If it is, I think it is not needed here

I mean the shebang

Babi-B · 2025-10-24T04:23:08Z

dev/arxiv_category_converter.py

+        data_dir: Directory containing arxiv_category_map.yaml
+    """
+    if not os.path.exists(input_file):
+        return


Here too...a silent return. Why not a warning or an exception? Could this not lead to confusing downstream errors?

Babi-B · 2025-10-24T04:24:47Z

dev/arxiv_category_converter.py

+
+    with (
+        open(input_file, "r") as infile,
+        open(output_file, "w", newline="") as outfile,


I think you should add encoding="utf-8 to prevent platform-dependent encoding issues

Babi-B · 2025-10-24T04:48:33Z

scripts/1-fetch/arxiv_fetch.py

+]
+
+# Log the start of the script execution
+LOGGER.info("Script execution started.")


You should put this in the main function so it triggers when the script actually runs

Babi-B · 2025-10-24T05:37:38Z

scripts/1-fetch/arxiv_fetch.py

+def initialize_data_file(file_path, headers):
+    """Initialize CSV file with headers if it doesn't exist."""
+    if not os.path.isfile(file_path):
+        with open(file_path, "w", newline="") as file_obj:


I think you should add encoding="utf-8" here too

Babi-B · 2025-10-24T05:38:37Z

scripts/1-fetch/arxiv_fetch.py

+    retry_strategy = Retry(
+        total=5,
+        backoff_factor=1,
+        status_forcelist=[408, 429, 500, 502, 503, 504],


There is a STATUS_FORCELIST constant in the shared.py

Babi-B · 2025-10-24T05:40:45Z

scripts/1-fetch/arxiv_fetch.py

+    # author_counts: {license: {author_count(int|None): count}}
+
+    # Save license counts
+    with open(FILE_ARXIV_COUNT, "w", newline="") as fh:


encoding="utf-8" here too

Babi-B · 2025-10-24T05:41:19Z

scripts/1-fetch/arxiv_fetch.py

+            writer.writerow({"TOOL_IDENTIFIER": lic, "COUNT": c})
+
+    # Save detailed category counts (code)
+    with open(FILE_ARXIV_CATEGORY, "w", newline="") as fh:


encoding="utf-8"

Babi-B · 2025-10-24T05:50:40Z

scripts/1-fetch/arxiv_fetch.py

@Goziee-git

I noticed you didn't add encoding="utf-8" to your open() calls when writing to CSVs. I didn't comment on all, but it is important to do so to avoid potential encoding issues where UTF-8 might not be the default

scripts/1-fetch/arxiv_fetch.py

Babi-B · 2025-10-24T06:40:04Z

Hi @TimidRobot @Goziee-git

I have noticed entries like these in the CSV files:

"TOOL_IDENTIFIER","AUTHOR_COUNT","COUNT"
"UNKNOWN CC legal tool","3","12"
"UNKNOWN CC legal tool","2","18"
"UNKNOWN CC legal tool","1","9"
"UNKNOWN CC legal tool","8","4"
"UNKNOWN CC legal tool","4","13"
"UNKNOWN CC legal tool","10","5"
"UNKNOWN CC legal tool","5","9"
"UNKNOWN CC legal tool","9","4"

I was wondering the purpose of collecting UKNOWN CC Legal tools values. Will they be used to diagnose data quality (like a plot of unkown vs known license coverage), or should they be excluded from the analysis phase?

TimidRobot · 2025-10-24T08:59:12Z

Without feedparser, the script can't process ArXiv's API responses. So i think you have to add the feedparser dep to your pipfile to run the script.

@Goziee-git no, you need to include an updated Pipfile and Pipfile.lock in your pull request.

Without feedparser, the script can't process ArXiv's API responses. So i think you have to add the feedparser dep to your pipfile to run the script.

@Goziee-git no, you need to include an updated Pipfile and Pipfile.lock in your pull request.

@TimidRobot, since this will require that i add a new dependency/tooling to the Pipefile and the Pipfile.lock would you prefer that i submit the updates for this here without raising an issue for it or otherwise

You can include Pipfile and Pipfile.lock in this PR (no new issue necessary). Please be sure changes are limited to what is absolutely necessary.

TimidRobot · 2025-10-24T09:04:03Z

Hi @TimidRobot @Goziee-git

I have noticed entries like these in the CSV files:
"TOOL_IDENTIFIER","AUTHOR_COUNT","COUNT"
"UNKNOWN CC legal tool","3","12"
"UNKNOWN CC legal tool","2","18"
"UNKNOWN CC legal tool","1","9"
"UNKNOWN CC legal tool","8","4"
"UNKNOWN CC legal tool","4","13"
"UNKNOWN CC legal tool","10","5"
"UNKNOWN CC legal tool","5","9"
"UNKNOWN CC legal tool","9","4"
I was wondering the purpose of collecting UKNOWN CC Legal tools values. Will they be used to diagnose data quality (like a plot of unkown vs known license coverage), or should they be excluded from the analysis phase?

I think it's helpful to include the unknowns, but I expect a single entry.

Goziee-git · 2025-10-24T10:19:41Z

Without feedparser, the script can't process ArXiv's API responses. So i think you have to add the feedparser dep to your pipfile to run the script.

@Goziee-git no, you need to include an updated Pipfile and Pipfile.lock in your pull request.

Without feedparser, the script can't process ArXiv's API responses. So i think you have to add the feedparser dep to your pipfile to run the script.

@Goziee-git no, you need to include an updated Pipfile and Pipfile.lock in your pull request.

@TimidRobot, since this will require that i add a new dependency/tooling to the Pipefile and the Pipfile.lock would you prefer that i submit the updates for this here without raising an issue for it or otherwise

You can include Pipfile and Pipfile.lock in this PR (no new issue necessary). Please be sure changes are limited to what is absolutely necessary.

Hello @TimidRobot, in addition to the feedparser, I also have a new dependency here PyYAML. The PyYAML dep is used by the arxiv_fetch.py and the arxiv_category_converter.py. Both scripts use import yaml which comes from the PyYAML package for:
• Loading category mappings (arxiv_category_map.yaml)
• Writing provenance data for audit trails
• Reading configuration files
I am making a note of this here because I am also going to be adding it to the pipfile and also the pipfile.lock which will be added to this PR.

In contrast, i also observed that the gcs_country_collection.yaml and gcs_language_collection.yaml files don't require PyYAML for their generation. However, if any Python scripts read these YAML files later, they would need PyYAML. so with your permission can i also add these here or would you prefer otherwise.

…ared STATUS_FORCELIST

- Removed type hints from normalize_license_text function - Type checkers not yet used as tooling for the project

Goziee-git requested review from a team as code owners October 11, 2025 23:29

Goziee-git requested review from TimidRobot and possumbilities and removed request for a team October 11, 2025 23:29

cc-open-source-bot added this to TimidRobot Oct 11, 2025

cc-open-source-bot moved this to In review in TimidRobot Oct 11, 2025

Goziee-git changed the title ~~Add arXiv data fetching and processing functionality~~ Add arXiv data fetching functionality Oct 12, 2025

TimidRobot requested changes Oct 14, 2025

View reviewed changes

TimidRobot reviewed Oct 14, 2025

View reviewed changes

scripts/1-fetch/arxiv_fetch.py Outdated Show resolved Hide resolved

TimidRobot self-assigned this Oct 14, 2025

TimidRobot mentioned this pull request Oct 15, 2025

[DISCARDED] Pull Request: Fix ArXiv Fetch Script - Replace urllib with requests and improve error handling #192

Closed

9 tasks

This comment was marked as outdated.

Sign in to view

TimidRobot closed this Oct 15, 2025

github-project-automation bot moved this from In review to Done in TimidRobot Oct 15, 2025

Goziee-git mentioned this pull request Oct 16, 2025

Integrate arXiv as data source for academic commons quantification #178

Open

5 tasks

TimidRobot reopened this Oct 17, 2025

TimidRobot mentioned this pull request Oct 17, 2025

Integrate Fetching Functionality With the Europeana Data Collection Script. #199

Closed

9 tasks

TimidRobot requested changes Oct 21, 2025

View reviewed changes

scripts/3-report/gcs_report.py Show resolved Hide resolved

scripts/1-fetch/arxiv_fetch.py Outdated Show resolved Hide resolved

scripts/1-fetch/arxiv_fetch.py Outdated Show resolved Hide resolved

scripts/1-fetch/arxiv_fetch.py Show resolved Hide resolved

TimidRobot reviewed Oct 21, 2025

View reviewed changes

arxiv_fetch.py Outdated Show resolved Hide resolved

Goziee-git added 4 commits October 22, 2025 04:03

Add arXiv data fetching and processing functionality

0783ca9

Delete scripts/3-report/gcs_report.py

6e16e63

added fixes: refactor request and license extraction logic

9ea0071

Refactor HTTP requests and license extraction logic.

f8c9774

Refactor arxiv_fetch.py to use requests library for HTTP requests, implementing retry logic for better error handling. Update license extraction logic and CSV headers to remove PLAN_INDEX.

TimidRobot reviewed Oct 22, 2025

View reviewed changes

.gitignore Outdated Show resolved Hide resolved

TimidRobot requested changes Oct 22, 2025

View reviewed changes

Delete .gitignore

f14e4ce

Goziee-git added 2 commits October 23, 2025 21:03

Merge remote-tracking branch 'upstream/main' into feature/arxiv

f9e5ae7

Merge branch 'feature/arxiv' of https://github.com/Goziee-git/quantif…

6769a33

…ying into feature/arxiv

Goziee-git force-pushed the feature/arxiv branch from d4409a4 to 6769a33 Compare October 23, 2025 21:52

Babi-B reviewed Oct 24, 2025

View reviewed changes

scripts/1-fetch/arxiv_fetch.py Outdated Show resolved Hide resolved

Goziee-git added 5 commits October 24, 2025 11:43

Improve arxiv_fetch.py: add debug logging, organize constants, use sh…

95df48a

…ared STATUS_FORCELIST

Add PyYAML and feedparser dependencies for ArXiv functionality

267105b

Update arxiv_fetch.py

0aa919c

Remove shebang from imported module

9b83241

Remove type hints from arxiv_fetch.py

58a9f99

- Removed type hints from normalize_license_text function - Type checkers not yet used as tooling for the project

		return session


		def normalize_license_text(raw_text: str) -> str:

Uh oh!

Add arXiv data fetching functionality #179

Are you sure you want to change the base?

Add arXiv data fetching functionality #179

Conversation

Goziee-git commented Oct 11, 2025 • edited by TimidRobot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Fixes

Description

Type of Change

Changes Made

Testing

Data Impact

Related Documentation

Checklist

Developer Certificate of Origin

Uh oh!

TimidRobot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

This comment was marked as outdated.

Goziee-git commented Oct 16, 2025

Uh oh!

TimidRobot commented Oct 17, 2025

Uh oh!

Goziee-git commented Oct 20, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Goziee-git commented Oct 20, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

TimidRobot commented Oct 21, 2025

Uh oh!

TimidRobot commented Oct 21, 2025

Uh oh!

Uh oh!

TimidRobot left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Goziee-git commented Oct 22, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

TimidRobot commented Oct 23, 2025

Uh oh!

Goziee-git commented Oct 23, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Goziee-git commented Oct 11, 2025 •

edited by TimidRobot

Loading

Goziee-git commented Oct 20, 2025 •

edited

Loading

Goziee-git commented Oct 20, 2025 •

edited

Loading

Goziee-git commented Oct 22, 2025 •

edited

Loading

Goziee-git commented Oct 23, 2025 •

edited

Loading

Babi-B Oct 24, 2025 •

edited

Loading