17744 results for "bridgy"

  • we have a long running thread about using p-summary for plain text fallback behavior in general, so I wonder if that's a good signal for Bridgy Publish to use on "unknown" post types as an explicit fallback
    [tantek] at 2023-10-11 00:29
  • [snarfed] agreed with keep Bridgy Publish simple! The special Bridgy markup makes sense. Another standards based way could be plain text p-summary markup.
    [tantek] at 2023-10-10 23:28
  • I’m seeing the same “Translate” links on Bridgy Fed posts too.
    [manton] at 2023-10-10 22:03
  • Bridgy classic has an option for publishers to provide the explicit text they want POSSEd, https://brid.gy/about#silo-content , I could do that in BF too
    [snarfed] at 2023-10-10 21:35
  • a la "keep Bridgy Publish dumb"
    [snarfed] at 2023-10-10 21:34
  • I love that for people to choose on their own sites, but I was reluctant to lean far into it in Bridgy classic, since it has more potential to surprise users if they don't expect it
    [snarfed] at 2023-10-10 21:33
  • [aciccarello] yup. https://github.com/snarfed/bridgy-fed/issues/442
    [snarfed] at 2023-10-10 19:49
  • looking for some UX design advice for Bridgy Fed. is that better for here or #indieweb-dev?
    [snarfed] at 2023-10-10 19:24
  • I'd rather they fix that then have bridgy-fed render everything as a note...
    [aciccarello] at 2023-10-10 19:18
  • (https://github.com/snarfed/bridgy-fed/issues/662#issuecomment-1754012915 )
    [snarfed] at 2023-10-10 18:49
Sort by:

Filter results by:

Tag

Query took 0.01s.


Search tips

Exclusion
+foo -bar
Logical OR
foo OR bar
Exact phrase
"foo bar"
Partial words
foo*
Particular fields only
title:foo
domain:example.org
nick:somebody
after:2016-11-23
before:2016-11-23
date:2016-11-23