That’s great, glad that worked as intended!

I pushed an update last night that added a settings page that includes all the URL Schemes for Arctic. I need to clean it up a bit, and I’ll probably add some more schemes for things like search, tab selection, post and comments by ID, etc. but at least for now there is a home for displaying the schemes.

The lemmy API is quite easy to use, you could even skip login by copying the JWT from another session to authenticate the custom connector (unless you can prompt for username and password in the connector) either way, it should be achievable.

This is a strange one that I haven’t figured out just yet. It doesn’t seem to be related to it being a crosspost. Was it displaying video controls (play button) but not playing, or did it just render as an image with no controls?

I have stumbled across similar issues, but I can’t consistently reproduce the issue for testing. I’m thinking it has to do with the video player failing to load the video, and then not retrying. For a while I was thinking it may be an issue causing video controls to show up on image posts, but now I’m thinking it’s just videos failing to play.

I’ll look into this further and see if I can’t figure out what is going on.

I’m not sure if I have this one completely fixed or not. It’s difficult to debug. I’ll keep working on a proper fix for this, but yesterday’s update should have improved this behavior.

Alright, I’ve added support for filtering communities and instances based on the defederated list for the active instance. I’ve also added support for blocking communities and instances straight from Lemmy Explorer.

This will be included in the update later on this evening. Thanks for the ideas!

The regex update did not work, I broke it myself. For some reason, just the presence of an emoji cases the cursor to jump, even when the text is not changed by the regex. Instead, I ended up storing and restoring the cursor position during the check.

I’m not sure why it behaves this way, but the fix seems to work just fine, so I’ll just leave it alone.

Alright, I have this fixed now. Deleted posts will show a badge in the UI. The delete action will now act as a toggle to delete or restore the post.

Indeed it does happen for regular text as well. Basically, if the title contained an emoji, the cursor would jump to the end after every change.

This was caused by stripping line breaks from the title field. I was able to fix this simply by updating the regex.

So the comment state issue was due to a regression, I had this working at one point and broke it in an update. This was a simple one-liner fix.

The stale state for save actions, I don’t believe I ever fixed this issue before, nonetheless it is fixed now. I was actually able to apply the exact same fix as the comment actions.

I frequently use the action popup menu, so it’s rather surprising I had never noticed these state issues before.

Alright, I’ve figured out the issue here. When a post is deleted, it still appears for the original poster. So, the first time you deleted the post, it worked, but the second time, an error message is displayed, essentially stating that you can’t delete a post twice.

To resolve this, I need to update the UI to show that the post was successfully deleted and disable the delete action for already deleted posts.

I haven’t forgotten about this, it’ll I just haven’t had the energy after work this week to implement this. I’ll probably get to this on Monday.

I pushed an update last night that adds support for searching block lists and browsing blocked content. For now I just allow opening the content in the browser, but as I roll out the new API integration I’ll add support for opening the content in-app. I also made a few other minor improvements such as icons for the blocked lists, and counts to show the total blocked for each category.

This was a super simple fix, I’m going to see about patching a few other issues, and then I’ll roll out an update.

I seem to remember adding support for this ages ago, perhaps I am mistaken, or I broke it in an update without noticing. I’ll look into it and get back to you. Either way, this should be a super simple fix, thanks for letting me know!

Yes, Arctic does support URL schemes. I made it as simple as possible, no need to grab the post_id or comment_id. Just simply pass it the URL to any post, comment, user, or community. This also works for most MBin URLS. The url scheme for Arctic is arctic://open-in?url=%7Bcontent_url%7D for example to open this post you’d use arctic://open-url?url=https%3A%2F%2Flemmy.world%2Fpost%2F25543739

Tapestry looks interesting, it’s been a while since I’ve found any rss readers that I actually enjoyed using, I’ll have to check that out. I definitely like that it supports URL schemes rather than opening in a browser.

Looking at the Tapestry documentation, you will likely want to use the __URL_ENCODED__ substitution variable for Arctic eg: arctic://open-in?url=__URL_ENCODED__

I should probably add a section in Arctic settings to list the supported URL schemes. Right now they are only listed in the Changelog, and they are all buried.

If you have any issues with it feel free to let me know know and I’ll help you out, or add new schemes if needed.

Glad you’re enjoying Arctic!!

If it is happening for regular text, I would assume it is caused by the same issue, so fixing one should fix the other. hopefully.

Just a little update on v1.0 support. I spent yesterday writing a parser for the v1.0 api that generates a swift library for me that is compatible with Swimmy for handling requests. In testing, it looks like everything is working except for image upload methods. For uploads I’ll need to update the parser for generating these requests. Now I just need to write a compatibility layer to map the responses into a common format for Arctic.

I’ve never noticed this one before either. I can reproduce this issue when inserting an emoji, but not regular text.

I’ll look into this, I don’t think I am doing anything special with the title field to cause this. As always, thanks for letting me know!

Oof, I must have broke something in an update without noticing. I’ll see if I can’t patch this tonight and release an update. Thanks for letting me know!

That’s a new one, I never noticed this before. I’ll either need to disable navigation while presenting popups, or make touches outside the popup dismiss the view.

I’ll look into this, thanks for letting me know.

For uploading to catbox.moe, you’ll need to go to (Settings -> General -> Upload Destination) from there you can choose Lemmy, Catbox, or Ask each Time. This defaults to Lemmy.

As for extracting the media url when posting a link, I’ll need to look into this a bit more. It’s a great idea, however some media links include an authentication token that expires after a predefined amount of time. This would in turn result in broken links after the time is up. I’ll see if I can’t work out a way to parse these links and see which ones are safe to directly embed. It’s definitely annoying to post links that are not easily viewable from other clients, I’ll see what I can work out on this front.