#dev 2023-07-25

2023-07-25 UTC
TechLifeWeb, tei_1, tei_, [tantek] and cyberleolao joined the channel
#
Zegnat
Amazon also launched something called AWS App Runner which is a little more like Heroku et al. It can either deploy straight from a code repo or you can supply it a container to deploy. I have found that one a lot easier to setup (if you are already stuck in the AWS infrastructure) than mucking about the permmissions stuff for exposing lambda to the public net.
#
c​apjamesg
++
[marksuth], win0err, gRegorLove_, IWSlackGateway and [jamietanna] joined the channel
#
[jamietanna]
Capjamesg worth also trying http://fly.io for very little ops hosting. I've enjoyed it for several apps I'm doing
#
[jamietanna]
Also building for AWS Lambda and the like is generally different than just hosting a Flask app that's always running - you can do it, but there are things to be cautious of, and to get the best of it you'd maybe need to rearchitect it
#
[jamietanna]
Barryf got me into https://arc.codes which is a really nice local + remote experience for building more AWS Lambda native apps
[Murray] joined the channel
#
[jamietanna]
Looks like they have a Python runtime, but not sure what it's like compared to Node which is their preferred stack
lanodan, win0err, gRegorLove__, [tantek], tei_, IWSlackGateway, [Murray], oodani, [schmarty], [KevinMarks], [fluffy], geoffo and [manton] joined the channel
#
[manton]
Posted that blog post I alluded to… Let the hate mail begin! https://www.manton.org/2023/07/25/next-step-for.html
#
Loqi
[preview] [Manton Reece] Next step for ActivityPub
[tantek] joined the channel
#
[tantek]
[manton]++ solid post. direct and upfront
#
Loqi
[manton] has 20 karma in this channel over the last year (44 in all channels)
#
[manton]
Thanks!
#
[manton]
I’m really a little conflicted about the state of the social web right now. It’s kind of a jumble, without a clear path forward other than platforms supporting lots of different, overlapping protocols.
[snarfed] joined the channel
#
[snarfed]
it doesn't feel the best for development right now, but honestly I think it's good. we had a solid ~15y of social media stagnation, we're overdue for a big messy explosion of experimenting
#
[snarfed]
plenty of time and space to consolidate and standardize again later
#
[manton]
That’s a good way to look at it.
#
[manton]
I like the explosion, but less so the messiness.
#
[snarfed]
yup, understood. most people don't, me included. but maybe sometimes it's necessary
#
[manton]
I’m also very curious about the impact of Bluesky and Nostr. Feels like a fork that can’t easily be reconciled.
#
[tantek]
The suite of AP specs as you put it [manton] is itself a big improvement over the suite of OStatus specs overall, which were even more complex / messier.
#
[schmarty]
When Better Still isn't Good: The ActivityPub Story
#
[manton]
[schmarty] 🤣
tei_ joined the channel
#
aaronpk
omg [schmarty]
#
[schmarty]
i don't mean to sound so harsh about activitypub. "When Better Still isn't Good" could be like a sub-imprint of No Starch Press covering lots of tech. :}
#
[tantek]
[manton] worth IndieNewsing your post
#
[KevinMarks]
I agree with [pfefferle] that the test suite can drive the convergence - by measuring and documenting what you expect you can help adjust it.
#
[manton]
I guess a lot depends on who controls the test suite. Maybe I should write one. 🙂
[pfefferle] joined the channel
#
[pfefferle]
oh, missed most of the discussion
btrem joined the channel
#
[pfefferle]
it's becoming more real, [j12t] is pushing it a lot atm.
#
[pfefferle]
and as far as I understood it, [dansup] already had something working for the initial fediDB plarform
#
[pfefferle]
I still love the idea and simplicity of the initial idea of having standardized activities floating between inboxes and outboxes
tei_1 joined the channel
#
[snarfed]
agreed. most of the difficulty is in structuring and interpreting the activities (ie AS2), not in the protocol delivery (AP) per se
#
[pfefferle]
for me it is still easier to work with AP (even with reverse engineering some platforms) then reading through the AP-Spec!
#
[KevinMarks]
Also, the AS2 spec doesn't require JSON-LD parsing, we explicitly worked to make that clear, so part fo the test suite should be rejecting JSON-LD stuff that isn't in the canonical form
#
[tantek]
^ [manton] that's a key bit that is worth perhaps correcting in your blog post mention of JSON-LD
#
[pfefferle]
I am not entirely sure what Dave Winer is referring to... it still sounds like a reader/crossposter thing instead of federation...
#
aaronpk
I do not want to listen to Dave's voicemail, can someone summarize it?
#
[KevinMarks]
I haven't listened, but it's likely his version of the social reader idea, which will likley have outlining built in because his always do.
#
sknebel
reader feature: speech-to-text for audio posts? (also for search in podcasts)
#
[snarfed]
for someone who's so text focused, it seems odd that he sent what sounds like an important message that he cares about as an audio recording
#
[tantek]
it's a public podcast with an audience of one right?
#
[manton]
Pretty much. I think Dave is mostly coming from the client API standpoint, not federation. But to me it’s all related so I used this as an opportunity to write about it.
#
[manton]
Aside from federation, there’s a separate trend now where every platform creates their own posting API. This seems like wasted effort to me.
#
[0x3b0b]
Hmm. If you address a thing to one person (target audience, I guess), but you deliberately make the thing public, are people besides the person to whom it is addressed part of its audience or not?
#
[0x3b0b]
I guess that's semantics, not -dev. It just caught my attention.
#
[manton]
I think if you post something publicly to your blog, everyone is the audience. 🙂
#
[snarfed]
"open letter"
#
[manton]
Posting APIs that attempt to be standards not tied to a single platform: Micropub, AP C2S, MetaWeblog, AtomPub (!), AT Protocol XRPC. Posting APIs that more client apps probably use: Mastodon, WordPress REST (?), Ghost, Tumblr. Just way too fragmented.
#
[pfefferle]
Sure, but we could make a difference! For http://Micro.blog and WordPress, there is a MicroPub endpoint(!) time to have some nice clients to „convince“ others that it is a good idea!
#
[KevinMarks]
is it time to revive silopub?
#
[KevinMarks]
that does tumblr and blogger
#
[manton]
[pfefferle] Definitely. I’d love to push Micropub more.
#
[KevinMarks]
and now we can't post to twitter that's one less to worry about
#
[pfefferle]
The issue there is that the audience and the app ecosystem is not yet big enough there I think
#
[manton]
I also think when Threads starts federating, people are going to ask: why can’t I use other apps with Threads? That’s a Meta problem, but related.
#
[manton]
[KevinMarks] Sigh. Silver lining with Twitter, I guess. 😞
#
[snarfed]
we can post to twitter, we just can't read from it, at least not for free
#
[pfefferle]
You mean X? :face_with_peeking_eye:
#
[snarfed]
[KevinMarks] just fyi Bridgy now does Micropub: https://brid.gy/about#micropub
#
[KevinMarks]
I thought the limits meant a relay app wouldn't work. Is the new limit per user, not per app?
#
sknebel
[manton]: question then, what can the standards learn from the "non-standard" APIs that seem more successful?
#
[snarfed]
ahh yes I think the free tier only lets you post as yourself, not oauthed as other users
gRegorLove_ joined the channel
#
[pfefferle]
[sknebel] I don‘t think it is about standard or proprietary… it’s about reach and success of the platform
tei_1 joined the channel
#
[pfefferle]
If mastodon wasn‘t so successful no one would have cared about their API
#
[KevinMarks]
their API is vaguely twitter-alike isn't it?
#
[pfefferle]
And I think bluesky is also wrong about that someone cares about the spec… it’s not the better spec wins…
#
[manton]
[sknebel] I agree with [pfefferle], it’s mostly because Mastodon is so popular, and it _only_ supports posting with its own API. Client apps have no choice.
#
[manton]
A better approach is to start with an existing standard for the basics, then layer in other things if needed. Micropub probably can’t do everything Mastodon needs, but it’s extendable.
#
[manton]
I would love to see Mastodon clients support both the Mastodon API _and_ Micropub (or even AP C2S). Not sure how to get there.
#
[pfefferle]
And to do so we should make MicroPub attractive to App implementers through reach and simplicity.
#
[snarfed]
of all the fediverse's pain points right now, the client side API arguably isn't really one of them
#
[snarfed]
at least to them
#
[manton]
Yep, it’s only a pain point for someone like me because my customers want to use Ivory with http://Micro.blog. So then I need to implement the Mastodon API, which I’ve been dragging my feet on for reasons.
#
[KevinMarks]
which is where interop testing is helpful, as there are a lot of mastodon clients and they're likely bug-compatible rather than tested
#
[manton]
And I’d argue the same for WordPress too. Why can’t Ivory post to WordPress? Seems like a reasonable thing to ask for, even if not all features are supported.
#
sknebel
its going to be interesting how the Mastodon API case evolves, now that it is used by more projects which also have features Mastodon doesnt
jonnybarnes joined the channel
#
[tantek]
[manton] re: "would love to see Mastodon clients support both the Mastodon API _and_ Micropub (or even AP C2S). Not sure how to get there." <-- since your most recent blog post ends with "The most popular Mastodon client apps do not support either ActivityPub or Micropub." that's an excellent setup for a "Next step for ActivityPub Part 2" where you could make a pitch for why Mastodon client apps should add support for Micropub, using its test
#
[tantek]
suite, etc."
#
c​apjamesg
What is a map!
#
c​apjamesg
*?
#
[manton]
[tantek] Yes, I’d like to write more about this.
#
[tantek]
in short: there are hundreds (thousands?) of servers (WordPress, http://micro.blog, etc.) that support the Micropub server API, and every Mastodon client would immediately have access to "crosspost" to any of those in addition to a user's Mastodon instance
#
[tantek]
I think that's the short version of the pitch that can provide enough user-centric value for Mastodon clients to add support. No need to leave your Mastodon client to post both on Mastodon and on your blog.
#
[tantek]
If/when enough Mastodon clients support Micropub, then eventually that will be enough for other AP server software (Pleroma, Misskey etc.) to perhaps invest more time to add Micropub support themselves instead of having to play catch-up with the Mastodon client API
#
[manton]
Yeah. Some client needs to jump in and be first. I’ve even thought of adding something myself to an existing Mastodon client that’s open source and seeing where it goes. Not enough time.
#
[tantek]
[manton] indeed. I suggest Elk (a fairly new Mastodon client) might be a good opportunity to file an issue for Micropub support with some reasoning and your intent to help
tei_1 joined the channel
#
voxpelli
Would be neat to create a Micropub to Mastodon service, where you expose your Mastodon account over Micropub
#
voxpelli
Likewise with Microsub
#
voxpelli
Then clients could start implementing those instead of needing to rely on a non-standard API like Mastodons
#
voxpelli
The opposite would be neat as well, exposing Micropub and Microsub over the Mastodon API
#
voxpelli
Funnily came to discuss this on Mastodon and jumped in here to see you discussing the same: https://mastodon.social/@voxpelli/110776308517900528
#
Loqi
[preview] [Pelle Wessman] @maffeis #ActivityPub is for federation whereas #micropub and #microsub are for interacting with your instance, so they are not really exclusive though.Micropub is already supported by tools like micro.blog, @ia Writer and such.Not sure if anyone has...
[benatwork] joined the channel
#
[fluffy]
People do have a tendency to conflate the roles of the various protocols yeah. What a lot of people think is “ActivityPub” is really Mastodon API.
#
[fluffy]
This conversation reminds me that I also really need to write a Micropub component for Publ. Every time I want to post something from my phone and end up needing ssh and vi to do it I get a little more annoyed.
#
[manton]
Aeeiii. That doesn’t sound fun. 🙂
#
[manton]
@voxpelli Yeah, either of those kind of bridges would be interesting… Maybe Micropub/Microsub → Mastodon would be most useful for moving the ball forward for Micropub clients. Not sure.
#
voxpelli
@[manton]: maybe I can find some time, hmm
#
[tantek]
[manton] LMK if you want to help nudge Elk toward Micropub and I'm happy to collaborate on that
tei_1 joined the channel
#
[manton]
[tantek] Thanks. I need to play with Elk a little, I haven’t really used it. I’ve mostly been testing native iOS apps (Ivory, Ice Cubes, Mammoth).
#
[KevinMarks]
I like phanpy.social
#
[Murray]
I need to check out Phanpy, any specific feature worth knowing about?
tei_ and sebbu2 joined the channel
#
aaronpk
TIL OwnYourSwarm uses 4500 API credits per day and my current API credit balance is 513,000
#
aaronpk
"We'll gift you $200 worth of credits on the 1st of every month. Once you use those, you'll need to purchase more below."
#
aaronpk
and apparently the credit does roll over?? my balance is $601
Soni joined the channel