Redirect mentions with unknown id on the site. #44

New issue

Open

opened 2024-11-06 11:00:08 +00:00 by Rubicon · 2 comments

Rubicon commented

2024-11-06 11:00:08 +00:00

Owner

<span class="h-card" translate="no">
  <a href="https://mastodon.social/@gamingonlinux" class="u-url mention">
    @<span>gamingonlinux</span>
  </a>
</span>

Figure 1: sample HTML from the server

Included:

Bio & account fields on profile page (might have mentioned accounts here)

This is originally part of #5, but for this we need better infra to handle this thing. Since in some cases we don't actually know the mentioned acct id on the site (see figure 1), we need to use the API with the webfinger for the id. In this process we must allow user to wait or even cancel. <figure> ````html <span class="h-card" translate="no"> <a href="https://mastodon.social/@gamingonlinux" class="u-url mention"> @<span>gamingonlinux</span> </a> </span> ```` <caption>Figure 1: sample HTML from the server</caption> </figure> Included: - [ ] Bio & account fields on profile page (might have mentioned accounts here)

Rubicon added the

feature

proposal

label 2024-11-06 11:00:08 +00:00

Rubicon referenced this issue

2024-11-06 11:02:05 +00:00

Page for Profile #5

Rubicon commented

2025-01-16 15:00:51 +00:00

Author

Owner

Now the profile page supports opening with the webfiger. This feature can be implemented with that.

I am wondering, if we need to parse the content and render it with our own semantic. It's clear we can have better control on this path.

For now we rely on the UA to render the html content, it's very tricky to implement additional features on it.

Now the profile page supports opening with the webfiger. This feature can be implemented with that. I am wondering, if we need to parse the content and render it with our own semantic. It's clear we can have better control on this path. For now we rely on the UA to render the html content, it's very tricky to implement additional features on it.

Rubicon commented

2025-01-16 15:01:25 +00:00

Author

Owner

Now the profile page supports opening with the webfiger. This feature can be implemented with that.

I am wondering, if we need to parse the content and render it with our own semantic. It's clear we can have better control with this path.

For now we rely on the UA to render the html content, it's very tricky to implement additional features on it.

Now the profile page supports opening with the webfiger. This feature can be implemented with that. I am wondering, if we need to parse the content and render it with our own semantic. It's clear we can have better control with this path. For now we rely on the UA to render the html content, it's very tricky to implement additional features on it.