T
@codl the one time i got an actual dm regarding that, it was a zionist upset that i had boosted something that wasn’t overtly critical of bds
on the other hand there have been occasions where i will find myself blocked by someone and have no idea why because they seemingly think i’m not being genuine in asking for feedback, or perhaps they do not consider my capacity to change, or maybe they never read my bio at all. who knows
basically if i’ve ever done anything wrong, no one has told me that
if i were sisyphus i would flatten the mountaintop so the boulder stays in place. i would make a little crater
@alice merkle tee $20 on my merch store
@Juju where are the good boys
every app having its own notification sound is one of those ideas that sounds cool but then you realize it should not be a per-app feature, it should be a system-level feature
@oblomov i mean if you say boundary="-" then the separator becomes --- but your markdown content might include --- as what gets rendered into an <hr> element
something like
```
---
foo: bar
---
stuff.
---
more stuff.
```
could get parsed as 3 parts instead of 2
it would probably be more correct to define application/mdx or whatever (since the typical intent is to be processed by something like an MDX processor), but i haven't really looked into the particulars of doing this properly and making it modular (instead of hardcoding semantics of "toml frontmatter, --- separator, markdown body")
revisiting: i discovered the iana media type multipart/mixed which could basically be this, just with a little modification https://www.iana.org/assignments/media-types/#multipart
the thing is the "boundary" parameter in multipart media types expects to be concatenated to a -- so you can't express the typical --- or +++ without problems (a markdown horizontal rule --- would get parsed as a multipart boundary)
still there's probably some inspiration to be had there, you could define an application/subtype that does similar
@steve for the ux features that mastodon api provides, there is no reason to shoehorn them into ap c2s. something like search can be its own api, and it is highly dependent on which data source you use to fulfill that request. it is valid to have a mastodon instance providing a search api but being able to bypass it with a direct POST to outbox when desired. you can then let all clients know that the outbox was updated, e.g. by sending them an activity
@codl i am content in the knowledge that my reply is a universal truth whether it is acknowledged or not
@steve i still think the way forward is less that an activitypub client should hook into mastodon, but rather that mastodon should become the activitypub client. a lot of the ux expectations of mastodon are driven by the abstraction of the all-knowing“instance”, but this doesn’t have to be monolithic. storage and delivery can be outsourced to a generic activitypub server. but that would require people to care about activities instead of statuses.
@silverpill @steve “all servers expect a short name” is exactly the problem. you can’t expect everyone in the world to use the same short name. this is a recipe for ambiguity and semantic confusion… which is a problem that exists regardless of whether you specify a @/context or not.
i ordered a hot dog and it arrived with a bite taken out of the hot dog. not the bun, just the dog.
how it's going
(somewhere in this tree of tabs is a wikipedia article on smoked salmon)
@0x2ba22e11 @codl that’s numbergllang!
@raphael i’m not sure how feasible it is to standardize “skills” descriptions, but the goal would indeed be to find some mapping between natural language and machine-parseable assertions/claims. there is some prior work from 2002 but i don’t really find it as an adequate solution: http://rdfs.org/resume-rdf/
having a database of potential candidates that you can query for leads is useful, but it would be interesting to consider a model where you basically swap the application requirement around so that the resume/cv is optional and the cover letter is required. like, as a thought experiment.
maybe i have no idea what i’m talking about, but it is incredibly demoralizing to get filtered out by automated systems to the point that i have had more relative success with direct messaging than in applying.
like, okay, congratulations, you’ve drained the soul out of the whole thing. good job!
imo the ideal is that a firm should describe accurately and precisely what it is trying to do, and a candidate should describe convincingly how they can fulfill the responsibilities. the “application form” attempts to normalize this into structured data, but it also normalizes out the human factor. it would almost be more effective to shoot them an email or something… if not for the massive volume of noise.
tangentially, i was discussing linkedin and job applications with a couple of friends, and my takeaway is that the hiring process for most firms is actually paradoxically making itself worse. consider how a resume/cv is required in most cases but a cover letter is not. this just results in a flood of applications for which you struggle to establish any sort of context on why a person would be a good fit. even worse are applicant tracking systems which downrank you for not using specific keywords
@codl i don’t mind footnotes but i’m wondering how you would replace their function in a way that preserves their semantic utility. probably by using the <aside> element somehow?
footnotes are the kind of thing that i use to stuff supplemental material outside of the flow of the actual content