Media is too big
VIEW IN TELEGRAM
I launched a Mac app in February. Four months later, a copycat replicated it and is selling/advertising it...
https://redd.it/1vr6ac1
@macappsbackup
https://redd.it/1vr6ac1
@macappsbackup
[OS] DemoTape: tell your coding agent what to demo and get a finished video, no timeline editor required
https://redd.it/1vr7hpx
@macappsbackup
https://redd.it/1vr7hpx
@macappsbackup
Reddit
From the macapps community on Reddit: [OS] DemoTape: tell your coding agent what to demo and get a finished video, no timeline…
Explore this post and more from the macapps community
FileFerry: FTP, FTPS, SFTP, WebDAV, SMB and a real SSH terminal in one native macOS window — free beta
I'm the developer, working alone on this, so treat the below as what it is — someone showing you his own app.
What it is:
A native macOS file transfer client — no Electron — that speaks FTP, FTPS (explicit AUTH TLS), SFTP, WebDAV and SMB, and opens a full SSH terminal on the same connection. Two panes, local and remote, servers in groups, several connections per server.
The parts I actually care about:
The session log shows everything.* Every line of every session, exactly as it goes over the wire — 220, USER, 331, PASV, the lot. No black box, and when something breaks you can see where.
Transfers are verified, not assumed.* After an upload the file size on the server is compared with the local one. A server answering "226 Transfer complete" is its opinion, not proof.
Failures are not just an error dialog.* Each file is retried three times. Whatever still doesn't get through goes on a list that survives quitting the app, so after the line drops mid-way through 500 files you don't have to work out where it stopped. You decide whether to retry or discard — nothing on the server is ever deleted for you.
Strict about who answers.* Host key and certificate fingerprints are confirmed once, then checked on every session. If one changes, the connection is refused. There is no "connect anyway" button, on purpose.
Nothing phones home.* No account, no registration, no analytics, no crash reports to me. Sandboxed. It talks to your servers, not to mine.
What I would like from you:
Break it against a server I have never touched. Odd LIST formats, a NAS with a self-signed certificate, an FTPS server that insists on TLS session reuse, an SMB share with unusual permissions — those are the reports worth having. Feedback goes straight to me from inside TestFlight.
Free during the beta, macOS 14.6 or later. Screenshots, what it does and the TestFlight link:
English: https://klausmack-software.com/FileFerry/index\_en.html
German: https://klausmack-software.com/FileFerry/index.html
Privacy: https://klausmack-software.com/FileFerry/privacy\_en.html
A note about me and this post, as the rules require:
I am the developer of FileFerry — this is my own app, and I have no other relationship to it than that. I write Mac apps on my own, and this is the fifth Beta.
FileFerry is in an open TestFlight beta right now and free while it lasts.
It will be a paid app on the Mac App Store later; there is no subscription planned, and there never will be advertising or analytics of any kind in it.
Nothing about how you use it is sent anywhere. The privacy statement spells that out in plain language.
Two testers have already found bugs that way that I could never have hit on my own equipment, and both are fixed. Awkward servers are exactly what I am looking for.
Happy to answer anything in the comments, including the awkward questions.
© Klaus Mack Software
https://redd.it/1vr7pdn
@macappsbackup
I'm the developer, working alone on this, so treat the below as what it is — someone showing you his own app.
What it is:
A native macOS file transfer client — no Electron — that speaks FTP, FTPS (explicit AUTH TLS), SFTP, WebDAV and SMB, and opens a full SSH terminal on the same connection. Two panes, local and remote, servers in groups, several connections per server.
The parts I actually care about:
The session log shows everything.* Every line of every session, exactly as it goes over the wire — 220, USER, 331, PASV, the lot. No black box, and when something breaks you can see where.
Transfers are verified, not assumed.* After an upload the file size on the server is compared with the local one. A server answering "226 Transfer complete" is its opinion, not proof.
Failures are not just an error dialog.* Each file is retried three times. Whatever still doesn't get through goes on a list that survives quitting the app, so after the line drops mid-way through 500 files you don't have to work out where it stopped. You decide whether to retry or discard — nothing on the server is ever deleted for you.
Strict about who answers.* Host key and certificate fingerprints are confirmed once, then checked on every session. If one changes, the connection is refused. There is no "connect anyway" button, on purpose.
Nothing phones home.* No account, no registration, no analytics, no crash reports to me. Sandboxed. It talks to your servers, not to mine.
What I would like from you:
Break it against a server I have never touched. Odd LIST formats, a NAS with a self-signed certificate, an FTPS server that insists on TLS session reuse, an SMB share with unusual permissions — those are the reports worth having. Feedback goes straight to me from inside TestFlight.
Free during the beta, macOS 14.6 or later. Screenshots, what it does and the TestFlight link:
English: https://klausmack-software.com/FileFerry/index\_en.html
German: https://klausmack-software.com/FileFerry/index.html
Privacy: https://klausmack-software.com/FileFerry/privacy\_en.html
A note about me and this post, as the rules require:
I am the developer of FileFerry — this is my own app, and I have no other relationship to it than that. I write Mac apps on my own, and this is the fifth Beta.
FileFerry is in an open TestFlight beta right now and free while it lasts.
It will be a paid app on the Mac App Store later; there is no subscription planned, and there never will be advertising or analytics of any kind in it.
Nothing about how you use it is sent anywhere. The privacy statement spells that out in plain language.
Two testers have already found bugs that way that I could never have hit on my own equipment, and both are fixed. Awkward servers are exactly what I am looking for.
Happy to answer anything in the comments, including the awkward questions.
© Klaus Mack Software
https://redd.it/1vr7pdn
@macappsbackup
Klausmack-Software
FileFerry — file transfer and SSH for macOS
Seven protocols and a real SSH terminal in one native window. Public beta on TestFlight.
Do you still remember the exact feeling when your app got its very first users? 🚀
https://redd.it/1vrdw1u
@macappsbackup
https://redd.it/1vrdw1u
@macappsbackup
My Mac Apps Story, Part 5 - Making the Touch Bar and macOS Work My Way
https://redd.it/1vrgniw
@macappsbackup
https://redd.it/1vrgniw
@macappsbackup
A month later: Aye now adds a save button to Telegram Web on Mac
I’m one of the developers of Aye. I posted the first Mac version here a little over 30 days ago. Rather than repeat the launch post, I wanted to come back with the update people actually kept asking for.
PROBLEM
A video can be playing in Telegram Web while saving that exact item is still awkward. Copying the page URL does not identify the video, and moving to another app breaks the flow if the rest of the work is already in the browser.
Aye now adds a Save Current Media control to the video that is open in Telegram Web. After clicking it, the file appears in Aye’s Downloads panel. I wait for the status to change from Downloading to Completed, then use Show in folder to verify the file.
This works one visible item at a time. It is not a channel archiver or bulk scraper.
COMPARISON
Safari and Chrome are better-known general browsers, but they do not add this Aye-specific media control or its completion check to the Telegram page. Telegram Desktop should still be the first option when its own save action already does what you need.
Compared with installing a generic media-downloader extension such as Video DownloadHelper, Aye’s control is built into the browser and is designed around the media currently open in the Telegram tab. There is no separate extension to install. The trade-off is that Aye does not claim to detect every media type or every future Telegram Web layout.
PRICING
Aye is currently free on the Mac App Store:
https://apps.apple.com/app/aye-browser/id6760281977
The boundary matters: Aye only handles media the signed-in account can already view and that the user has the right to save. It does not bypass login, invitations, DRM, paywalls, Telegram permissions, or other access controls. Saving a local copy also does not grant redistribution rights.
For people who use Telegram Web on a Mac: is the more annoying part finding the right file, tracking a large download, or verifying where it was saved?
https://preview.redd.it/2s5rgvpqb3kh1.png?width=1672&format=png&auto=webp&s=e2088bb89db2c1c12f612b3b0f535115512a3774
https://redd.it/1vriyuo
@macappsbackup
I’m one of the developers of Aye. I posted the first Mac version here a little over 30 days ago. Rather than repeat the launch post, I wanted to come back with the update people actually kept asking for.
PROBLEM
A video can be playing in Telegram Web while saving that exact item is still awkward. Copying the page URL does not identify the video, and moving to another app breaks the flow if the rest of the work is already in the browser.
Aye now adds a Save Current Media control to the video that is open in Telegram Web. After clicking it, the file appears in Aye’s Downloads panel. I wait for the status to change from Downloading to Completed, then use Show in folder to verify the file.
This works one visible item at a time. It is not a channel archiver or bulk scraper.
COMPARISON
Safari and Chrome are better-known general browsers, but they do not add this Aye-specific media control or its completion check to the Telegram page. Telegram Desktop should still be the first option when its own save action already does what you need.
Compared with installing a generic media-downloader extension such as Video DownloadHelper, Aye’s control is built into the browser and is designed around the media currently open in the Telegram tab. There is no separate extension to install. The trade-off is that Aye does not claim to detect every media type or every future Telegram Web layout.
PRICING
Aye is currently free on the Mac App Store:
https://apps.apple.com/app/aye-browser/id6760281977
The boundary matters: Aye only handles media the signed-in account can already view and that the user has the right to save. It does not bypass login, invitations, DRM, paywalls, Telegram permissions, or other access controls. Saving a local copy also does not grant redistribution rights.
For people who use Telegram Web on a Mac: is the more annoying part finding the right file, tracking a large download, or verifying where it was saved?
https://preview.redd.it/2s5rgvpqb3kh1.png?width=1672&format=png&auto=webp&s=e2088bb89db2c1c12f612b3b0f535115512a3774
https://redd.it/1vriyuo
@macappsbackup