mirror of
https://github.com/dutchcoders/transfer.sh.git
synced 2026-02-03 14:13:26 +00:00
Accounts #293
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @notramo on GitHub.
I have read #22.
What about allowing creating accounts, and if a file is uploaded in an account, then permit raw access?
If GitHub account should be used for transfer.sh account creation, unethical use of the service could be lowered.
@mckaygerhard commented on GitHub:
umm i understand what do you want! like we-transfer does! but that will complicated the things in any case.. i means will be not ease!
@mckaygerhard commented on GitHub:
@notramo you can review the pull https://github.com/dutchcoders/transfer.sh/pull/105/files and see or adapt for your needs! personally this will convert into a nextcloud/owncloud system but i also understand your point of view!
also that was limited implemented into https://github.com/dutchcoders/transfer.sh/pull/127
@notramo commented on GitHub:
It would only attach an username to transfers for tracking.
@notramo commented on GitHub:
Yes, it would be similar to We-Transfer, but it would use a permanent account.
@mckaygerhard commented on GitHub:
well i think account will complicated more that simple ways of the thinks!
also account will convert this into a kind of owncloud/netxcloud!
@notramo commented on GitHub:
Authenticated uploads should have a raw content URI, which don't use the web wrapper.
@paolafrancesca commented on GitHub:
@notramo what issue are you facing? what are you trying to do that you cannot?
@paolafrancesca commented on GitHub:
@notramo what's the problem you have exactly?
@mckaygerhard #105 was closed by the author and implemented properly in #127
@mckaygerhard commented on GitHub:
yeah @aspacca that's what i wrote, .. as a extra note that only added http authenticacion from uloader, not for download of files @notramo so you must adapt to your needs and also send in clear the password! as i said, its very basic and enought to keep in simple!
@notramo commented on GitHub:
#22
@mckaygerhard commented on GitHub:
yeah, it's a great idea that solved the raw links problem, as i said in previous comment!
@paolafrancesca commented on GitHub:
@notramo , I repeat the question for the last time: what issue are you facing? what are you trying to do that doesn't work?
#22 is not an issue on itself
@notramo commented on GitHub:
I want to have raw links. Authentication can be a solution against abuse.
@notramo commented on GitHub:
@mckaygerhard Yes. Authenticated uploads should have raw links.
@mckaygerhard commented on GitHub:
swo i understand, raw links can be offered but with authentication, so abused could be avoid! right?
@paolafrancesca commented on GitHub:
@notramo you have "raw link" available with curl
@notramo commented on GitHub:
How can phone users use curl?
@mckaygerhard commented on GitHub:
@notramo have now a good point.. so then phone users wil always be authenticated and so can access directly to the files and those files can be serverd directly to that users ummm.....
@mckaygerhard commented on GitHub:
umm so the software detect the agent and property offerts the raw link?
and i think you dont understand that @notramo said! @aspacca : i think its that raw links can also be available for browsers agents too! but autenticated to avoir abuse
well i guess!