support short urls

[derberg]

details of proposal are here where I consulted them with the community first

https://asyncapi.slack.com/archives/C34F2JV0U/p1716306515791259?thread_ts=1716306515.791259&cid=C34F2JV0U

wdyt folks?

[SGI-CAPP-AT2]

Hi @derberg, I would like to contribute. I want to know what are the technologies being used for backend for routing and database management?

[anshgoyalevil]

@derberg How about using a subdomain under asyncapi.com rather than a path under asyncapi.com/s/*

For example, go.asyncapi.com/*. There are many link shorteners out there that support custom domains and offer benefits like link tracking.

I have personally tried the free plan at https://short.io/

I also read the slack conversation, and seems like this redirect thing would serve the purpose too 🥂

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity :sleeping:

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience :heart:

[aakankshabhende]

@derberg I have opened PR for this. Could you please review https://github.com/asyncapi/website/pull/3311

[derberg]

@aakankshabhende I apologize for coming here so late. Had few hard months last Q3 and Q4. I left a comment in a PR

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity :sleeping:

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience :heart:

[NalinDalal]

so need to directly implement the feature? perhaps can you tell something more? @akshatnema i have implemented a basic url shortner in ts,

[Jaishree2310]

Hi @akshatnema, I need more context for this issue to solve if not already pr raised. Thanks!

[aeworxet]

Bounty Issue's service comment

Text labels: bounty/2025-Q4, bounty/medium, bounty/docs First assignment to regular contributors: 2025-09-19 00:00:00 UTC+12:00 End Of Life after: 2025-10-31 23:59:59 UTC-12:00

@asyncapi/bounty_team

The Bounty Program is not a Mentorship Program. The accepted level of Bounty Program Participants is Middle/Senior.

Regular contributors should explain in meaningful words how they are going to approach the resolution process when expressing a desire to work on this Bounty Issue.

[princerajpoot20]

so are we going ahead with this asyncapi.com/s/* approach? cc: @anshgoyalevil @derberg @sambhavgupta0705

[vishvamsinh28]

@aeworxet @sambhavgupta0705 I would like to work on this issue under the bounty program

[derberg]

@princerajpoot20 yeah, I think so

for me most important is not only implementation but also documentation - so it is super clear how to add short urls, and who manage them

probably under: https://www.asyncapi.com/docs/community

[aeworxet]

Following the expression of desire to work on this Bounty Issue, @vishvamsinh28 (githubID: 90895835) is an AsyncAPI Maintainer specified in the file https://github.com/asyncapi/community/blob/master/MAINTAINERS.yaml, so they fall under the first category in the prioritization list.

[aeworxet]

Bounty Issue's Timeline

Complexity Level	Assignment Date (by GitHub)	Start Date (by BP Rules)	End Date (by BP Rules)	Draft PR Submission	Final PR Merge Start	Final PR Merge End
Medium	2025-09-16	2025-10-06	2025-11-16	2025-10-19	2025-11-02	2025-11-16

Please note that the dates given represent deadlines, not specific dates; so if the goal is reached sooner, it's better.

Keep in mind the responsibility for violations of the Timeline.

Assignee: @vishvamsinh28 (githubID: 90895835)

[aeworxet]

Despite being responsive in DMs, @sambhavgupta0705 (githubID: 81870866) is currently experiencing capacity issues. Therefore, the Timelines of all Bounty Issues dependent on him

• https://github.com/asyncapi/website/issues/4187
• https://github.com/asyncapi/website/issues/2124
• https://github.com/asyncapi/website/issues/3005
• https://github.com/asyncapi/website/issues/3186

are frozen for an indefinite amount of time until those issues are resolved.

[aeworxet]

@vishvamsinh28 (githubID: 90895835), please provide an update to the PR of the Bounty Issue.

[vishvamsinh28]

collecting suggestions from community, would the PR for review soon.

[sambhavgupta0705]

@aeworxet I think we can move this out of Bounty Program

[vishvamsinh28]

yea, there isn’t much work to do in this issue, its just copy pasting using ai

[derberg]

I'm done commenting if this is bounty or not, did it already in https://github.com/asyncapi/website/pull/4491#issuecomment-3448985199

what I do not like is statements like copy pasting using ai because it means you do not respect maintainers that will do the review of your PR.

docs are equally important as code, if not more. You don't just generate them and copy paste as later you get multiple comments like you already got in https://github.com/asyncapi/website/pull/4491

you can use AI but you should later review what you generated, there are guidelines you should follow and styleguide that you should respect. If you do not want to read them, then make sure at least that your AI have them in the context and respect them when generating docs with funny emojis.

docs about short URL should be present in https://www.asyncapi.com/docs/community so they are easy to access for community members and are searchable. You do not have feedback from community where to place them? then you check it on your own, you clone community repo, you investigate where to put docs, you put them in, then you need to figure out how you can test if this will render correctly in the website. There is a lot of steps to do, a lot of investigation, and maybe outcome is just some markdown - it is still important job to do. Such document could also be shared with community so they know what to do. Things like https://www.asyncapi.com/tools/generator could be updated so https://bit.ly is no longer used.

and yes, I'm angry when I see someone do not respect docs as job that is worth the effort and simply copy/paste from AI.

so let me challange you, is this an issue that should not be under bounty, or maybe you should not work on that issue 😄

[vishvamsinh28]

hey, my bad i didn’t mean to make it sound like the work isn’t important. sorry for not taking it seriously earlier. I’ll continue working on it properly, follow the guidelines, and make sure I put in the right effort this time 🚀

[aeworxet]

@sambhavgupta0705, could you please confirm whether this GitHub issue should be removed from the Bounty Program, since the chatter after https://github.com/asyncapi/website/issues/3005#issuecomment-3490902788 calls this decision into question?

[vishvamsinh28]

@aeworxet i'm working on the issue

[aeworxet]

Should this Bounty Issue be reclassified to Docs to reflect the factual order of things?

[vishvamsinh28]

yes