mjwalfreds

I want to exclude one app Tweetbot so that when I search for it in Alfred, nothing is returned.
 
The reason I want to do it is that I work in Focus sessions similar to Pomodoro where I block all distracting things for 1 and half hour and focus on what I need to do. Only issue is that I sometimes do want to post a tweet and thus use Tweetbot's create tweet action.
 
I activate Tweetbot app with Keyboard Maestro macro that will not open Tweetbot when I am in the focus session because I create a file at start of Focus session and erase it in the end. The macro looks like this if anyone is interested: 

 
However I still can access Tweetbot quickly from Alfred and I want to block that.
 
Is there a way to blacklist an app from Alfred search?
 

I think you can also add an alfred:ignore comment to the application if you don't want to delist it from Spotlight completely.

System Preferences → Spotlight → Privacy. Drag Tweetbot to the list in that pane. Alfred Preferences → Advanced → Clear Application Cache.

Done.

This is awesome! I look forward to experimenting with this. Thanks!

For those who are interested I have created a workflow for running iOS shortcuts from Alfred using a spare iOS (12.0 or above) device (I use a second hand iPhone SE).
 
Here is a short video I have published to Reddit:
 
This workflow requires a Siri Shortcut to get a list of your shortcuts:
https://www.icloud.com/shortcuts/f8dcbc7ac14f4d03b1fc3bcebf28b2f5
 
Once the workflow has been imported you will need to put your Pushcut Webhook Secret key into the "api" variable by typing !pushcutapi in Alfred and then type into Alfred !pushcutupdate and Helper shortcut will start to do it's job. Once the shortcut has run you should be able to access your shortcuts within Alfred like on my video above.
 
It currently support 3 different modes.
Using the keyword "pushcut" or keyboard shortcut: control+option+P will just run the shortcut and won't return any data. It's good for shortcuts like "Turn on the fan" Using the keyword "pci" or keyboard shortcut: control+option+I will ask you to select a shortcut and give it some input (input is optional), return the shortcut output in Large Type Using the keyword "pcd" or keyboard shortcut: control+option+D will ask you to select a shortcut and delay it. 5s , 5m , 5d ...  
Link to the workflow:
https://mega.nz/file/6OxhjILb#N1ntqJIWfM539UdVVYq1gwfrnB6YmRfbbuc5hrA1Rl0
 
This is an unofficial workflow, I am NOT affiliated with Pushcut.
 
This workflow requires:
A spare iOS device (min iOS 12 and above, recommended iOS 13 and above), A subscription to Pushcut Automation Server, more info on the developer's website: pushcut.io  
Link to the wallpaper:
http://getwallpapers.com/wallpaper/full/a/2/2/1516267-download-free-star-wars-star-destroyer-wallpaper-3554x1999.jpg
 
Feel free to use and maybe improve this workflow. 
 
Update:
ver 1.0.3:
Making it clear that this workflow is using your Pushcut Webhook Secret instead of an API key (it can be found at Pushcut -> Account -> Webhook) Removed unnecessary update commands, now the only way to update the list of shortcuts is to type !pushcutupdate directly to Alfred. Added ability to copy shortcut output into clipboard, when using keyword "pcic" or the keyboard shortcut : Shift+Option+I Added ability to remove your list of shortcuts from the workflow with the keyword !rmshortcuts , in case if you wanted to export it for sharing. Fixed the !pushcutapi did not require argument.

One other note re Pacmax - the design could be tightened up a lot - there’s quite a lot of white space e.g. on every page there’s a big open area with a horizontal line and then the page title in a huge font, and only below that is the actual content.  I’d also prefer one workflow per line in results, rather than needing to read down newspaper columns.  And it would be nice to keep the search box in view even when you scroll down (an issue currently exacerbated by the multi column format).

I think my alfred workflow list is a bit cleaner than Dave's but thats my opinion.
 
The tool I wanted to build was also what Dean had in mind. It should be automated to get info from GitHub first and foremost with additional submit ability.
 
I wanted to build some hook in system to map a workflow to github releases and have the site update from that.

Although not all distribute workflows via github releases and some dont distribute via github at all.

Discussion continuing in
 

Here is an AppleScript that polls System Events for all running apps and pops up a list for you to choose which apps to quit:
tell application "System Events" set processList to ¬   (name of every process where background only is false) & ¬   (name of every process whose ¬    (name is "AppName") or ¬    (name is "AnotherAppName")) tell me to set selectedProcesses to choose from list processList with prompt "Select process(es) to quit:" with multiple selections allowed end tell if the result is not false then repeat with processName in selectedProcesses   tell application processName to quit end repeat end if You can select multiple apps to quit by using the ⌘ or ⇧ keys as well.
 
Just make a new workflow and pipe a hotley or keyword into the script above.
 
Original found HERE

Hi again all! Just wanted to follow up on a few improvements I've made to Pacmax with your feedback. Have even more in the works for hopefully later this week that should be even more exciting. Here's what's new, though:
 
- Added: Created By field on posts (links to the author's GitHub profile) - this might be my favorite addition
- Added: A scroll to top button for long pages
- Fixed: Rewrote About page to help better explain different aspects related to PM & Alfred; also created a GitHub repo for anyone interested in helping make About better!
- Fixed: Styled README section of posts make clearer that they're from the project's repository
- Added: Support for wider screens on Explore (fill it up!)
- Fixed: Pagination on Explore
- Fixed: Last Updated field displaying wrong time
- Improved: Several styles across the site
 
Check out the changes at https://pacmax.org/
 
Thanks!
 
P.S. Great reading all the conversations here. I look forward to more!

If there is any missing emoji, feel free to open an issue on the repo

@unitof Alfred is showing the actual location of the apps as passed back to him by macOS when searching.
 
I'm going to be adding a bit of logic to be able to show the virtual locations of the apps (/Applications/.../) in a future release.
 
Cheers,
Andrew

@MVR London Did you type "reload" into Alfred? This will refresh the app cache for any apps that may no longer exist in the old location.
 
Cheers,
Vero

Hi again all! Just wanted to follow up on a few improvements I've made to Pacmax with your feedback. Have even more in the works for hopefully later this week that should be even more exciting. Here's what's new, though:
 
- Added: Created By field on posts (links to the author's GitHub profile) - this might be my favorite addition
- Added: A scroll to top button for long pages
- Fixed: Rewrote About page to help better explain different aspects related to PM & Alfred; also created a GitHub repo for anyone interested in helping make About better!
- Fixed: Styled README section of posts make clearer that they're from the project's repository
- Added: Support for wider screens on Explore (fill it up!)
- Fixed: Pagination on Explore
- Fixed: Last Updated field displaying wrong time
- Improved: Several styles across the site
 
Check out the changes at https://pacmax.org/
 
Thanks!
 
P.S. Great reading all the conversations here. I look forward to more!

Yeah, I mostly use neovim. But of course I use Xcode, too. If I want to write a good GUI app, then I should start with a good GUI library. And then I use the editor/IDE that works best with that library.
 
I'm trying to write halfway decent software, not have a great time writing a turd. I don't see any point in epic productivity gains if, in the end, that leads to producing crap.
 

@ollieread We have discussed such a system in the past, more than once (here’s one such case). You’ll see there was at one point a tool that did just that.
 
I’ve thought about it a lot and always circle back to a Homebrew Cask-like system, where you have definitions for Workflows and their download locations that are interpreted by the tool and used as downloads. Yes, the definitions have to be updated when a new version of the Workflow is release (depending on the method), but in practice that can be automated with minimal effort.
 
My most recent idea (which I haven’t yet written about and could tie-in to yours) was a similar system where we’d just have Workflow definitions in a JSON file (or anything, really), such as Workflow Name, Workflow ID, Workflow Source, Author Name, Author Website. It’d be a Github repo, so anyone could contribute info about any Workflows, even the ones that are only hosted on Packal or a personal server. It’d then be a kind of central hub/database where other systems (like a CLI installations utility or a website like Pacmax) could “drink” from.
 
That would be a true community effort that could solve the plaguing problem of abandoned systems for sharing Workflows. Any new one would save themselves a ton of work gathering data and could focus on the interface and features

I am planning to prioritize the .alfred file types, but have the releases available for download. What do you think?
 
 
Respectfully, I didn't say I won't support monorepos, that I'd focus on GitHub Releases first. By having Pacmax look at Releases I'd be doing the opposite of being the one to manually add the .alfred file types; PM is going to be doing the heavy lifting. I didn't say that Pacmax would ever look at GitHub. It seems like a great place (if not the best place) to start, to me. If it helps: The Share form is not any core functionality. It's a way for people to communicate what packages they'd like to see on the site while I was getting the ball rolling (namely getting the site to be a leaner experience altogether). Automation has always been on my mind, but it was important for me to get feedback from the start. I'm glad I did because without the community's feedback I wouldn't know what to tackle next (and it has helped a lot).
 
Your concerns don't escape me, and I respect them, however this is a new project and I hope anyone interested in it can see that I am scratching the surface. To reiterate, I'm not discounting building beyond GitHub—it feels like a great place to start (and I've got to start somewhere). I'm not expecting to be manually managing the site much longer; that's not realistic—but I didn't make that clear. I hope that better explains my position.
 
All the best,
Max

Presumably if any automated solution based on github is to work, there would need to be a standard for how Alfred github repos are structured.

I’ve reread that multiple times and can’t decipher what that mean in practical terms. 1. How are you making the adding os packages “more accessible”? 2. In what way are the current solutions not accessible enough? Right now your solution seems less accessible, because you’re a gatekeeper to whatever gets added to the site.
 
And you haven’t answered my previous point: 3. if I want to submit to Pacmax, am I supposed to dump almost 50 Workflows on your lap lap for you to go through? 4. Are you the one who decides which Workflows are added to the website? 5. If yes, why, what’s your criteria for inclusion or refusal?
 
If you are curating, that would indeed make Pacmax the same as Awesome Alfred Workflows and far from a Packal replacement. Packal wanted to be the central repository where everyone could share their Workflows. The biggest problems with Packal are that it asks for too much information for a submission and is buggy. Had it been bug-free, we wouldn’t even had noticed it was abandoned nor would we be needing an alternative. But it still works, even if crippled. Manual addition, by comparison, will only work for as long as you’re excited with the website, and that makes me worry for its longevity.
 
That’s my biggest eyebrow raise with Pacmax right now: it isn’t clear (and specific) about what it is or what it wants to be. Awesome Alfred Workflows is shameless about being a subjective biased list: it’s a particular kind of list (from the “Awesome” series) connected to a specific person, and mentions curation right away. Packal is automated and lets anyone submit whatever they want. Pacmax, I don’t know.
 
The optimistic news is you seem like a nice person with a true desire to make something good. Make no mistake, I see Pacmax as having positive potential. But it’s common for projects to die for lack of enthusiasm, and with the subject of sharing Alfred Workflows, every time that happens we get worse off. People submit to what is popular at the moment, and when that dies off most don’t jump on the next thing, so we keep losing Workflows in the process.
 
So I hope you understand where my worry comes from and why I have some reservations (and many questions) about what Pacmax is and what it wants to be. But I also want to make it clear that I thank you for at least trying, and I understand these may only be your first steps.

To get a discussion going and hear what the community thinks. I am not the one to judge what people should do, they can decide for themselves.
 
For all we know, the tool might be using some crawler (spider) under the hood already or has one planned.
 
And for another point, it's currently the best website to fill Packal's void. And it has a search that works. Packal is also closed source for whatever reason. 

Morning all! I've suggested to @mjwalfreds to join this conversation, so he can chat with some of our most experienced and active community members, so I'm sure he'll come and introduce himself soon
 
Cheers,
Vero

It's called Pacmax. Saw it posted on Reddit.
 
I was actually thinking of building it but glad that I don't have to. 😅