You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Idea would be to write in the web client a small progressive web app (PWA) that implements the Share Web API client. This would mean users could install fro the web browser a small share application essentially what Party-Up does with significantly less code. Potentially also allows multiple share to apps to be installed (one per server, i.e. no need to edit config when switching between servers).
I believe this would be Android ONLY. I'm not sure what (if any plans) there are for Apple iOS implementations (I don;t have a device to test with).
This has the potential to replace Party-Up for some uses cases (unclear if this is a pro or a con, Party-Up works great so far with my experiments I'm not suggesting is needs to be replaced), specifically https.
Disadvantage of Web Share API is that it (understandably) requires https, Party-Up can work with plain http as well as https, so I don't think this idea would ever remove the need for Party-Up.
I'm definitely not an android dev so this will be way comfier / more motivating to work on, and would be great to get rid of the pain points you already mentioned (inflexibility with multiple servers and so).
I haven't looked into any of the details yet, but the first version could be dead simple (much like the android app), just allow for a plain PUT/POST upload... but would be real awesome if it was possible to do chunked/resumable uploads over up2k eventually!
And the best part is, it looks like this might actually be supported by apple devices as well -- MDN mentions that support was added into iOS 15, which just so happens to be the final version that my iPod Touch will get, so I can actually give this a try :> (in particular, should check whether the gallery app transforms/shrinks images before they get uploaded)
Mainly I'm really curious how this will be performance-wise, whether Party-Up will launch faster, or process files faster -- since I've noticed the android web-browsers have really poor performance when reading files from the filesystem during uploads, and I suspect Party-Up's performance in that sense is better, but I don't think I ever checked.
I'll take a better look at this over the weekend :>
Idea would be to write in the web client a small progressive web app (PWA) that implements the Share Web API client. This would mean users could install fro the web browser a small share application essentially what Party-Up does with significantly less code. Potentially also allows multiple share to apps to be installed (one per server, i.e. no need to edit config when switching between servers).
I believe this would be Android ONLY. I'm not sure what (if any plans) there are for Apple iOS implementations (I don;t have a device to test with).
This has the potential to replace Party-Up for some uses cases (unclear if this is a pro or a con, Party-Up works great so far with my experiments I'm not suggesting is needs to be replaced), specifically https.
Disadvantage of Web Share API is that it (understandably) requires https, Party-Up can work with plain http as well as https, so I don't think this idea would ever remove the need for Party-Up.
Unclear about basic-auth implications.
Resources
The text was updated successfully, but these errors were encountered: