GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    dansup (dansup@mastodon.social)'s status on Wednesday, 10-Apr-2024 20:12:13 JST dansup dansup
    • pixelfed

    Experimenting with separate hashtags in the @pixelfed app

    Before vs After

    Wdyt?

    #askFedi #pixelfed #pixelfedApp #pixeldev

    In conversation about a year ago from mastodon.social permalink

    Attachments


    1. https://files.mastodon.social/media_attachments/files/112/246/617/287/499/869/original/921e2b70dbb2754a.jpg

    2. https://files.mastodon.social/media_attachments/files/112/246/617/613/756/430/original/e4caf7eceb7d8063.jpg

    3. https://files.mastodon.social/media_attachments/files/112/246/619/802/766/480/original/a71641735a85ab1d.jpg

    4. https://files.mastodon.social/media_attachments/files/112/246/620/881/307/894/original/3520ed057921ecac.jpg
    • Tim Chambers repeated this.
    • Embed this notice
      nicolas ⁂ (nclm@mastodon.social)'s status on Wednesday, 10-Apr-2024 20:15:11 JST nicolas ⁂ nicolas ⁂
      in reply to
      • pixelfed

      @dansup @pixelfed Looks good! Much cleaner and more parseable. I do however think it’s important to keep the capitalisation and the tag order that the person chose? Those can convey meaning.

      In conversation about a year ago permalink
    • Embed this notice
      HerrHerrmann (herrherrmann@mastodon.social)'s status on Wednesday, 10-Apr-2024 20:17:30 JST HerrHerrmann HerrHerrmann
      in reply to
      • pixelfed

      @dansup @pixelfed I think it’s helpful to have them shown in this new button style!
      I’d also suggest increasing the line height of the description text. Currently, it’s very tight which doesn’t look great, and makes reading multiline descriptions harder.

      In conversation about a year ago permalink
    • Embed this notice
      Chee Aun 🤔 (cheeaun@mastodon.social)'s status on Wednesday, 10-Apr-2024 20:19:08 JST Chee Aun 🤔 Chee Aun 🤔
      in reply to

      @dansup from my observation (in IG), most folks there purposely "hide" hashtags by putting in a lot of newlines (and force "show more") or add them via a comment instead of post description. Surfacing them this way seems to undo their intentions in my opinion 🤔

      In conversation about a year ago permalink
    • Embed this notice
      ITX Mike (mspsadmin@msps.io)'s status on Wednesday, 10-Apr-2024 20:24:53 JST ITX Mike ITX Mike
      in reply to
      • pixelfed

      @dansup @pixelfed I'm old school and don't like the overall UI push to more whitespace/vertical spacing. This is minor but still, tend to prefer tags that are different color so they stand out. But also realize that's not fully accessible. Buttons certainly make tag navigation more likely. So on fence 😂

      In conversation about a year ago permalink
    • Embed this notice
      Børge (forteller@tutoteket.no)'s status on Wednesday, 10-Apr-2024 20:35:14 JST Børge Børge
      in reply to
      • Chee Aun 🤔

      @cheeaun @dansup Yeah, but didn't nt they do that because all the tags are noisy, which this UI would fix? That manual way of hiding tags is more work for those posting, and annoying for those reading, because they can't know if there's a read more link because there's a new paragraph of actual text, or just tons of tags. So people have to press the read more all the time just to check, wasting everyone's time.

      What if the tags are separated out, like this, but also hidden behind "Show tags"?

      In conversation about a year ago permalink
    • Embed this notice
      Habib (habibcham@mastodon.social)'s status on Wednesday, 10-Apr-2024 21:40:39 JST Habib Habib
      • Eugen Rochko
      • pixelfed

      @dansup @pixelfed @Gargron After + limit with Show All. 👏

      In conversation about a year ago permalink
    • Embed this notice
      naught101 (naught101@mastodon.social)'s status on Wednesday, 10-Apr-2024 22:17:39 JST naught101 naught101
      in reply to
      • pixelfed

      @dansup @pixelfed absolutely. Much better.

      In conversation about a year ago permalink
    • Embed this notice
      Elengale (elengale@mastodon.social)'s status on Wednesday, 10-Apr-2024 22:34:58 JST Elengale Elengale
      in reply to
      • pixelfed

      @dansup @pixelfed *Strongly* prefer the separated hashtags where they're parsable (I've mixed thoughts on how to handle inline #hashtags as opposed to ones put at the end).

      It just looks so much cleaner.

      In conversation about a year ago permalink
    • Embed this notice
      Tim Chambers (tchambers@indieweb.social)'s status on Thursday, 11-Apr-2024 09:53:59 JST Tim Chambers Tim Chambers
      in reply to
      • pixelfed

      @dansup @pixelfed After. Cleaner, clearer and less clutter.

      In conversation about a year ago permalink
    • Embed this notice
      Brian (brianch@mastodon.social)'s status on Thursday, 11-Apr-2024 10:39:52 JST Brian Brian
      in reply to
      • pixelfed

      @dansup @pixelfed I much prefer the new version, but as others pointed out, I think maintaining the case is important.

      I would also like for the # signal to be kept to make it more explicit, which I feel is specially more relevant when the hashtag is in the middle of the text for example (which I assume would still be possible, it would be horrible for them to always be at the bottom).

      In conversation about a year ago permalink
    • Embed this notice
      gergo (gergolippai@mastodon.social)'s status on Saturday, 13-Apr-2024 15:38:34 JST gergo gergo
      in reply to
      • pixelfed

      @dansup @pixelfed what would this do with inline hashtags? Ie if i use a hashtag in a sentence like
      "A nice #photo of #amsterdam canals"

      In conversation about a year ago permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.