Gordon Brander

That exploration references an earlier version of Subtext that has been superseded by the latest spec. Subtext now has a link form called a `/slashlink` that may be embedded in...

I lean toward `ipfs://` support. One of the design decisions we made for Subtext is to support pasting in bare links for common protocols (http and https, basically). Given we're...

> ...but rather rely on doing a full-text search for the direct text instead. As an aside, this is more or less how we plan to use `[[wikilinks]]`, albeit with...

If we do bring in something like this, my sense is that it should follow the scroll-to-text approach https://wicg.github.io/scroll-to-text-fragment/

My intuition is that we should err on the side of supporting unicode as written. OTOH I'm not well-versed in the history that led to percent-encoding in URLs. I suspect...

Points in favor of leaning into URL syntax as-spec'd: - You can delete the origin of a URL and it becomes a valid slashlink. A slashlink is literally a relative...

@cdata flagged IRIs which expand URI grammar to include most unicode characters, and have a backwards-compatible encoding scheme https://en.m.wikipedia.org/wiki/Internationalized_Resource_Identifier This seems like a compelling path forward that solves for both...

Decision: support Unicode characters in slashlinks, just like we do everywhere else. Just do whatever we need to do on the backend to encode/percent-escape when converting to URL form. This...

@snarfed we are keen on seeing ActivityPub interop emerge (indeed, any interop)

@bfollington here's my take on #46. Not sure if the method rename will cause too much carnage in Subconscious. If so, we could instead do: - `send(:)` synchronous but not...