Skip to content
  • Categories
  • Recent
  • Popular
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

NodeBB-ActivityPub Bridge Test Instance

trwnh@mastodon.socialT

trwnh@mastodon.social

@trwnh@mastodon.social
About
Posts
215
Topics
31
Shares
199
Groups
0
Followers
1
Following
0

View Original

Posts

Recent Best Controversial

  • nothing worse than typing a really long thing on ios safari and switching tabs to check something only for ios safari to inexplicably refresh the first tab and eat everything you wrote -_-
    trwnh@mastodon.socialT trwnh@mastodon.social

    why is everything related to typing on ios such a pain

    Uncategorized

  • nothing worse than typing a really long thing on ios safari and switching tabs to check something only for ios safari to inexplicably refresh the first tab and eat everything you wrote -_-
    trwnh@mastodon.socialT trwnh@mastodon.social

    nothing worse than typing a really long thing on ios safari and switching tabs to check something only for ios safari to inexplicably refresh the first tab and eat everything you wrote -_-

    Uncategorized

  • Questions:
    trwnh@mastodon.socialT trwnh@mastodon.social

    @asoftdessert @mcc one thing that is funny about content formats is that a lot of them have metadata headers and content bodies, but you can just stuff an entire head+body into another body with its own head, matryoshka style. you can just keep doing this arbitrarily as long as your consumer knows which layers to unwrap and how

    anyway for http i think http resources having headers plus the HEAD method can work with zero unwrapping

    if you wanna conneg media type perhaps application/oembed+json?

    Uncategorized

  • Questions:
    trwnh@mastodon.socialT trwnh@mastodon.social

    @mcc i think ive posted before about an idea for what is basically http HEAD but it also returns html <head>. or otherwise some http headers that fulfill the same use case as opengraph, so the existing http HEAD can return those.

    Uncategorized

  • @trwnh have you looked over this explainer?
    trwnh@mastodon.socialT trwnh@mastodon.social

    @evan a bit, but not in depth -- it's on my todo list

    Uncategorized

  • "@context": [
    trwnh@mastodon.socialT trwnh@mastodon.social

    @reiver @thisismissem but more importantly: before defining such terms, consider what you are actually trying to do with them practically. how do you intend to process them? what's the use case? which information do you need and why? ask yourself those questions first.

    Uncategorized activitypub activitystreams fedidev fediverse jsonld

  • "@context": [
    trwnh@mastodon.socialT trwnh@mastodon.social

    @reiver @thisismissem instead of making up properties that don't exist in a namespace that you don't own, you should use something that someone else already defined properly within their own authority, or otherwise define stuff under your own authority.

    for example: CITO is an ontology for citations http://purl.org/spar/cito

    see also http://www.w3.org/ns/prov#Quotation or http://purl.org/spar/fabio/Quotation

    Uncategorized activitypub activitystreams fedidev fediverse jsonld

  • genuine question: what do people like about Substack?
    trwnh@mastodon.socialT trwnh@mastodon.social

    @hornblende medium used to be nice to read, that was the initial draw to medium, people even made css that cloned medium's layout and typography like medium.css

    medium got a lot worse after they tightened the vise that is capitalism (article limits, annoying popups, etc)

    Uncategorized

  • genuine question: what do people like about Substack?
    trwnh@mastodon.socialT trwnh@mastodon.social

    @capeta would it be fair to say the integrated newsletter is the main draw then (plus i guess monetization)? i know you can run those separately but i can see how it would be convenient to have multiple ways to publish under one roof

    Uncategorized

  • genuine question: what do people like about Substack?
    trwnh@mastodon.socialT trwnh@mastodon.social

    genuine question: what do people like about Substack? it feels like the new Medium but idk what it offers that actually draws people to it

    Uncategorized

  • @julian @darius Hugo does the same by default, taking the first ~70 characters to the nearest word boundary (or something like that).
    trwnh@mastodon.socialT trwnh@mastodon.social

    @julian @darius Hugo does the same by default, taking the first ~70 characters to the nearest word boundary (or something like that).

    i'm just pointing out that there might be some needed disambiguation with how `summary` is used, to account for this kind of "excerpt vs subtitle", "duplicative vs additive" usage.

    Uncategorized

  • So I'm improving Article display in Hometown.
    trwnh@mastodon.socialT trwnh@mastodon.social

    @darius @julian @technical-discussion one thing this suggests is that there is a semantic difference between "summary" in the sense of providing a short blurb that is additive to the content (kinda like a subheading!), vs "summary" in the sense of providing an excerpt to be used as a kind of preview (as in a list of articles)

    Uncategorized

  • So I'm improving Article display in Hometown.
    trwnh@mastodon.socialT trwnh@mastodon.social

    @darius @julian @technical-discussion interestingly https://indieweb.org/post-type-discovery#Algorithm suggests that you check if the `name` is a prefix of `content`, and if it is, then it is a Note. perhaps similar logic can be used to check if `summary` is a prefix of `content` in some way?

    i don't think this is particularly *wrong*, as generating summaries from excerpts of content is a common pattern in e.g. static site generators like Hugo. it is indeed duplicative, though!

    Uncategorized

  • I realize the frustration regarding the Loops delays.
    trwnh@mastodon.socialT trwnh@mastodon.social

    @dansup @hiphopheaven @shlee @matlfb team of *devs*, specifically, not just auxiliary roles

    Uncategorized loops tiktok activitypub

  • @helge @julian several do, but not in all languages.
    trwnh@mastodon.socialT trwnh@mastodon.social

    @helge @julian with that said: we'd have less complexity if everyone used fully expanded jsonld without any context, because that would make it so that there's exactly one correct canonical way to express anything

    ...at the cost of readability. which is really why context exists: to allow for using more readable shorthand, without losing the mapping to the unambiguous form. with enough context you should be able to map any arbitrary json to an unambiguous generic entity-attribute-value graph.

    Uncategorized

  • @helge @julian several do, but not in all languages.
    trwnh@mastodon.socialT trwnh@mastodon.social

    @helge @julian of course, if you had a central registry of allowed symbols and their definitions, then that means you can't just add whatever you want to extend the data. we've seen this in atproto where the end result of their lexicons is that you have to create sidecar records and have prior out-of-band knowledge on which lexicons you need to check.

    Uncategorized

  • @helge @julian several do, but not in all languages.
    trwnh@mastodon.socialT trwnh@mastodon.social

    @helge @julian several do, but not in all languages. here are the ones that conform to the test suite https://json-ld.org > "developers"

    without a json-ld processor, you will end up reimplementing parts of json-ld anyway, and you have to be consistent with something whose definition you are unaware of. is your Public my Public? which natural language is that string? is that even a string, or is it actually a reference? json-ld is one answer. the other answer would be a central registry.

    Uncategorized

  • @julian it literally would be!
    trwnh@mastodon.socialT trwnh@mastodon.social

    @julian it literally would be! instead of 100 different attempts at producing almost any json, you would have everything coerced into a data model with a single canonical output that can be serialized deterministically

    Uncategorized

  • @helge @julian i don't think the bugs would go down.
    trwnh@mastodon.socialT trwnh@mastodon.social

    @helge @julian more serious answer: if everyone used a proper json-ld processor, the output would be more consistent.

    Uncategorized

  • @helge @julian i don't think the bugs would go down.
    trwnh@mastodon.socialT trwnh@mastodon.social

    @helge @julian i don't think the bugs would go down. never underestimate the bug-generating capacity of fedi devs ​ ​

    Uncategorized
  • Login

  • Login or register to search.
Powered by NodeBB Contributors
  • First post
    Last post
0
  • Categories
  • Recent
  • Popular