Feed of "asudox"

asudox pushed to main at asudox/reinkpy

2025-12-22T15:42:01+01:00

48f172762556fcab5cb9feec08465904cf5d51c9 epson: sort and update db 0c8de5703839301df5abe647c924e461d8a8830e README: link to non-linux resources a9f2f86df005a232f5c925449a65ae9153722db5 usb: less verbose logging ae2a672292b73dad9121cc3f8ca99219418097f1 epson: abort atomic write if eeprom cannot be read (from #64) c866efaacc7e31ac32c75363954be67412081dda fix #61 typo in README

asudox pushed to main at asudox/pages

2025-12-15T20:20:28+01:00

276b6b6d0904eccfd44639fc4fadf30da1fe3cdb .domains aktualisiert

asudox pushed to main at asudox/.profile

2025-11-01T13:49:49+01:00

7c118e3bd3bbf04c7574dcebaf7c304d723ea1b1 README.md aktualisiert

asudox pushed to main at asudox/.profile

2025-07-05T11:57:58+02:00

8735561c424a46f013782fecd634360d07f82d93 avatar1.jpg gelöscht

asudox pushed to main at asudox/.profile

2025-06-14T12:22:57+02:00

1af676fdb5a74ee5ba362a5cc72a5944a5f8e50a README.md aktualisiert

asudox pushed to main at asudox/.profile

2025-06-14T12:21:15+02:00

b95a98f33d4665b5d5c12d58d05a8fa8f191d5da Dateien nach „/“ hochladen

asudox created repository asudox/reinkpy

2025-06-06T21:45:39+02:00

asudox commented on issue gitnex/GitNex#1441

2025-04-10T17:36:51+02:00

Implement edit history

@mmarif whoops

asudox commented on issue gitnex/GitNex#1441

2025-04-10T16:47:28+02:00

Implement edit history

@mmarif There is such an API endpoint, but it is not documented for some reason.
Using the devtools, I can see that there is this endpoint:

https://{ instance.tld }/{ user }/{ repo }/issues/{ issue ID }/content-history/list?comment_id={ comment ID }

Then to get the previous comments, you use this endpoint:

https://{ instance.tld }/{ user }/{ repo }/issues/{ issue ID }/content-history/detail?comment_id={ comment ID }&history_id={ history ID }

History ID can be found in the JSON payload the first endpoint gives (value).

Here's also the code for it if it helps: forgejo.dev/forgejo.dev/forgejo@bebc244156/routers/web/repo/issue_content_history.go

asudox commented on issue gitnex/GitNex#1434

2025-04-03T22:14:04+02:00

Where is user/password login option?

It has been removed.

asudox commented on issue gitnex/GitNex#1430

2025-04-02T12:57:12+02:00

Version 8.0.1 does not include the authorization header

I noticed that it does include the authorization header when restored from a backup.

asudox opened issue gitnex/GitNex#1430

2025-04-02T12:50:40+02:00

I confirm that I have searched the issue tracker

Before opening an issue, take a few minutes to search the issue tracker (both open and closed issues) for the problem you are facing. This will reduce the need for issue triage and save time.

I confirm that I have searched the issue tracker

Describe the bug

I am unable to log into my account using the token into Codeberg's instance.

After inspecting the requests using PCAPDroid (a MITM tool), I can see that Codeberg returns a 401 HTTP status code as the authorization header is not being sent along with the request. Version 8.0.0 includes it.

To Reproduce

Open app
Try to login

Expected behavior

Should login.

Logs

Logs from PCAPDroid:

Version 8.0.0 request:

GET https://codeberg.org/api/v1/user HTTP/2.0
authorization: token __________
accept-encoding: gzip
user-agent: okhttp/5.0.0-alpha.14

Instance response:

HTTP/2.0 200 
cache-control: max-age=0, private, must-revalidate, no-transform
content-type: application/json;charset=utf-8
vary: Origin
date: Wed, 02 Apr 2025 10:47:37 GMT
content-length: 671
strict-transport-security: max-age=63072000; includeSubDomains; preload
permissions-policy: interest-cohort=()
x-frame-options: sameorigin
x-content-type-options: nosniff

{"id":116905,"login":"asudox"," ...}

Version 8.0.1 request:

GET https://codeberg.org/api/v1/user HTTP/2.0
accept-encoding: gzip
user-agent: okhttp/5.0.0-alpha.14

Instance response:

HTTP/2.0 401 
cache-control: max-age=0, private, must-revalidate, no-transform
content-type: application/json;charset=utf-8
vary: Origin
date: Wed, 02 Apr 2025 10:44:22 GMT
content-length: 73
strict-transport-security: max-age=63072000; includeSubDomains; preload
permissions-policy: interest-cohort=()
x-frame-options: sameorigin
x-content-type-options: nosniff

{"message":"token is required","url":"https://codeberg.org/api/swagger"}

Screenshots

None

Versions (please complete the following information)

GitNex: 8.0.1
Android: 14
Gitea/Forgejo: 10.0.0-141-ebf1f5b+gitea-1.22.0

Mode of installation

Google Play Store
F-droid
APK
Built from source
OpenAPK
Other stores (Name: )

SSL certificate

Signed (Codeberg, Let's encrypt etc.)
Self-signed

Declaration

I have carefully read and agree to follow the contribution guidelines.

asudox opened issue lemshare/lemshare#3

2025-04-01T09:34:30+02:00

3#[Feature Request] Support comment links#

asudox closed issue Codeberg-e.V./requests#465

2024-11-15T23:04:16+01:00

[CI] Personal website and a rust project

asudox opened issue Codeberg-e.V./requests#465

2024-11-15T22:57:57+01:00

Projects

CommunityModerator (WIP, upstream code not uploaded yet)
asudox.dev (WIP)

Expected Resource Usage

minimal

I would also like the following users to be added

No response

Additional Information

No response

Other Work

No response

Statement

I have placed a LICENSE file in my repository.
I understand that Codeberg's CI might not always be available or stable, despite best efforts.
I understand that I can use the feedback repository to share feedback or report problems.

asudox pushed to main at asudox/.profile

2024-10-12T18:04:01+02:00

2a3b23a610cd798dfe740f772a1b31dc4da01271 Dateien nach „/“ hochladen

asudox pushed to main at asudox/.profile

2024-08-14T15:14:53+02:00

026d8198d186cd9eafdebeaac46bd41ba497364a Update README.md

asudox pushed to main at asudox/.profile

2024-06-14T21:45:34+02:00

e22577170983b70433d09df3c4420331eebaf0bb Update README.md

asudox pushed to main at asudox/.profile

2024-06-14T21:45:16+02:00

d3d95ab87a21e6834d92ededc269b86681f59e3b Update README.md

asudox pushed to main at asudox/.profile

2024-06-14T21:44:58+02:00

09784900fa58c1cfc442ebdbedde4e55966a1245 Update README.md

asudox created repository asudox/.keyoxide

2024-05-24T16:46:30+02:00

asudox pushed to main at asudox/.profile

2024-05-24T15:36:15+02:00

e27a91c9837c47e249e27843f745e7383462c11c Update README.md

asudox pushed to main at asudox/.profile

2024-05-24T15:20:24+02:00

68318032473a8ae7a8c1d4c27b6cc8c3e4674ad5 Update README.md

asudox created repository asudox/.profile

2024-05-24T15:19:17+02:00

asudox opened issue Bazsalanszky/Eternity#246

2024-01-28T13:54:38+01:00

Description

In Lemmy frontend, you can "speak as mod" in the comments section, which sets the "distinguished" flag to "true".
This is pretty much overlooked by anyone, but useful when a mod wants to highlight their comment.

Background

https://join-lemmy.org/api/interfaces/DistinguishComment.html

Proposed Solution

This should be a single if statement that checks whether the retrieved comment response from the API has "distinguished" set to "true", and if it is, change the comment background to something like red or yellow and it also should be pinned at the top of the comments section.

Additional Context

An example of a distinguished comment available below.