pixelfed / ideas Goto Github PK

As a user (and possibly admin), I would like the ability to keep the original copy of the upload as well with no compression/optimization/stripping. This comes in handy as an archival mechanism as well as a migration tool. How that's further implemented is up to suggestion -- per instance by admin, per post, per account. The ability to download the original as the owner or third-party?

This is feature of keeping an original copy is a feature I appreciate from Flickr -- knowing I can migrate easily and know I can at least get the original JPEG in case of a disaster.

Please add a global filter in the settings to filter out all pictures with 'cat' in the caption or description!

"Locked":

• manually approves followers
• profile visible to public (with only public posts)

"Private":

• requires authentication to load
• profile not visible to public (403/404 error)

Currently the language we use is "private mode - when your account is private, only people you approve can see your photos and videos on pixelfed. Your existing followers won't be affected." This isn't strictly true. Therefore I propose more clearly separating / making a distinction between "locked" and "private".

Hello, in my opinion it would be great for new users if they see a preview of what they could expect at this instance. At the moment every image is blocked if I have no account.

When applying filters, one may want to compare filtered image with the original one.
Currently Pixelfed UI forces you to scroll back and forth between {filter} and "No filter" options.

To solve this issue, I suggest applying filter when you click on it and disabling it (reverting to "No filter") if the same filter is clicked for the second time.

For larger instances and for division of work, it would be good to further refine the rights management. Then it would be possible to make someone e.g. a moderator without giving this person access to the whole instance.
Possible levels could be: User, Moderator, Admin, Root

Not everyone likes this kind of feature — mainly photographers who still work in all rights reserved licensing and don't like media/press share pictures without contract.

It will be great if we can choose to authorize embedding posts, publication by publication and maybe with default settings in preferences.

Also, embed profiles must show only images with embed options turned on.

Is your feature request related to a problem? Please describe.
I use Pixelfed as an iOS Add to Home Screen app and I never know when there are new notifications at a glance when I open it.

Describe the solution you'd like
Highlight the notification icon when there are unread notifications. Notifications are created unread. Tapping on a notification marks it as read. Visiting a post marks all notifications related to this post as read.

I'll love to have exif details about my picture each time I upload a new one one pixelfed. Details about used camera, aperture, speed etc.
Of course, picture needs exif on it, and this functionality must be enabled on account option for work (privacy reason).

How can I make my instance really public?

To access the public timeline or public profiles you still need an account. I want my instance to be browsed without an account.

I'd love to see Pixelfeld support WebAuthn (by now supported by all major browser vendors) for multi-factor-authentication. It would introduce Pixelfed to other, more security-conscious communities as well as possibly entice others to use their own security keys or hardware second-factor devices (macOS fingerprint scanner et al). There's a library already available for integration.

Peertube allows for following of whole remote instances (I believe it is all public videos), this ticket is requesting that for PF. Similar to "tag" follows where you don't need to follow specific users, this would just be for whole instances instead.

An example: perhaps pixelfed.art is a real instance where many different artists posts to, this ticket would allow users to follow all the public posts from that instance.

Env file while great, isn't particularly accessible. With some packages on some distros, some services are as easy to set up as installing and then opening a web browser with a certain url. Take for example nextcloud:

It would be cool to approach Pixelfed setup the same way, with a short setup wizard, without going into a text file and changing strings.

Consider adding a file for vendor preset, so we can have defaults in the wizard set according to the way the vendor shipping a package intended it to be used.

Given that in many places in the UI for some aesthetic choice, images are fit to a square. Obviously not all images are square and many images aren't center-weighted for composition and as a result, many images get cropped in an unpleasant manner.

I would propose that there be a UI element for choosing the object-position--or background-postition where CSS backgrounds are used as a hack.

The on option could be a 9-point element denoting the possibilities for the keywords that happens after the filter selection phase. The 9 points would correspond to the x and y values top / center / bottom and left / center / right. This would update the thumbnail in that UI as well. This could be modeled as the product of two sum types for x and y.

Another option, would be the ability to drag that thumbnail around and get a relative percentage. It could correspond to 2 <input type=number> or <input type=range>s that could be used to dial in an exact amount and make it more discoverable. This could be modeled as the product of two floats for the percentages.

Another option (not recommended), could be a straight-up text input under advanced settings so a user could use calc() or whatever. This would need sensitization and could be modeled as a string.

What

In light of tumblr cracking down on nsfw art as well as greatly reducing their artists ability to monetize and thrive by removing any posts from searches and tags that have a link on or off site I think we should integrate deviantart-like gallery filter using tags (like tumblr), reasoning explained below.

For reference here is the deviant art 'gallery' view.

if you click on a 'folder' to the left, it filters the overall view to just things put into that folder.

I propose we add a panel to the left that would display tags that the user has used, and clicking on it would only display pictures that contain that tag.

#ProgrammerArt

if you click on a tag, you are only displayed content related to that tag. one could possibly click multiple tags to display only posts that contain all tags selected. Tags should be organized by frequency but users should be allowed to pin certain tags to the top (I don't really have a UI idea for this, possibly something in settings or a little pin emoji on tags when users view their own gallery).

Here is how I imagine it interacts with Post visibility in this way:

1. Public is public, it's both displayed on the timeline as well as galleries and tags.
2. Unlisted would have art only appear when you click on a tag that it contains.
3. Locked would not display the art in the gallery, regardless of tagged status.

Why

1. Granular searching promotes exploring user content, which is great for creatives because it helps expose their work which can be hard on a network of communities that by design create content that is fleeting and in-the-moment.
2. The Fediverse is composed of multiple communities running multiple backends like Mastodon and Pleroma, which means that a larger assortment of people will be could be browsing this work than simply sharing it on a site like DeviantArt, which only has users who explicitly set out to look at the creators deviantart page. Artists would often use sites like tumblr and twitter not because they're great platforms for displaying art (they're actually really bad at that), but because they have the most discoverability which allows them to potentially sustain their livelihood or just find an audience in their craft.
3. Tags not only allow easier discovery of desired content, but allow a greater ability to filter content one does not want to see through filtering, promoting the usage of tagging in the Fediverse to enhance individual user experiences.
4. This helps differentiate Pixelfed from Instagram, why should we simply be content to provide the exact same service but federated, we should be imagining new ways of communicating that value the users over corporations.
5. This provides functionality similar to what artists expect when they come in from other social networks. Sudden loss of functionality because you don't enjoy corporate control of your social media experience can reduce uptake and continued use.

tl;dr: this is a great way to allow gallery views while promoting a form of non-fleeting content in the Fediverse. It also helps differentiate Pixelfed from Instagram.

I've forked pixelfed, and dependabot notified me of about 17ish packages it can upgrade for us automatically.

Something that would be expected by transitioning Instagram users, and has been done in diaspora* and Friendica, is to give joint ownership of comments on posts to both the comment author and the post author. In ActivityPub terms, the comment is owned only by the comment author, but there should be a way to delist certain offensive or unwanted comments on a specific photo of yours, and this should be signaled to the comment author's instance so that it can handle the situation, either by removing the comment from the remote instance, or at least removing the inReplyTo link. This can probably be done by Reject Create Note.inReplyTo, which might not be supported at first in other softwares, but is something that should at least be supported between Pixelfed instances.

Is your feature request related to a problem? Please describe.
I'm writing my community guidelines and they are pretty long.

Describe the solution you'd like
Internal links to go to others sections of the text would be more ergonomic.

Describe alternatives you've considered
A system to create links and anchors.

Pitch

It could be great to have a 1 click installation plugin for freenas.

Motivation

I have a freenas server and they have a plugin system where you can install some popular app like nextcloud (https://www.ixsystems.com/documentation/freenas/11.2-U5/plugins.html?highlight=plugins#official-plugins). It will help to get more adoption if it that easy.
They have a documentation here : https://www.ixsystems.com/documentation/freenas/11.2-U5/plugins.html?highlight=plugins#creating-plugins

I'm sure that not easy to develop but begin to think about it it's a good beginning.

If someone hosts a personal instance of Pixelfed for a single user, the default splash page should be the gallery view of their profile.

Some location names have a lot of ambiguity and it would be nice to show the name of the state or territory that they belong to. This could be enabled on a per-country basis.

Is it possible to embed collections? I think that would be great
Thanks!

As it stands the content warning system is not particularly effective; there's no field for entering in what the sensitive content is. You just get a generic message.

Being able to change the message from "Content Warning: This may contain potentially sensitive content" to something more descriptive for each individual post would be a huge benefit for usablitiy.

Additionally, displaying the custom content warning text on the greyed-out thumbnail in the profile view too would help people find a content-warned image in a profile that has had heavy use better (though maybe that would be best put into a separate issue)

• Instagram lets you hide / archive certain posts without deleting.
• Pixelfed currently has an "unlisted" scope modeled after Mastodon.

I propose using a separate property for the latter, so that we can clearly signal whether a post is discoverable and should be shown in Discover, or in public timelines, or in other discovery features. Maybe we can reuse toot:discoverable from Mastodon, but apply it to objects and not just actors.

Then, I propose reworking "unlisted" posts to only be accessible via direct URL, like YouTube.

Hello,

Pixelfed instances would be way better if the landing page was also an "about" page, with a description of the instance's goals, the instance's owner, the moderation method, etc...just as peertube does in the pages "domain.tld/about/instance", it would be more readable than a specific page for community guidelines.

Hello,
Just a suggestion after using Pixelfed.

When you are on the timeline of someone, you see all the pictures of that person.
If you want to see one picture in big / all the post details / or comments it, you have to click on it.
But you have to back one page to see every pictures of that person again.

So maybe when you are on the picture (that you selected), we could put two arrow (right and left) to go on the next picture and previous picture without back one page ?

I hope I am clear? Have a good day

This is a low priority feature request but thought I put it out there just in case. And somethings are best mentioned earlier than later. The Tumblr exodus has brought to light one concern: avatars are federated as-is (as are header but that's n/a).

Here are some possible solutions that come to mind:

The following assumes servers can distinguish a local request from a remote one and can react accordingly.

1. give admins the ability to default all avatars to a default one when fetched remotely.
2. have an option akin to "nsfw avatar" (checkbox) or perhaps a more generic "nsfw account" that could be leveraged for this and other features. When toggled, an alternate version, perhaps a blurred version, is sent to the remote server.
3. let users set at most two avatars: a global and local one. Your Clark Kent / Superman option. As to which one is set when only one avatar is provided: it depends on the ui and what you guys prefer. One possibility would be a user specified avatar clobbers all neighboring default avatars but never a neighboring user specified one.
4. Other
5. None of the above

for me option 2 might be best, if any.

Suggestion to add basic edit before submitting

Maybe crop, auto crop to box, flip, rotate?

Hello,

On the instance picker, we have no information about the purpose of every instance. So you could advise submitters to add a description to the instance they submitted, it would be easier to choose the instance with a such information.

So far, I see pixelfed finally has support for explicitely adding a license to pictures posted there, which is great. Compared to especially Flickr, it would be great, too, to have more support for such licenses in navigation and exploration to (a) make it easier for people to discover such pictures and subsequently (b) make it more interesting for creators to use such licenses for pictures. Ideas could include:

• add or support something like a "find by license" feature
• have an "explore" view dedicated to Creative Commons licenses
• ...?

Just a thought / enhancement request; not sure whether possible or relevant for anyone but me. ;)

I want to store all media on a CDN (S3 compatible). this allow Pixelfed admins to destory/rebuild the pixelfed server (docker container or standard install) and leave the media in a safe dedicated location.

I don't need to worry about disk space on the server ETC ETC

I noticed it's a little hard to find the address to follow a Pixelfed user from another part of the Fediverse. Currently if you want to follow a Pixelfed account from Mastodon, you have to explicitly know that you need to format the address: @[email protected]

Maybe we should add the full address below the username on profiles and make sure it's easy to copy and paste.

Is your feature request related to a problem? Please describe.
After installation an instance of @pixelfed, people would like to upload their own logo instead of original.

Describe the solution you'd like
Pixelfed is protected under GNU Affero General Public License v3.0, that allows private and commercial use. So having an option in admin panel for changing website logo, will have no conflict with the project.

Additional context
Maybe adding a .gitignore file to img directory for logos after change would be a nice trick to prevent invalid commits on original logo files in branches merge.

Since Mozilla and Microsoft announced they'll support WebP format in their browser soon, I think this would be a good thing PixelFed allows users to upload WebP files.

edit by trwnh:

• Upload WebP
• Convert to WebP?

Hello,

Every time i upload a pic with transparent background, it is replaced by a black color. It can be a problem if the pics has some black elements in the said background because they become invisible. It would be more practical if we could use a custom color, like white or checkerboard.

I remember that I saw @dansup brainstorm about a non-compression mode that instances could turn on. Probably about a year ago. I really liked the idea, but I couldn't find anything about it here, so I open this issue.

Alternatively, I would suggest such an option for either accounts or posts. So you could turn in on in your account settings or for specific posts. Which might make sense, as some images suffer more from compression than others. :)

Here is the request json:

{
  "@context":[
    "https://www.w3.org/ns/activitystreams",
    "https://w3id.org/security/v1",
    "https://hub.somaton.com/apschema/v1.2"
  ],
  "id":"https://hub.somaton.com/follow/1335",
  "type":"Follow",
  "actor":{
    "type":"Person",
    "id":"https://hub.somaton.com/channel/testc1",
    "preferredUsername":"testc1",
    "name":"testc1",
    "icon":{
      "type":"Image",
      "mediaType":"image/png",
      "url":"https://hub.somaton.com/photo/profile/l/28",
      "height":300,
      "width":300
    },
    "url":{
      "type":"Link",
      "mediaType":"text/html",
      "href":"https://hub.somaton.com/channel/testc1"
    },
    "inbox":"https://hub.somaton.com/inbox/testc1",
    "outbox":"https://hub.somaton.com/outbox/testc1",
    "followers":"https://hub.somaton.com/followers/testc1",
    "following":"https://hub.somaton.com/following/testc1",
    "endpoints":{
      "sharedInbox":"https://hub.somaton.com/inbox"
    },
    "publicKey":{
      "id":"https://hub.somaton.com/channel/testc1/public_key_pem",
      "owner":"https://hub.somaton.com/channel/testc1",
      "publicKeyPem":"-----BEGIN PUBLIC KEY-----\nMIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAu2rdf4ZVT5ScPr2epmBw\nKodj+PFwwlFmlK7bgovKVlTkyUoM8Uv4nGnzmtt3ew8J2DAXicqISjiRBI/0pNCq\nPMJqTtN8+aELtnUnWivSCOar5GuGeZRHoLtJp9nI3T7iG07NrMnAXjwVaRNm0+Wk\nOv7ht6645EeksGRIbRgbKZnx5liL/Shd9Dxx5sqZy4GM0dUcibxO0SDnauhM7JJR\nn43QBgK/8T3g6ZiO4jYiztCQRzrdLgWhAPvX290AMtO8UBhwBm5a2vIsMAZvdVLs\nvbTReJj8X2N+GArAcFdCSaARWN9mlpKyN5PJn2ItMWmcbCchwDcEI45edgDSWSNx\nALKyqqboCgI71nFHGD8Ws+LE77a4wJGGRYX8mb7J3xUCd4lHSqsp1z9wQ88Jvfwk\nDAmVX6buyiBR0gTlmBzIEwHjUUFrqKOnK2xQj0kD6Mi6TrSNlil6R6YzVGr06gYL\nL5fWvonMk836/FOTB4QDfacDnBmyKezSivLUPyN5+fUt9fuDW0BX8dEVCvow/dIc\nKWWem+1OzqoetT5p02QLsE8JS/ZEI5uQ6uFy17S3HCCT5DHQvKXnNDimqK4aaaQU\ngWMZQ+2C2GHoi9QaLtlwsA0EKWxH8zWmMFJ41mR2J8/WnTQJLYtOB4ifcsi53tZw\nnY8kD4uCu7ntlWLdvw8omGsCAwEAAQ==\n-----END PUBLIC KEY-----\n"
    },
    "nomadicLocations":[
      {
        "id":"https://hub.somaton.com/locs/testc1",
        "type":"nomadicLocation",
        "locationAddress":"acct:[email protected]",
        "locationPrimary":true,
        "locationDeleted":false
      }
    ]
  },
  "object":"https://pixelfed.social/users/motedting",
  "to":[
    "https://pixelfed.social/users/motedting"
  ],
  "signature":{
    "@context":[
      "https://www.w3.org/ns/activitystreams",
      "https://w3id.org/security/v1"
    ],
    "type":"RsaSignature2017",
    "nonce":"034d9b243b5930e65246b411e2d796c3aca94fd28395710deef95457ef7f2984",
    "creator":"https://hub.somaton.com/channel/testc1/public_key_pem",
    "created":"2018-12-30T01:59:48Z",
    "signatureValue":"OlYg5mFeTNMWgwmCJpgfTkjVcY3zmz1bzGKuLrNlglZHW88et9pUMK0lmQF63/iSZuEfmYgdmScohXpnt042rN9D2dcqaRoyhfggKlzXE3kouCPVUrNwMV/rFCuqiPid4kRugJULS1dLYyNXz7HvTVvl8HYKyMNKqZcZMdJrKoUYr6EgWesm5G8EeqxJTUDQ3M8rrmvz/+lMAmabmv6WOrTqXiLOE4VPpkmaEyGZasXWceoIFSt1280sQ0Gr6m+WCU/kG7/etgOFGfLi63MwBh/134Dueag5DfO61yAvuFMTUHcaMeJ/XHT4ck4xtDXQBLGhdaJeFuFIqp9GBaBrjGRWSe1SyJFR6qT+gk9lJKLKoUQXH4zc0NqlpUYYGZZRlBt2bI8FF8Sgte1tUa6U4nZHAScRcPPfQBqeiV/RNdbz15P6uhVqFh6x3Vlgis6CDnRnHgGWE/qXzqQWtcfDyxmQxAxY+WLWECtJOeEUDDR6OaGpiKIXOE82OIgkYsfGBFT/On++B2FT0jkrNLYDTN9r/j8QNGwc6XWA8zbax8I/CO5OYYZBo+goqHRaQYErffsvTX/OkHokQ59QebfNaXsp+dRKdociVxUfv8qTmTVqlVoyK5gLllu7GpDo+a5oJ7BCYm1oiHGEDGLeLvLuIURiBGXxzXfsAxAVNBOmBnA="
  }
}

Currently we can post a set of images in 2 ways: as an album, with one "title"/"legend", and a set of images, seen as a "slideshow" (one by one); or a collection, with a collection title and the set of images, all together. At least in Pixelfed UI
But it's not possible to see a set of images + a title (or a short comment ?) for each of them.

Proposal: allow a collection to show a per-image title.
I see 2 possibilities : 1) include the original image description/legend 2) add a specific title in the collection.

1. could result in long test bellow the image, while it's the fastest to use and maybe the easiest to develop (?).
2. is longer to use, but allow for short titles (even if the original image had a long description), and title only for some images.

Use case examples: as an user, I want to publish a collection of pictures from different places, and indicate which one is from where. Or a series of wildlife pictures on a common theme (= collection title) with their names/species bellow the pictures. And so on.

What do you think ?

Most organisations (or associations) use LDAP for user management. It is the case for my own infrastructure.

I would like to provide a PixelFed instance for my users, but for that it needs to integrate into the "single account" policy.

Adding LDAP support might be a little tricky as user names can have special characters that are not allowed by Mastodon (maybe it would break the federation). For instance, on my infrastructure the username is always the email adress on the form [email protected].

Therefore either username allow dots and "@", or better the user should be able to log either with his username or with his email adress. When a user connects for the first time with his email then he is asked to choose a username.

See the following thread for Mastodon support of LDAP:

• mastodon/mastodon#7857
• mastodon/mastodon#6830

If I have an instance with only one user and registrations are closed, it might be nice to (optionally) have the main page redirect to the profile page of the only user rather than the "Registrations are closed/Try to log in" page.

It would be trivial to implement the API to check against passwords used in data breaches in javascript for the registration page.

API Docs: https://haveibeenpwned.com/API/v2#SearchingPwnedPasswordsByRange

Comments from external fediverse (i.e. from some mastodon instance) accounts don't have their custom emojis rendered in the pixelfed instance website, as you can see here:

https://pixelfed.social/p/PixelFed/12348

Expected result: Custom emoji showing on comments

Actual result: "This is a custom emoji test :blobcat:"

If you have accidentally created a private post and you want to make it puplic afterwards, you cannot do it, because there is no edit option to change the private flag.

Version: 0.10.6 beta

I would really like to see an autocomplete overview of popular hashtags while entering a hashtag in an image description field (like a list of hashtags that contain the entered letters and the corresponding number of hashtag appearances on the fediverse).

I think this is necessary to reduce scattering and would improve features like following hashtags, hashtag-album and stuff like that.

I understand the common user won't do these, but some power/ high profile users may need these to reinforce the account security...

"Disable the use of e-mail address for login and recovery"

Should be possible disable the use of e-mail address for the login username and login recovery.

The e-mail is a widely know security vulnerable vector of attack, that is almost impossible for the common user to protect.

"Dedicated username just for the login"

In alternative the network should generate a dedicated random login username, ex: "zvs2j-fkqfx-kbpti" plus the user chosen password to login into the account.

The use of the special random login username, for both normal login and for the recovery... prevents hackers from just asking access using the public known e-mail, specially if they get access to it.

... or just use "SQRL" suggested bellow at number 5.

"Special account recovery username & password"

To recover access to the account you could have a special username & password, randomly generated by the server, say:
Recover username: 7urvv-3rp5w-ddic4-7t3ry
Recover password: pfrp3-v9rj6-c7w25-xd3f5

Using these special recover data the user should be logout and ask to login again normally and then asked to enter the recover username & password to make sure the user really knows it and only then by entering it correctly activate the use of it, otherwise the functionality stay inactive until the user produces new values and successfully logins with those.

The change of them should require knowing them, to prevent hackers from modifying them after a successful attack on the normal username & password login.

Of course the e-mail login use and e-mail recovery could be available by default, but users be offered these upgrade to make stealing social accounts harder.

... or just use "SQRL" suggested bellow at number 5.

"Provide secure notifications"

Usually users are notified by e-mail and/ or sms of things happening on the account, but since none of them are truly secure/ private solutions I would suggest the integration of Threema Gateway into the platform.
Unfortunately I'm not aware of a similar free substitute for these kind of notifications on a messenger platform that are both secure and private end-to-end.
If one such thing exists or is created for free then even better.

What would be notified?

• Login into account;
• Use of recover username & password to access the account;
• Attempt to change the e-mail;
• Attempt to change the password;
• Attempt to create/ disable/ change second factor;
• Attempt to change username;
• Attempt to delete de account;
• Attempt to delete/ change the notification recipient, should request a confirmation code, but allow the action to be blocked by the user to prevent hackers from modifying it, and also allow say 7 days before automatic accept the change, so that if the notification can't be delivered because the device no longer exists the user still can change to a new recipient.
• Creation of recover username & password to access the account;
• Send confirmation code to make sure is really the user (with IP/ browser/ App of the device trying to access) in addition to the username & password, and even if other second factor is activated (Webauthn/ FIDO2 for example);
• New publish attempt on the account (confirmation code), optionally enable for higher account security;
• Attempt to delete one/ multiple thing(s) on the account (confirmation code), optionally enable for higher account security.

"Support more secure login technology"

SQRL (Secure Quick Reliable Login) (https://www.grc.com/sqrl/sqrl.htm) seems a better/ more secure way to login and in and by itself solves all the problems at once [nothing private for the server to loose, recovery of the account, lock recovery access (if supported by the platform) to just allow the use of the secure SQRL to login], effectively preventing all the work suggested in suggestion two (2) and three (3)above.

SQRL is to substitute the need for login username & password. FIDO/FIDO2/Webauthn second factor, for example, can still be used for extra security.

The use of SQRL allow even for the platform to not need to use the e-mail address at all, being better to comply with privacy laws around the world by not requiring a information that is not really needed to use the service.

"Prevent large account creation of SPAM accounts"

• Captcha services should be supported to prevent mass creation of SPAM accounts;
• The mandatory use of "Threema" may reduce a little the SPAM since there is a one time small payment needed use the software;
• Special question/ answers made by the Admin to prevent random bots from getting in.

I'd love to be tipped in Monero, and probably a few other cryptocurrencies, would it be possible to add such a field to the sponsor area?

Hello,

When we play a video, it loops automatically. It would be more practical if we had an option to disable it.

When trying to upload an image as avatar, the message appears, that the size exceeded 2MB. It would be nice when the image is automatically resized and maybe the cutout is selectable

I'd love to see the ability to add some metadata to pixelfeds profile like Mastodon does e.g. adding a link to your Mastodon account or Twitter etc. Right now you have to type it into your bio.

Why store more than one copy of the same file?