oddly ominous amazon product promotional image
Remote
infinite love ⴳ
@trwnh@mastodon.social
mastodon 4.8.0-nightly.2026-10-06i have approximate knowledge of many things. perpetual student. (nb/ace/they)
xmpp/email: a@trwnh.com
https://trwnh.com
help me live:
- https://donate.stripe.com/14kg1Og6J4jvfbW145
- https://liberapay.com/trwnh
notes:
- my triggers are moths and glitter
- i have all notifs except mentions turned off, so please interact if you wanna be friends! i literally will not notice otherwise
- dm me if i did something wrong, so i can improve
- purest person on fedi, do not lewd in my presence
3213 Followers
340 Following
50 Posts
Joined November 24, 2016
Website:
Portfolio:
Fan of::
Punk-rock and post-hardcore (Circa Survive, letlive., La Dispute, THE FEVER 333)Manga (Yu-Gi-Oh!, One Piece, JoJo's Bizarre Adventure, Death Note, Shaman King)Platformers and RPGs (Banjo-Kazooie, Boktai, Final Fantasy Crystal Chronicles)
What to expect::
talking about various things i find interesting, and otherwise being a genuine and decent wholesome poster. i'm just here to hang out and talk to cool people! and to spill my thoughts.
sister meant to say "brainrot" but accidentally said "brainslop" and now i'm like wait this makes too much sense keep cooking
hex editor but for witches
Replying to
@kopper@not-brain.d.on-t.work @hongminhee@hollo.social i think you could upload the binary media to one endpoint, get an https: url for its Location header, and turn around and Create an Image or whatever with that Location header as the url.href of your new Image
although now that this topic comes up: there is a lack of clarity around "image" vs "image representation", since Image assumes "image" and not "image representation". as:url is nominally that "representation" and i wish it was better defined that this was the case...
Replying to
@kopper@not-brain.d.on-t.work @hongminhee@hollo.social (think of a CDN or image proxy server that lets you live-resize images or convert to whatever format using query parameters, then think about how that maps to AS2, then cry a lot)
evil* idea for likes/shares/etc collections that allow interactions by direct POST. instead of POST to inbox you just POST to the collection. the collection can return 4xx if your interaction isn't accepted, and if it's missing you just "can't" interact that way. basically every interaction collection could be its own "inbox" in a way. you could still use something like AP outbox delivery to forward published activities to appropriate targets.
*not really evil
Assigned Gender At Registration
anyone know of any good free checking accounts? my current checking account recently instituted a $5/month charge and this is as good a time as any to move off, but idk what my other options are.
my main considerations are:
- no fees
- no interest
- a website that doesn't suck
Replying to
@kopper@not-brain.d.on-t.work @hongminhee@hollo.social it's a bit of an extreme example when the smaller case is: you have an image that has a jpg and also has a 2nd jpg for smaller viewing sizes. or like srcset in html at different media widths. Image.url is sorta parallel with img src at that point or picture source
Replying to
@benpate@mastodon.social @reiver@mastodon.social "POST a thing to a collection" is a design pattern that has come up multiple times, for what it's worth. It might make sense to reuse it here as well.
Replying to
@cwebber@social.coop i suspect we are not thinking of the same song https://www.youtube.com/watch?v=k-lf9CIZ9OM
Tanjaret Daghet - Ta7t El Daghet / Under Pressure (Official Music Video) l طنجرة ضغط - تحت الضغط
Replying to
@hongminhee@hollo.social This is all covered in more depth in https://github.com/w3c/activitypub/issues/404 including examples of vocab-relative terms and examples of undefining the as: prefix.
Replying to
@hongminhee@hollo.social It was never entirely clear why the concept of a Public collection was used with properties used for a delivery mechanism. If you're supposed to special case it and not actually deliver to it, then why not separate it out so you don't have to special case it?
For backwards compatibility, I think it could be acceptable to mistake public objects to actually be private objects. (It would be a problem if private objects were mistaken to be public objects, but that shouldn't happen.)
Replying to
@hongminhee@hollo.social It's subtly more messed up than that. AP didn't explicitly allow all 3, but it calls out in a non-normative note that implementers may produce non-canonical serializations.
Right now, as:Public is canonical. Public would be canonical if properties like to/cc/audience were vocab-relative, but they aren't (and shouldn't be). Undefining the as: prefix results in the full URI being canonical.
I think introducing a vocab relative term for visibility could make sense, using Public.
Replying to
@cwebber@social.coop @bkuhn@fedi.copyleft.org @ossguy@fedi.copyleft.org @richardfontana@mastodon.social how do you launder proprietary codebases if the source isn't available? i just see this as 2 negatives since it would incentivize trade secrets
Replying to
@evan@cosocial.ca maybe some examples would clarify what you mean, but i'm not sure how to define "the actual game" in a way that everyone would agree they're playing it. like, what counts as a "loophole" and what counts as a fundamental use case? what makes a conclusion "ridiculous", or an interpretation "intentionally misinterpret[ed]"? these questions all depend on the frame of reference of whoever's asking them. i generally assume good faith whenever these things are being discussed. should we not?
i'm a firelover, not a firefighter
i sneezed about an hour ago and my upper right abdomen has been hurting since... that doesn't seem good :(
step-by-step walkthrough of cave story in the form of a concept rap album, started in 2009 and completed a few days ago https://www.youtube.com/watch?v=faBrzVHm7ow&list=PLtEPz7pWO1AXLRlsUjbjXhyd9I-24zaJo
01_Start Point
Replying to
@thisismissem @hongminhee imo the value of a did document is overstated -- did can be a useful framework for how to interact with identities that *can* be operated on and *can* have keys and *can* link out to other services, but none of those things are actually required and a lot depends on the actual did method to fill in that framework. in the case of did:key, the "key" method is just a thin wrapper around a key (for when that key is the identity). this makes the key valid for *any* purpose.
Replying to
@steve@social.technoetic.com @silverpill@mitra.social it's why mastodon went with the concept of "stamps" as http resources that could be fetched to retrieve latest state (200 / 404). you no longer need a complete ordered history of activities and you don't need to calculate the current state from those activities.
subscription records would work the same way and could be extended to allow subscribing only to certain activities instead of an unfiltered everything
Replying to
@steve@social.technoetic.com @silverpill@mitra.social the other question is if this level of explicitness is useful. the answer AP spec gives is "no, just assume every server SHOULD do this".
and a tangent for follows: they are too stateful. you send Follow and Accept and someone knowing about those two might assume you are a follower now but not be aware of later removal or undoing (of either the Follow or Accept). this is broken in practice for years because Follow/Accept follow is not expressive enough
Replying to
@silverpill@mitra.social @steve@social.technoetic.com so maybe instead of "generic activitypub server" the FEP should be called something like "explicitly specifying side effects with the result property". it seems to me like the references to 2277 and fe34 are not strictly necessary to the core idea and a separate FEP could bundle them together into a profile, like "a profile for using outbox activities to manage objects and collections". not sure what the best name is because naming things is the hardest
Replying to
@joncamfield@mastodon.social @khm i'm no genai lover but agency is very much not only for humans. agency is for anything that can perform an action. machines do things too, both manually and automatically; your web browser is literally an http agent. the focus should be on "what is being done" and "the people who decided it should be done".
Replying to
@npdoty@techpolicy.social @w3c@w3c.social
This group will discuss mechanisms for age-based restrictions to content
The only acceptable conclusion is that any such mechanism is wholly unacceptable.
If the intent is truly "bolstering safety for vulnerable populations such as children", then this intent is not achieved via "age-based restrictions". We should strongly oppose any "restriction" and instead reframe any such discussion around "consent". If one is asked for consent to see content and provides it, end of story.
https://www.wbrc.com/2026/03/30/judge-orders-central-alabama-water-restore-fluoride-drinking-water/
so basically our water company announced 10 days ago it was going to stop fluoridating our water, effective as of... 2 years ago
city sued the water company, judge ordered them to start fluoridating again, and of course anyone whose dental health worsened in the past 2 years is just written off
Replying to
@silverpill@mitra.social @steve@social.technoetic.com regarding as:result itself there are some other ideas that have come up in past years so good to discuss those in a more focused thread:
- either marking activities as the "result of" (maybe "in response to"?) another activity could update the other activity to refer to the later activities, or the "result of" property is defined as a @\reverse property of as:result
- quote stamps currently use result for the stamp itself, not a Create activity for it
Replying to
@kopper@not-brain.d.on-t.work @hongminhee@hollo.social ...at least, for an Image that has multiple representations, this is a lot more necessary than for an Image with only one representation.
it's really a question of what the identifier identifies. AS2 is un/fortunately loose enough that people stick ids of the blobs in the same properties that may or may not expand to an Image object with multiple url
lockerz
Replying to
@steve@social.technoetic.com @silverpill@mitra.social now if only AP had officially defined conformance profiles to this effect... (the "activity publishing profile" and the "notification delivery profile", to be clear)
Replying to
@evan in the Mastodon sphere, boosting a post has these side effects:
- servers that receive the boost will now be aware that the boosted post exists. if it contains hashtags, then that post might show up in hashtag timelines/searches and the home timelines of anyone following that hashtag.
- servers will also be aware that the author of the boosted post exists. their profile can appear in search results based on their account's name/summary. -- (in the future, their outbox might be backfilled)
Replying to
@steve@social.technoetic.com @silverpill@mitra.social i assume the Undo would have a result that describes that? so Undo(Follow) might have a result of Remove from Follow.actor.following+Follow.object.followers in theory. for the other way around the Follow doesn't have a result but the Accept(Follow) has a result of Add to Follow.object.followers+Follow.actor.following
but i think Follow is a bad example because it really should be subscription record management instead, ideally.
Replying to
@benpate@mastodon.social @reiver@mastodon.social HATEOAS would have you using links to do this. Perhaps this suggests that AP-style collections should take POST requests directly? For example, to Like a resource, you wouldn't necessarily POST the Like activity to only the attributedTo.inbox, you could POST the Like activity to the likes collection. Or you could define a link relation specifically for "this is the inbox you can POST a Like activity to", if the likes collection weren't suitable for whatever reason.
Replying to
@silverpill@mitra.social @steve@social.technoetic.com also the server's main responsibility being publishing and therefore needing to mint an identifier for the top level activity, we should ask if the server is expected to assign any inner ids as well? assigning ids changes the graph so it's not clear cut. is an open question (and maybe blank node identifiers are actually in practice required to avoid ambiguity?)
Replying to
@brooke@bikeshed.vibber.net @cwebber@social.coop ah, the "web browser in a web browser" experience
Replying to
@Johann150@genau.qwertqwefsday.eu in xml you would have
element foo="bar"
and it would be a bit awkward if "element" and "foo" came from different namespaces. also you wouldn't know right away that "bar" was a resource/thing/id.
the rdf/xml syntax uses about= and resource= for this kind of "the value is a reference id" disambiguation, but i wouldn't wish rdf/xml as a serialization on anyone. it's been decades since most people moved on to turtle which is easier because it's plain text
Replying to
@steve@social.technoetic.com @silverpill@mitra.social in theory POST to outbox should publish the activity, and should trigger the delivery algorithm based on audience (which is another thing handled poorly compared to even smtp which it tried to copy...)
imo that should be part of the protocol contract, and the idea of "side effects" unfortunately muddles that. the guarantee should be built into the outbox delivery algorithm and an outbox should signal this algorithm is in effect.
Replying to
@cwebber@social.coop @bkuhn@fedi.copyleft.org @ossguy@fedi.copyleft.org @richardfontana@mastodon.social sure, but my point is this would happen less often
Replying to
@silverpill@mitra.social @steve@social.technoetic.com so we might need to recommend that these "side effect" activities in as:result SHOULD have fragment identifiers, to be able to refer to them later? or do we intend to never refer to them later? we could say they're transient activities so don't need to be referred to later (only processed in-order).
lastly as:result itself maybe doesn't have these semantics defined, so should a subproperty or different property be used, or do we skip non-CRUD results?
Replying to
@evan@cosocial.ca sorry, i have no idea how to interpret this response in context of what came before it. what am i being thanked for? i was expressing confusion at the original premise.
Replying to
@evan@cosocial.ca one example that illustrates just how much contention there is about even supposedly basic things: are activities content? one might argue they are the primary reason the specs exist at all, to publish activities to activity streams. someone else might equally argue that they are simply vehicles for distributed CRUD of notes, which are the real content. the specs currently support both interpretations. should one be closed as a loophole? is one an intentional misinterpretation? which one?
Replying to
@silverpill@mitra.social @steve@social.technoetic.com the type information is largely unnecessary and shouldn't factor into handling CRUD, especially if the objects are managed by the client. the authorization/trust model for which activities are allowed to CRUD which objects is important but can be something other than fe34 (such as an explicit access control policy or authorization resource). also multiple CRUD mechanisms may be in use.
Replying to
internet searches seem to blame fractional scaling or multiple monitors but it still happens even when i disable all my monitors except 1 and also i always use 100% scaling (and attempting GDK_SCALE=1 doesn't fix it either)
Replying to
@Johann150@genau.qwertqwefsday.eu jsonld is a bit like xml namespaces but extended -- it tells you when strings are actually ids, it lets you use non-prefixed terms, it lets you do transformations of a sort
so a term definition like this
"foo": {
"@\id": "https://foo.example/",
"@\type": "@\id"
}
means you can do this in the doc
"foo": "bar"
and you know "bar" is an id and not just a string. and you know "foo" is specifically foo.example.
xmlns iirc only let you do x:foo or set a default ns for all subnodes
Replying to
@silverpill@mitra.social @steve@social.technoetic.com it sounds like you're describing an "AP server" whose primary functionality is not "publish activities" but rather "manage CRUD for objects and Add/Remove for collections", by taking the AP "side effects" for Create/Update/Delete/Add/Remove and and saying the outbox should also check as:result.
which is cool but should probably be disambiguated.
Replying to
@starkos thank you, i'll look into them! is there anything in particular you like about them?