Just to add to this, Friendica is known to have issues with being an unkind citizen of the web before (this time for RSS):
> Friendica, various versions. 100% unconditional requests. Occasionally shows up < 10s after the previous poll. Not good.
Just to add to this, Friendica is known to have issues with being an unkind citizen of the web before (this time for RSS):
> Friendica, various versions. 100% unconditional requests. Occasionally shows up < 10s after the previous poll. Not good.
Can someone with more #JavaScript experience tell me what's an idiomatic way of solving the problem of an application that must fetch multiple URLs?
I currently have the issue that a lot of those URLs actually are the same, so I end-up with 40 requests for the same resource.
Is there an elegant way to solve this with minimal overhead over the native fetch API?
@silverpill I added a ticket here: https://todo.sr.ht/~mariusor/go-activitypub/296
I will need to create a test-case for it, but I think I have all I need.
@silverpill which works for maybe 1% of people that create content professionally. How are we to dar say that the fediverse needs to accessible to everyone if we put crypto-currency obstacles in front of people.
In my humble opinion, any monetization option that only deals with cryptocurrency is useless in making the fediverse a valid alternative to whale content creators that might want to migrate from traditional social media.
@benpate see if you can come up with some sort of activtiypub vocabulary based on this idea: https://floss.fund/funding-manifest/
I'm sure more of the fediverse creator would be interested in having some monetization capabilities.
@benpate are there any useful things built on top of them, or are they just crypto currency adjacent? Regular artists, I bet, would prefer to be paid in actual currency, not make belief money.
I've finally got off my ass and created a Codeberg account in order to submit my first PR to the #FEP repository.
I'm not very familiar with the FEP submission etiquette so any pointers from more experienced people would be helpful.
The PR: https://codeberg.org/fediverse/fep/pulls/452
Mailing list thread for feedback: https://lists.sr.ht/~mariusor/go-activitypub-discuss/%3Cwecobrezdaeqzfsukst42hncuuimomii5oeixonirrksrvs4md@4l76dr4obisi%3E
@catileptic wouldn't offering options to the users be a better compromise than full "removal".
I feel like users are still capable, or at least should be capable, of agency in deciding what's better for them, even if the final result is consuming more garbage.
@sinituulia I use a light therapy lamp for when I need super bright lighting during evenings.
@silverpill @benpate in fairness there's already a schema.org document for music releases:
https://schema.org/MusicRelease
Bandcamp uses them on album pages.
@dmitri the way I understood what
@silverpill is saying is that if those are part of the same server ... they're not "auxiliary".
@silverpill care to elaborate?
What is wrong with those things existing as auxiliary services?
@gvlx I don't mean to talk for @silverpill but the post is about a library under AGPL, not his service built on top of it.
You probably clicked on the wrong link.
@BeAware I know, I know... I have two or three issues that they have been ignoring for over three years. :)
@BeAware in fairness I don't think I advertised the feature anywhere where the Mastodon devs might have looked.
I didn't create a FEP for it sadly.
@BeAware I have not gone over the details, but to the best of my knowledge Authorized Fetch is just the name Mastodon uses for a similar mechanism to what I'm doing in FedBOX. In their case I think they don't allow any C2S get request on collections if they're not authorized, in mine I just filter out non Public activities/objects.
But, I'm pretty sure that my work on having the collections filtered based on recipients predates Mastodon's by quite some time. :P
I often struggle with working on non-trivial, long standing projects because when I sit down to do the work after some hiatus, I can't seem to find the pain points I wanted to fix quickly enough.
It feels like trying to get a bandaid off when you can't find an edge where it comes unstuck easily enough.
The largest piece of bandaid that I wasn't able to get unstuck from the ActivityPub adjacent work is getting the HTTP-signatures working well with the rest of the fediverse (by which I mean Mastodon).
Today I might have got the corner of another little bit of bandaid unstuck which hopefully will help in the long run.
@multiverseofbadness that's burn out talking
@BeAware federating between instances should have nothing to do with it.
Dan is presenting a feature where a user views another profile and then they can see mutuals. This can be done if Mastodon would load *all* the information (including follower list) about the profile when you view it from your own instance, instead of relying only on data that has been previously federated.
It's a *trivial* feature that Mastodon is lacking, and I feel like that's what the toot you quoted complains about.
@BeAware I think you misunderstand the problem. The ActivityPub specification encourages implementations to expose a followers/following collections on actors. Those collections have a TotalItems property in them which should allow anyone to see the count.
Here's an example.
Mostly a programmer.Implementing #ActivityPub in the #Go programming language.Current projects: * #GoActivityPub - a library to use ActivityPub in Go. * #FedBOX - a generic ActivityPub service supporting the client to server API. * #brutalinks - a link aggregator inspired by (old) reddit, hacker news and lobste.rs built on top of FedBOX. * #oni - a single user ActivityPub server with minimal fuss.My posts are mostly related to ActivityPub and web development.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.