"*" search results - search chat.indieweb.org

1671571 results for "*"

I don't POSSE to Mastodon. My website federates directly with Mastodon followers via BridgyFed
[tantek] at 2025-05-08 21:26
I suppose the same would apply for POSSEing to Mastodon but this is for direct federation
[tantek] at 2025-05-08 21:26
I guess the POSSE argument makes sense, but since I don't POSSE, that doesn't affect my decision
btrem at 2025-05-08 21:26
So it's for POSSE? That's mentioned in https://indieweb.org/footnote. But there's also the claim that unicode characters are more readable than the wiki method. I disagree, as the unicode characters are quite a bit /smaller/ than the wikipedia style. So much smaller that I can't read them
btrem at 2025-05-08 21:25
Mastodon, for example does not allow ^{so if you use that in your post to depend on making footnote refs look smaller and superscripted, it will not show up on Mastodon views / replies / reposts of your posts}
[tantek] at 2025-05-08 21:25
unicode superscript numbers are "plain-text" and thus far more syndication safe. e.g. they make it through to Mastodon views of my posts, e.g. when people repost or reply on Mastodon
[tantek] at 2025-05-08 21:23
Or, if it could know, I can't think of how
btrem at 2025-05-08 21:22
two different questions. there is prior art for using smaller superscripted numbers per every print style guide in the world like since forever. CMoS etc
[tantek] at 2025-05-08 21:22
[KevinMarks] has 11 karma in this channel over the last year (28 in all channels
Loqi at 2025-05-08 21:22
[KevinMarks]++ thanks for replying yesterday re: keeping track of footnote numbers. Sorry, I only just now saw your reply. I think a macro would have the same problem. Each macro call is independent. It wouldn't know that it had already been called on that template
btrem at 2025-05-08 21:22

Sort by:

Relevance Date

Filter results by:

Tag

Query took 0.1s.

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