@[email protected] if we do it and @[email protected] can't hack it does it get published anyway 😝

@[email protected] I'd say a protocol handler would be one small step in making this better handled.
The friction with a global "share to the fediverse" button is the instance chooser. Not knowing what your home instance is is a major sticking point.
A protocol handler could allow you to skip this step, assuming you have an app that has registered against it.
Otherwise, yes, the same fallback would need to continue to exist (enter your home server! blah blah)

@[email protected] I find it curious that this needs to be spelled out in an FEP.
Isn't a generic AP server one that ingests anything and shoves it into the outbox... like a mail transfer agent?
... then delivers it dutifully?
I mean, sure, you can do stuff in between, like spam detection, blocklists, etc etc etc...
My quick read through of the FEP (and it was quick, because it was a short FEP :stuck_out_tongue:) seems to confirm this.

@[email protected] hard to gauge where to draw the line, but that is not what @[email protected] is suggesting.
There are DNI lists of varying severity, from "worst of the worst" to "all that plus a couple more you probably want"
But the key here is a sensible default and administrative choice. Nobody is forcing anything on anybody here.

@[email protected] nice! Will you be around tomorrow evening? Let's catch up!

@[email protected] add and remove feel more like building blocks than actual activities.
It would never capture the nuance of many of the activities that it would purportedly represent.

@[email protected] I'm sorry you feel that way. I agree that I suppose there hasn't been a lot of true R&D lately, though a lot of that could be we're just shipping with little fanfare.