• idrk anything about ldap
• Multi-domain can be done but it's weird I can elaborate on this if you'd like
• 👍
• I think this would be better of as a folder but maybe

idrk anything about ldap

Instead of LDAP, try implementing support for authelia or authentik. Both of those have support for it and they allow you to use the OAUTH specification.

Authentik is supported in v4, but it was also brought into light that authentik is just a OIDC implementation, you can see in the PR #372.

I really like the idea for the report abuse text, perhaps expand upon that with a fill-able form vs. email since some people prefer not to send emails.

no need for a /u/ (or whatever) in upload links but make sure there's backwards compatibility :)

So you don't know? you can just use / without /u/ for upload links. So it would be DOMAIN.com/NameofImages.jpg instead of DOMAIN.com/u/NameofImages.jpg. Just edit the UPLOADER_ROUTE=/ in your configuration or docker yaml if you are using Docker.

huh.. i wish i knew this before uploading 30,000 files. cause you cant change it after the fact without getting dead links

huh.. i wish i knew this before uploading 30,000 files. cause you cant change it after the fact without getting dead links

Yeah, maybe because of the database thing.

• this exists already, I think I might add some sort of extension/(white/black)list setting instead of it just being a blacklist
• meh idk
• this is planned, so yeah hopefully
• idk what this is supposed to mean but I did revamp it a bit in the current v4
• planned
• is this referring to the 50mb limit bypass? If so then, yes it is planned
• you can already do this
• like youtube I guess, I don't really know if it's a good idea though
• unfortunately I can't do anything about this - maybe some redirect for those who have already posted links that go to one route

• good idea
• not sure what this means? I won't be adding a custom video player since there isn't really anything like different qualities and such that you can do on Zipline's videos
• not sure what this means
• maybe
• this can be done through the table view

This is something I've wanted to do in v4, though I'm not sure it will be possible to support multiple types of serverless platforms (which would be the goal). The way Zipline v3 works, as a lot of functionality within the custom server, and I'm not sure how else it would be done.

you can probably still use a custom server with serverless if you use something like hono instead of fastify, not sure though.

I forgot that zipline has a lot of stuff with worker_threads 😔, so I don't think it will be possible to support serverless platforms

I was thinking about this earlier, and was thinking about some sort of proxy that would serve images from Zipline, but I'm not sure. It would be a pretty limited Zipline if serverless.

I was thinking about this earlier, and was thinking about some sort of proxy that would serve images from Zipline, but I'm not sure. It would be a pretty limited Zipline if serverless.

what I was thinking is maybe handle just the image serving using serverless. maybe like with cf workers that only respond to the /u/ path or whatever it's set to and everything else just goes to the main Zipline instance.

idrk, it sounds complex but this is definitely something I'd like to see implemented in some form. maybe this could be an extension that advanced users could setup, but Zipline can still run standalone.

Are there any docs for this?

Matrix is a decentralized chat network, and relies on matrix clients. These clients must parse meta tags and opengraph data for link previews.

It has URL Shortener built-in

Yes I know. But imo Shlink is better for this because it is just built for shorten and has way more options. That's why I wrote in the last line that this integration could be also implemented in creating short URLs in Zipline, so everything is in one place.
Also, I want to use my short URL domain for Shlink because, as already mentioned, it has more options to customize the short link. So I don't want to redirect the Domain to Zipline.

Adding integration for another url shortening service when Zipline has it's own seems counter-productive. If you would like more options consider suggesting them?

not sure what a content warning means? is it like a spoiler and u have to click on it to see the image?

Either a clickthrough or a CSS blur that unblurs on hover, yeah; a content warning could function as a spoiler warning, nsfw content warning, or somesuch.

What are you doing to do that for every image or do you want some sort of ai to try to identify it

Let the user specify it for image uploads themselves. Trying to involve AI for that is overcomplicating things.

Sounds a bit vague... What sort of meta tags? What sort of functionality would be gained from adding it?

Not sure what this is supposed to mean, but I don't think they have any custom stuff and usually opengraph is the standard for link previews as well as other meta tags, so this won't be added(?)

This seems out of the scope of Zipline and imo, unnecessary for zipline.

Maybe, I think this is a bunch of stuff that could be added later but not really that important for the major release.

I don't know exactly how it was developed, I guessed before that it involved the underlying design, so I made this suggestion.
If it's not something that needs to be considered at the outset subsequently it can always be attached and I'll wait patiently.

Should actually be /metrics, and if possible add support for it to be pulled only by an Authorization header.

maybe

• I think all of this except tags is introduced in v4 as of now (i will work on tags later)
• good to hear! what are you using currently?
• Kind of(?), viewing exif required a library that called a executable and was pretty clunky and I didn't like how it worked. The new way just reads the files bytes and removes GPS metadata. So now we can't view exif metadata - and I thought it was a fair tradeoff since the amount of people wanting to view exif metadata would be pretty small. Unfortunately you are one of the people in that small group, I would like to hear what metadata you would even look at (imo I think its just useless unless you upload pictures from your phone, digital cameras, etc)

• That's great to hear, thanks!
• I currently use XBackBone, it's nice but it's beginning to feel a little clunky compared to the more recent solutions such as Zipline, and overall has fewer features.
• That makes sense, now I understand why you felt that way about EXIF support! I will fairly often be uploading images from various cameras so yes, I fall into the subset of users who would still find that useful, but it is something I can live without. The ability to strip GPS coordinates is great; I would appreciate the option to strip all EXIF data from images, but I'm guessing if you were to implement this then you'd essentially be back where you were before in terms of calling binaries and so on.

Yeah, I think the different types of limits are outlined in the Prisma schema if you want to take a look at that

Where can I find this? I found line 51 as the only line potentially relating to file size upload limits.

I think I may have removed it, sorry - but #433 (comment) offers a good explanation on how it will work.

at that point you might as well use something more streamlined for video uploading, zipline doesn't really need this

Gotcha! It would have been neat though, and it would have made it our go for sharing the videos we produce with our clients.

Like what? Currently you can set the title, description, site name and color, and afaik you cant really add any more since discord doesn't support them (I'm guessing in the way you're thinking)

the provider?

Well the two that are "missing" and discord still supports are the author and timestamp

I'm pretty sure you can't set those fields through metadata tags, but feel free to correct me (and if you want show what properties it reads).

(this was discussed more in discord) thank you for providing more info about how user limits should be implemented, I'll just have to see what works and what would be the best way to implement. I think I'll be doing some polls in discord so those who are interested in this should look out

cool idea i think

What would an example usage of this? i can't really think of anything useful out of this..

No. Zipline stays in Zipline. Having multiple datasources would make it too complicated. This is just a simple image/file host.

If you're at this point, you may as well use Nextcloud.

1. sure
2. already exists in v4

It is expected that you figure out how to install nginx, if i were to add instructions on how to install something required/recommended for zipline, I'd have to walkthrough docker, nginx, etc. plus there are countless guides online that you can reference, i don't really get why it should be included in the docs.

I've tried, yeah. Unfortunately it's not feasible with super large files and can sometimes be completely unnecessary especially with single file uploads like zip files. But something super simple like uploading over an existing file and appending the file name and modified date would all it need to be.

So let me iterate on this a bit more too. I have a case scenario where I am going to be uploading new versions of a file all the time, where I need to share that file for download. I would like the download to update automatically with that updated version of the file, so I do not have to manually update the link.

However, the only solution I see to this right now is a folder system which works fine, but I cannot customize it and I would also just prefer to have a single download button that has the latest version of the file.

Just throwing in my two cents - seems like a bit of a far-fetched feature for something like Zipline. At that point I'd say spin up a Git server.

The other point I see being an issue on this is file integrity, brewing itself to be a recipe for disaster.

That's fair, personally think it would fit great in zipline. But also then again zipline is great for simplicity. I will see what I can do in my case scenario with Gitea and try to get it working again.

I think what @Permanently said sums it up pretty well, and also what you say, Zipline is "supposed" to be simple though at this point idek lmfao but i'd like to keep it within some sort of area where it is simple enough to the end user (and me). hope you get gitea working to your needs!

RE: #443 (comment) Can there be an external endpoint or similar addec that allows the deletion of expired files in the system. This would be in addition to just expiring the link so the user cannot see it anymore, as is currently the case?

I can just make the files endpoint have finer control over filters, so you can append a query string like &filter=expired or something, then send a separate request to delete these files. And I think it already runs on a interval right now, but this will allow more functionality outside of zipline ig.

Hoping this might be up-voted by some other users or perhaps even included without...here's hoping 🤞 ;)

😂 no one really upvotes here, but I or a poll in discord usually have the final say (I'll prolly add what you're talking about anyway lol)

good idea

not possible since the embed is controlled by the destination URL. you can have custom url shortener embeds if zipline waited 1 second before redirecting (using javascript) but I don't really know why you would want this...

isn't that already in zipline? file expiration

isn't that already in zipline? file expiration

That's a valid question, I thought not but I may have overlooked it..

is this the thing that u meant?
https://stef.likes-ur.mom/u/hnJ3uDiJ2oBg.png