Notices by 洪 民憙 (Hong Minhee) (hongminhee@todon.eu), page 12

@mjgardner I don't think so, because revealing that a version is unstable by notation is not a bad idea for many users, it just might not be what you need.

We have a space on #Matrix for the #Fedify community, so if you have any questions, feel free to join us and ask!

https://matrix.to/#/#fedify:matrix.org

@mjgardner Oh, right, the pre-release I'm talking about is a pre-release as defined by Semantic Versioning, which means it's not guaranteed to be stable.

@mjgardner If you want to publish a pre-release version to npm, it's simple. Just use a pre-release version (in accordance with the definition of Semantic Versioning, e.g., 1.2.3-dev.123) and tag it with anything other than latest (you can specify a tag with npm publish --tag option).

Progress Report, March 31, 2024.

Fedify is now available on npm. The package name is @fedify/fedify, exactly the same as the JSR.

Added Deno KV adapters: DenoKvStore and DenoKvMessageQueue. Although they can only be used with Deno.

Fixed a few places in the docs to match the changed API.

I did a quick test in Node.js and Bun and found it works well.

It was pre-released to npm as version 0.5.0-dev.95+46f77429, and you can test it out:

https://www.npmjs.com/package/@fedify/fedify/v/0.5.0-dev.95

I did a quick test without expectations, and found that #Fedify works great with #Bun as well! The version I tested was 0.5.0-dev.95+46f77429.

https://www.npmjs.com/package/@fedify/fedify/v/0.5.0-dev.95

A pre-released version of #Fedify is now available on #npm!

https://www.npmjs.com/package/@fedify/fedify/v/0.5.0-dev.90

Progress report, March 30, 2024.

I tried #CommonJS packaging, but it turned out to be quite challenging, so I decided to support #ESM only.

I got #Fedify packaged into npm using #dnt, but it hasn't been published to npm yet.

I've made the entire unit test pass in Node.js now.

It was pre-released to JSR as version 0.5.0-dev.86+31d077e4, and you can test it out.

https://github.com/dahlia/fedify/discussions/24#discussioncomment-8958020

@root 거의 같아요. 氣象은 좀 더 學術適인 語感이 있고, 날씨보다 總體的인 現象을 가리킨다는 느낌이 있어요. 날씨에 좀 더 가까운 漢字語는 日氣인데 이 말은 口語로는 거의 안 쓰는 것 같아요.

@ayumisato 多分BlueskyはActivityPubではないので今後も無理だと思いますが、Threadsは今はまだだけど今後実装される可能性が高いと思います。 MisskeyとMastodonの間では、既に引越しが出来るようです。

Is there any way to force #jose to use the Web Cryptography API backend in Node.js?

@gwil It would be nice if dnt's deno shim would also replace the Deno KV API with the @deno/kv package, which @thomasreggi tried to do late last year, but unfortunately it didn't merge.

https://github.com/denoland/node_shims/pull/164

Progress report, March 29, 2024.

Work on Node.js compatibility is currently being done in the dnt branch (the branch name may not be appropriate, but I like it because it's short).

I've added the dnt.ts script in the root of the repository. It's not working yet—I'm getting the error below, and I'm trying to figure out a solution:

TS2725: Class name cannot be 'Object' when targeting ES5 with module CommonJS.

I added KvStore and MessageQueue interfaces, an abstraction layer for key-value storage and message queues. Although there are a couple of implementations for development purposes called MemoryKvStore and InProcessMessageQueue, they are not meant to be used in production.

I haven't implemented an adapter for Deno KV yet, so it is not usable in #Fedify. Implementing the adapters for it itself isn't hard, it's the packaging that's the problem. Anyway, this regression is only temporary during development and will go away in the general release.

It was pre-released to JSR as version 0.5.0-dev.79+562c62cf, and you can test it out:

https://jsr.io/@fedify/fedify@0.5.0-dev.79+562c62cf

https://github.com/dahlia/fedify/discussions/24#discussioncomment-8948476

#Deno doesn't support Windows ARM64 yet, so I need to use the Linux AArch64 version of Deno inside #WSL to get up to speed in it.

https://github.com/denoland/deno/issues/13331

@gwil That phrase, I'm going to have to use it in Fedify!

@teleclimber Even though I've decided to work on Node.js compatibility, I'm still going to use #Deno as my primary development runtime—the developer experience in Deno is too good to resist.

I was quite impressed with the result of the above poll, and am going to work on the non-#Deno compatibility of Fedify for the time being. Here's #Fedify's rough roadmap:

https://github.com/dahlia/fedify/discussions/24

#fedidev #ActivityPub

@ch0ccyra1n like https://github.com/sfomuseum/go-activitypub from @thisisaaronland - exciting times!

I expect (hope?) we'll see a lot of these. Like apache/nginx/etc and the many micro web frameworks in every language. 😁

Fedify 0.4.0 was just released! Here are the highlights of the changes:

• Added a step-by-step tutorial.
• Integration with the Fresh framework has been made much simpler.
• Added authenticated document loaders: within personal inbox listeners, Context.documentLoader is now automatically authenticated.
• Improved the ergonomics of the vocabulary API.

https://github.com/dahlia/fedify/releases/tag/0.4.0

@lapy @root 「오프모임」이라는 말도 써요.