read-only view for pads #1

New issue

Open

opened 2025-09-28 18:40:42 +00:00 by cf7 · 0 comments

cf7 commented

2025-09-28 18:40:42 +00:00

Owner

The idea

having a link that can be shared for read-only access to the pad without disclosing the original URL.

Current status

Some ideas:

[1] having a UUID for a read-only view, pad_id and UUID are independent, must be saved somehwere
[2] hashing the pad_id to generate a readonly_pad_id, makes it easier to work with, but must be saved somewhere again or hashed again (time intensive)
[3] having an encryption methods for the pad_id with salt to allow a 1-to-1 matching, does not have to be saved anywhere

All the above have different advantages or disadvantages. I've looked into [3] and even tho it worked, it made things way more complicated and the performance was bad (couldnt figure out why, but might be some problem with the websockets and the sync).

Been a while but just for later.

Might be enough to have the /raw/ endpoint readonly which would make things way easier.

### The idea having a link that can be shared for read-only access to the pad without disclosing the original URL. ### Current status Some ideas: - [1] having a UUID for a read-only view, pad_id and UUID are independent, must be saved somehwere - [2] hashing the pad_id to generate a readonly_pad_id, makes it easier to work with, but must be saved somewhere again or hashed again (time intensive) - [3] having an encryption methods for the pad_id with salt to allow a 1-to-1 matching, does not have to be saved anywhere All the above have different advantages or disadvantages. I've looked into [3] and even tho it worked, it made things way more complicated and the performance was bad (couldnt figure out why, but might be some problem with the websockets and the sync). Been a while but just for later. Might be enough to have the /raw/ endpoint readonly which would make things way easier.