did:w(h)e(y)b
@dw.whey.party
33 followers 22 following 290 posts
self indulgent thought landfill part of the did:web club in my RDF era performative: @whey.party whiny: https://mas.to/@whey
Posts Media Videos Starter Packs
dw.whey.party
Okay i think i finally get why i feel so strongly against this. App stores (and package repos) are mostly one way. Most users dont need an account to download. So why do you even need server to server federation and notification? All you need is a discovery to resolve the respective download server
dw.whey.party
probably is a cache issue. i restarted rinds and it works again. other feeds (particularly the ones based off the golang template (which is what rinds uses)) still doesnt work
dw.whey.party
> Message from server: Failed to get claims from auth header: Failed to parse authorization token: signature verification failed

and some generic 401s
screenshot of rinds feedgen 401-ing when my main fetches it
dw.whey.party
even my own Fresh feeds arent working at least i can debug this
dw.whey.party
just moved @whey.party to this same PDS im on (pds-nd.whey.party) and i feel like half of the personalized feeds dont work and i must assume it is because theyre still holding on to my cached identity or something?
dw.whey.party
love mkizka.github.io/pdsadmin-web/ makes pds administration one click instead of ssh-ing to my vps
pdsadmin-web
mkizka.github.io
dw.whey.party
i really really really really want a standardized community lexicon for declaring alternate representations. So like i can link a app.bsky.feed.post and a pub.leaflet.document or a pub.leaflet.comment or anything else really
dw.whey.party
more importantly "very bad performance" and "profile pages arent using microcosm yet" and "react update tree too deep"
dw.whey.party
i should get this on tangled so i can make an issue titled "solve the missing likes problem" and tag it with very-bad-first-issue
red-dwarf-social-app.whey.party
Bluesky
red-dwarf-social-app.whey.party
dw.whey.party
and more of the social part of federating than actually being a package repository that is meaningfully decentralized
dw.whey.party
so if they are putting software update content inside Note objects how the hell are the atproto side supposed to interop? its decidedly a lossy conversion i get that but bsky bridging means nothing and the fact that theyre doing this implies that it isnt a major issue / they are prioritizing tweets
dw.whey.party
more on this... so like the thing that i dont like about bridgy is that we havent seen any real bridging going on for non-twitter content from atproto, while literally anything from fedi that fits into a Note gets bridged as a tweet
Reposted by did:w(h)e(y)b
mackuba.eu
Lulz it broke on your own post 🙃🙃

I deployed some changes to my feedgen library, which added some extra validations, and apparently the regexp I wrote doesn't match the URI for did:webs 🫠
dw.whey.party
hahahahahah lmao sorry did:web users at it again
dw.whey.party
the weird part of this is red dwarf still uses the bsky cdn which means appview bans does not automatically mean a cdn ban lmao
rude1.blacksky.team
As you can see in this screenshot, not only are AJ Link's post and profile still available elsewhere, he is still posting (though seemingly less happily) freedom of speech unimpeded
This app Red Dwarf by @whey.party skips the bookstore and goes straight to the author. blacksky.community doesn't 5/11
avatar
Festive Łink. 🎅🏿 🎄 🎁 @spacelawshitpost.me
· 19h
A lot of people talking big shit now because they think I won’t see. Fucking cowards. Bootlicking losers.
0
0
1
avatar
Festive Łink. 🎅🏿 🎄 🎁 @spacelawshitpost.me
· 19h
It’s so weird being able to see people have whole discourses about me without being able to visibly respond. lol
0
0
3
avatar
Festive Łink. 🎅🏿 🎄 🎁 @spacelawshitpost.me
· 1d
Hi @jazzpomegranate.blacksky.app. Make everyone change their profile pics to Free Link.
Free Link Black Panther button like Free Huey.
1
0
1
dw.whey.party
fyi @mackuba.eu the atproto feed is down
dw.whey.party
and besides i do think something like a spec should be done in the community so we can actually collaborate and share ideas on what is needed how it should be implemented and etc etc i shouldnt be the singular person to decide what goes in the spec by being the sole developer of it
dw.whey.party
i guess this whole layered appview thing is why i want to build skylite but i have no energy to actually ship it man it because it really is two things
1. specification for a composable bsky appview
2. implementation of this composable bsky appview
either one is already hard enough doing both is aaa
dw.whey.party
functional vs technical independence i think is the deal here
technically youre fully independent but at what cost right when you dont need all that. same for the new blacksky appview i dont think you need that but i do respect the effort
dw.whey.party
and like the whole deal with atproto and bsky is composability so why dont you compose the appview so like layer microcosm with api.bsky.app so you get the best of both worlds you dont spam the PDS nor microcosm with requests and you get to see all the banned stuff
dw.whey.party
but also like i dont really actually believe in red dwarf i think it is much more reasonable to use a social-app fork that falls back to microcosm constellation rather than being completely independent with major downsides
dw.whey.party
i did this because tanstack router version of red dwarf was mentioned and like the social-app version of red dwarf is still wayy behind in terms of features and stability
whey.party
just added a few good first issues for red dwarf if you want to help tackle some of the lower hanging fruits
tangled.org/@whey.party/...
dw.whey.party
the boostrapping resolver should be done on the user's root node (whatever it may be) and the system should allow for patching a specific mapping in the tree without branching because branching makes auto updating the forked branch to follow main branch hard but maybe thats fine ?
dw.whey.party
okay but if you import OID to SID mappings by Opaque IDs then how do you resolve the SID of that OID? you resolve the resolver? ughhhhh
dw.whey.party
my current idea is to have mapping be node-scoped
but to allow for cascading updates, we need to allow to import specific triple mappings from a centralized definition
one node exports mappings
then a bunch imports from this one node
idk i havent thought this through all that much