This is a warning about Meta and Threads.
Please boost this here and outside of Mastodon so that pregnant people in the United States are informed that using Meta/Threads is dangerous.
I'm unlikely to get pregnant but I have ZERO presence on Meta/Facebook/Instagram/Threads as a matter of principle.
@dym that's probably possible with a custom gateway or http server. one limitation I'm dealing with however is publicly run Ipfs gateways which have very simple logic so I think the most I could do is convince them to adopt some new mime types. ideally I would like to make it possible to resolve an identity from any gateway.
another approach that I have been thinking about is that we could focus less on web finger and more linking directly to the profiles page
@dym not sure. I would love that as an option though! The way mastodon and other fedi instances treat webfinger might vary accross the board. Hypothetically any username @staticpub.mauve.moe should resolve to the same thing
I just want to slide in here and comment: "The data" is terribly vague here. What you get from ActivityPub is at worst: the likes, the shares, the posts, the social graph.
What you don't get is data like: How long did this person spend looking at something? Or more pointedly said. There has been this screenshot of Threads app permissions circulating. Consuming the firehose from ActivityPub gives you lots of data, but still a lot less than you would get with all these permissions.
He he he 😈 I got my first statically published blog to load! Still need to work on the inbox server and get post resolving wired up but I'm happy with the progress so far. @mauve@staticpub.mauve.moe
This is also being published on #p2p protocols on ipns://staticpub.mauve.moe/about.jsonld
One limitation is you can only #webfigner one account per domain.
This is being published using #DistributedPress and is part of our upcoming #ActivityPub integration.
@glitchontwitch Yeah big mood. One hope I have is that the non-algorithmic nature of fedi stuff could lead to better RoI per user once there's enough users for that to be viable.
I totally agree that numbers and potential customers seeing your work is important for people to make their livelyhoods on social media.
@glitchontwitch I have a feeling Threads users aren't generally up to date on the state of federated software. From the looks of things the network effects of being able to bring your instagram follow graph with you outweighs any feature needs.
it's genuinely wild how we heard nothing but long winded platitudes on how innovative silicon valley was for like 20 straight years and it's all culminated in a bunch of the dullest, most petulant billionaires imaginable all just copying each other's version of a very basic chat app
@decentral1se kinda like hyperbeedeebee but with prolly trees and go :P https://github.com/RangerMauve/ipld-prolly-indexer/tree/initial
@orsinium Nice, thanks for the info. I'll add it to my TODO list. Thankfully in this case I just forgot to close a channel in a very stupid way. :P
A programmer is just a machine that turns #Golang code into deadlocks. :P
@thisismissem @renchap it's similar to how desktop gui apps can have separate "main threads" with all their logic and renderer threads that talk to the main thread to get data in and out.
More #JavaScript folks should consider using the SharedWorker API in their app. Especially if you have particularly heavy initializing code.
E.g. instead of Element loading everything from scratch each time you open it in a tab, it could have the bulk of the resources shared across tabs in a worker and have speedier inits that don't block the render thread.
https://developer.mozilla.org/en-US/docs/Web/API/SharedWorker
Occult Enby that's making local-first software with peer to peer protocols, mesh networks, and the web.
Exploring what a local-first cyberspace might look like in my spare time.