AmaseCocoa

I'm currently working on: https://github.com/AmaseCocoa/apmodel

trying to use snaplet

I would like to migrate some of my projects to Codeberg, but since Codeberg doesn't seem to support PyPI's Trusted Publishing (yet), I don't think I'll be able to do that...

I made snaplet, an minimal JSON Mapper :)

I making auto-translated FEP document for Japanese, trying local models...

I have archived the apmodel repository. While developing apkit, I encountered the problematic aspects of apmodel, so I plan to redesign it. This does not mean I intend to abandon apkit.

I making activitypub server used for testing...

rewritting a apkit's ActivityPub client, current async-client inherited from aiohttp.ClientSession but, that's not recommended method...

I using Rust for writting DNS server for peculiar usage...

A relatively big issue with apkit that I'd been unable to resolve for ages was solved surprisingly easily, and once I thoroughly checked the cause, it turned out to be something obvious...😅

I have emoji but, I lost frontend 😂

Ok, I should to fix bootloader to use linux (and development environment)...

...or, reinstall?

I'm falling behind in my studies, so I need to hit the books for a while...

Gemini 3.0 is great... it quickly wrote out the design I had in mind.

I must work on this issue...

I now have domain for fedi-libs...

I finally managed to complete a working RFC9421 implementation... I didn't realize that Fedify's RFC9421 public key retrieval didn't include assertionMethod...

JSON-LD is difficult...

I check later...

https://github.com/boyter/activitypub

I have headache...

I want to display it somewhere...🤔

It seems the time has come to seriously consider migrating to another platform like Codeberg...

But, GitHub is also another side to it, that's a Social Platform. This is getting in the way migrating to Codeberg.

😕 https://github.blog/changelog/2025-12-16-coming-soon-simpler-pricing-and-a-better-experience-for-github-actions/

My docker network has so problem...

I remembered it wrong implementation as "implemention"...😅

Why don't recommend to implement ActivityPub from scratch

https://amase.cc/articles/en/why-dont-recommend-implement-activitypub/

By design, we expect that simply importing will add the model to the loader, but we haven't created the test yet...

Today new apmodel features:

• User can add and override (required inheritance the class) own model to loader (core models is can't override, show warning)
• apmodel supports to preload json-ld schema from local (example, schema.org, activitystreams 2.0)

I making next-version of apmodel, that uses pydantic for better validation and better loader.

Currently, this feature is either not implemented or not fully implemented:

• export to json is not avaliable

Additionally, some models have not been migrated to pydantic, so they cannot be used properly.

If you interested this, can read this branch: https://github.com/fedi-libs/apmodel/tree/pydantic

まぁPoCくらいは作ってもいいかもね

ActivityPub関係のリクエストをに別のサーバーがプロキシになって取得するようにできないかなーなんて思ったけど、信頼性とか鮮度の観点から厳しそう

やるとしたら、署名周りの問題や鮮度をどうするかっていうのが重要なポイントになる

I should more learn the English...

My first Rust project (in effect)

Since there was a library by PyO3, reading pyproject.toml wasn't too much trouble.

https://github.com/AmaseCocoa/libretto

Fixed already in this PR, Gemini has reading wrong text...🤨

https://github.com/hackers-pub/hackerspub/pull/165#discussion_r2468149490

😂

typo? (リアクションだと他n人になってる)

ActivityPubを一から実装するのをお勧めしない理由みたいな記事書きたい

By the way, I'm anxiety because, maybe have spell miss... (don't or can't?)

I don't understand why Mastodon is not pass signature...

I'd like a json-ld library like Calamus, but Calamus doesn't seem to be actively maintained... (Even if I wanted to use Calamus, it appears to have vulnerabilities)

Currently, apmodel does not uses any JSON-LD processor.

I should test to integrate pyld for apmodel...

😮 https://www.w3.org/press-releases/2025/new-logo/

Implementation of RFC9421 is complete, but unit tests have not yet been created and compatibility testing with existing implementations has not yet been performed.

RFC9421 is allowed multiple signatures? I saw that now...

Within today, I finish to make first-version of RFC 9421-implementation.

I'm interesting in FEP-fe34

Currently, apkit is experiencing a critical issue... It appears there are problems with interoperability with Mastodon... I'm investigating where exactly it is failing... (https://github.com/fedi-libs/apkit/issues/19)

However, I think I'll try to sleep today... If I keep researching, my day-night reversal will probably get worse...

Okay, I made experimental Flask integration:

https://github.com/fedi-libs/apkit-flask

Today new #apkit features:

• Added synchronous client
• New Abstract class AbstractApkitIntegration, This enables the creation of apkit integrations based on a somewhat formalized class.

today is improve the synchronous support in apkit

I currently making requets-based synchronous ActivityPub client for apkit...