378668 results for ""a""

  • i know for a fact this will fail with pleroma/akkoma users
    trwnh at 2025-07-03 05:22
  • domain/@handle is becoming a de facto
    [tantek] at 2025-07-03 05:20
  • Who else uses gravatar besides WordPress/Automattic and GitHub (which I realize is a lot)?
    [tantek] at 2025-07-03 05:20
  • this is a mastodon-specific url pattern, it doesn't need to be /@localpart and different softwares do different things (/localpart, /~localpart, /, it's completely arbitrary) > @example.com@example.com -> https://example.com/@example.com
    trwnh at 2025-07-03 05:20
  • if i understand correctly the target use case of libravatar is to operates on email addresses rather than on websites (like gravatar before it), so it's not a 1:1 comparison. the problem is that everything in the space still uses gravatar directly and doesn't care about libravatar> libravatar is dead compared to rel=icon which is simpler and requires less power (HTML)
    trwnh at 2025-07-03 05:16
  • that was kind of my point, in practice the software that implements activitypub expects you to have implemented a big chunk of it. the ecosystem doesn't lend itself to small modular components providing individual portions of a social network service
    aaronpk at 2025-07-03 05:10
  • the problem with this is that fedi expects specifically acct: URIs which require a localpart and a domainpart, since it represents a user account on a given service. "fun" fact, the localpart of an acct: URI can be an email address, not specifically a username :-) > it really should be simply `@domain`
    trwnh at 2025-07-03 05:08
  • in theory for just a reader, you can implement GET outbox (if the actor publishes an outbox and allows GET); this is almost directly analogous to an rss/atom feed except the data format is activities instead of entries, and you also probably have to deal with paging which differs across implementations > I don't want my reader to also have to implement ActivityPub pieces.
    trwnh at 2025-07-03 05:03
  • technically you can choose to implement the outbox and/or inbox separately. the problem is that doing this isn't enough for fedi; you need to also implement a bunch of extra stuff like webfinger and http sigs cavage draft, and that's leaving out the issue of assumed schemas entirely... > activitypub is kind of all or nothing [...] it doesn't lend itself well to modular design
    trwnh at 2025-07-03 05:01
  • it might be great if that actually worked consistently... in most cases the http signature is from a proxy actor and not the user-associated actor > well it does enable fetching protected posts since it authenticates the requester
    trwnh at 2025-07-03 04:58
Sort by:

Filter results by:

Tag

Query took 0.03s.


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