xilopaint

@slyfox I need the Alfred Debugger output as well.

@slyfox Now I see I committed a mistake when packaging the workflow. Could you delete your copy, download it again and tell me if it works?

@slyfoxTo get support you need to post the !diagnostic keyword output.

Update v0.4.0 New Features (ENH) Add live broadcast search (#4) Full Changelog: https://github.com/xilopaint/alfred-youtube/compare/v0.3.0…v0.4.0

You need macOS Ventura to run the latest workflow version. It seems v0.1.0 might work with some older versions of macOS according to this post:

What version of macOS are you running?

@Faris Najem You need to post the Workflow Debugger output.

v0.1.0 was the only uncompiled version. If someone has the same issue on Ventura with the latest version, I'll investigate it.

This suggests the Foundation framework version present in Monterey lacks a symbol needed to run the workflow. If you can't upgrade your system, I'm afraid there's nothing we can do.

@vitor, would it be possible to support the Arc browser?

@BenjaminO, would it be possible to make this workflow set colors to folders like this App Store application?

I still have an unnamed window when the app is maximized.

hmmm, I assumed it was possible because it's the approach of the nice Swift Windows Switcher workflow. Looking at it more closely, I now realize that it seems to use AppleScript for the tabs.

@vitor, would it be possible to also make this work with tabs through a different keyword?

Is there a documentation of the new API?

@vitor Has the API changed? I see the suggestions are greatly improved since the last update.

The issue has been fixed on macOS 13.4.

Update v0.3.0 New Features (ENH) ENH: add playlist search (#3) Full Changelog: https://github.com/xilopaint/alfred-youtube/compare/v0.2.0…v0.3.0

The workflow is no longer available in Alfred Gallery and will be updated in the future through OneUpdater. I requested its removal because the Gallery doesn't accept non-notarized binaries. Using uncompiled code has performance and development limitations. Good news is that the workflow will be faster from now on (~40% faster). If you downloaded the workflow from Gallery I suggest you to download v0.2.0 from GitHub. Future updates will be automatic.

Update v0.2.0 New Features (ENH) Add channel search (#1) Add auto-update capability via OneUpdater (#2) Full Changelog: https://github.com/xilopaint/alfred-youtube/compare/v0.1.0…v0.2.0

Just installed. Thanks!

@jjaybe this workflow would be even more useful if it could reveal the data and cache folders of the workflows in Finder. I often find myself navigating to these folders to clear their contents. If you do this, please release the workflow.

Warp offers command suggestions which is different from simply executing commands using natural language. It's safe because you can check in advance what you're running. I can't understand what you mean by "manage third-party programming languages". Do you mean Alfred workflows? Checking a workflow usage frequency is a trivial task. It's not necessary to have any kind of AI for this. Another trivial task that has nothing to do with "AI". I can't understand why you keep talking about "updating programming languages" as if it were a complex task. It takes literally two words for having everything up-to-date: Again, you can't execute this kind of tasks using natural language without checking in advance what is being executed because it's not safe. It's not how Warp, that you used as an example, work. This is a trivial task that can be easily achieved with ChatFred. You can even attach a hotkey to it. I'm not advocating Alfred shouldn't use AI. Maybe the only point I agree with you is that it could offer integration to the new OpenAI's language models, either via API or a paid plan. In any case I think a new UI should be used for the integration.

AI can't help you with this. You can do this by using only two words: "brew upgrade". What do you mean by this? Alfred has recently introduced update capability for workflows through Gallery. How could AI be helpful in "verifying working and obsolete workflows"? This is not something language models should be used for. You can't rely on some unpredictable language model whose response you don't know in advance to perform any kind of terminal task. This can lead to disastrous results. Which tasks? This is a field where language models can be useful. While you can use ChatFred for this I personally think Alfred cannot currently offer a decent AI experience through workflows because of the lack of proper UI elements. I've been a loyal Powerpack user since v2 and have colleagues who purchased Alfred just because I convinced them. During this time I had never felt the need of a substancial change in the core concept of Alfred. This has changed. A couple months ago I installed an Alfred competitor for the first time just because it offers a better AI experience. Having both launchers installed forced me to live with multiple annoyances. They start by dealing with two different shortcuts whereas I only had one before. Also, now I have to deal with thoughts like "what's the best launcher for this task?", or "to which launcher should I create this extension/workflow for?". All these questions push me to make a decision and choose a single launcher. I still think Alfred is more straightforward for most tasks. There are some small details that make me prefer Alfred's UX: the font sizes are just perfect and I love the visual appeal of the big icons in the results. In some way Alfred feels more seamless to me, even relaxing, and it delivers what I want as a good and efficient butler. That being said, I think a good AI integration is important. Alfred is a one-time purchase software and as such it depends on new purchasers. With the competition offering extensions for free and AI through a subscription model people may see more value in spending money to get what they don't have for free and it makes me worry for Alfred's future.

Update (v4.3.1) Fixed bugs in workflow objects.