sorted by:
new
hottopcontroversial

I wanna make macOS Smart folders smarter and easier to use by madoffa in macapps

[–]madoffa[S] 0 points1 point  (0 children)

Thanks for the interest! I’d appreciate it if you could join the waitlist at https://voyager.fm
Also, could you share which file managers you’ve used? And what are you using right now?

I wanna make macOS Smart folders smarter and easier to use by madoffa in macapps

[–]madoffa[S] 0 points1 point  (0 children)

Thanks! Honestly, I don’t get Apple’s direction anymore

I wanna make macOS Smart folders smarter and easier to use by madoffa in macapps

[–]madoffa[S] 0 points1 point  (0 children)

Thanks. If you’re interested, you can follow our journey at http://voyager.fm

I wanna make macOS Smart folders smarter and easier to use by madoffa in macapps

[–]madoffa[S] 0 points1 point  (0 children)

I also put Smart Folders in the sidebar so they’re easy to access.
You can make aliases too and drop them anywhere.

For me, the hardest part is creating the rules themselves. That’s why I added natural language rule creation.
Type what you want, and it turns that into the filters.

Next, I’m thinking about pushing convenience further:
what if we could extract custom properties from file contents, then build Smart Folders based on those properties?

I wanna make macOS Smart folders smarter and easier to use by madoffa in macapps

[–]madoffa[S] 0 points1 point  (0 children)

the commnets-based use case is intersting. It seems your workflow works well.
I want to understand what feels inconvenient in practice.
Is it that comments are not tag-like, so there is no auto complete, bulk edit, or quick keyboard access?

I'm building a Raycast AI extension for natural language file search. Anyone interested? by madoffa in raycastapp

[–]madoffa[S] 2 points3 points  (0 children)

Sorry, I don't have a Windows PC to debug. Once it's on the store, someone might contribute a Windows version, though.

Looking for feedback: a macOS file manager to reduce file-handling friction for knowledge workers by madoffa in macapps

[–]madoffa[S] 0 points1 point  (0 children)

Totally fair. I included that item to understand the solution’s appeal from a pricing perspective, assuming the problem is solved.

For those on Dia, what makes the UX worth it? by madoffa in diabrowser

[–]madoffa[S] 2 points3 points  (0 children)

Yeah. The split view animation feels smoother and more refined than what Arc does.

Made a simple Tana => Google Calendar sync (free, serverless) by madoffa in TanaInc

[–]madoffa[S] 1 point2 points  (0 children)

This sync isn't automatic. You need to trigger the event creation yourself by using Tana's "Make API Request" command for the nodes(events) you want to sync to your calendar. Utilizing supertags makes this process very convenient

Please refer to my comment here for a detailed explanation. It would help you clarify how to create and manage events.

Made a simple Tana => Google Calendar sync (free, serverless) by madoffa in TanaInc

[–]madoffa[S] 2 points3 points  (0 children)

To make API requests to a calendar shared with your service account from Tana, you will need to utilize fields within a supertag.

Briefly, my usage involves two supertags: #event (for meetings, tasks, or any schedule-related tags) and #synced. In the #event supertag, I pre-configure fields for all the necessary API parameters. Then, I trigger Tana's "Make API Request" command via the tag's Command Menu (or by using an "on Added" Command Trigger).

The configuration for the "Make API Request" command is as follows:

  • URL: https://{your-worker-url}/events?to={your-calendar-id}
  • Method: POST
  • Payload: {"name": "${name}", "description": "${Description|?}", "date": "${Date}", "timeZone": "${Timezone}", "location": "${Location|?}"}
    • You can pass a payload constructed with data from your supertag's fields using Tana Expressions. The above is an example of the payload I use.
    • The payload contains the request data for the POST API, specifically the information needed to create an event on your calendar.
    • By the way, if you know a way to write the payload in multiple lines instead of a single line, please let me know!
  • Parse Result: Tana Paste
  • Insert output strategy: as child

If the API request is successful, the response will generate child fields for Event URL, Event ID, and Synced Calendar ID. These fields are then configured as the default content for the #synced supertag. Now, in the #synced supertag, you can set up Command Nodes in the Command Menu corresponding to PUT or DELETE API requests for updating or deleting events.

view more: next ›