hongminhee, 13 days ago

If you already have Deno installed on your system, you can try the fedify command now:

deno install -A --unstable-fs --unstable-kv --unstable-temporal -n fedify jsr:@fedify/cli@0.8.0-dev.152+7dc1eb38

hongminhee, 13 days ago

I've done some basic documentation on the fedify command:

https://unstable.fedify.dev/cli

hongminhee, 12 days ago

Fixed a bug that the option -a/--authorized-fetch did not work on Windows.

hongminhee, 12 days ago

The second feature of the #Fedify #CLI that I'm working on is ephemeral inboxes.

#fedidev #ActivityPub

hongminhee, 11 days ago

The fedify inbox command, which will be shipped in the next #Fedify release, is a tool that creates an ephemeral #ActivityPub server so that you can debug and test the activities you send.

Here's a demo of it.

https://unstable.fedify.dev/cli#fedify-inbox-ephemeral-inbox-server

#fedidev

The demo video of the

mariusor, 13 days ago

@hongminhee I like the part of "spinning up a temporary ActivityPub server", but how does that work? The key needs to be reachable from the internet, so DNS and such must be already set up.

hongminhee, 13 days ago

@mariusor It depends on a public local tunnel service under the hood, haha. Here's my module for that:

https://github.com/dahlia/localtunnel

mariusor, 13 days ago

@hongminhee I see, but is that safe to disseminate as part of a library? Meaning that multiple developers will be making use of those services through - what I assume to be - your account.

hongminhee, 13 days ago

@mariusor First of all, the library itself does not have this feature — only the CLI toolchain has it.

And these services fortunately do not require signing up! So it does not share any account of them.

mariusor, 13 days ago

@hongminhee TIL. Thank you.