got a public url for red dwarf social app red-dwarf-social-app.whey.party so far i only got feeds and post thread to use the red dwarf direct pds + microcosm queries, and everything else is still standard unchanged social-app. i havent touched profile pages yet code is at github.com/rimar1337/so...

オスプレイ (osprey) は、使っているライブラリの名前から来てるようだ github.com/bluesky-soci...

tried porting the new react query based red dwarf fetching logic into social-app. its really slow and if i dont wait for the profile data itll crash from Maximum update depth exceeded

Forumtest development is paused because i developed ESAV for it and then realized it wasnt a good fit for a variety of reasons and then Spacedust released and i saw its potential but i did other projects with it instead so yeah forumtest is still on the table but i got distracted

Since people ask every so often: constellation's index occupies 270GiB on disk right now It has all links from all atproto records in the the last 221 days, so we're at +1.2 GiB/day needed on average to maintain it. Cassiopeia's SSD has 1TiB so we're good for a while ✨

wrote a thread about an idea i had mas.to/@Whey/115155...

okay i tried something 6789.whey.party constellation instance running on my laptop (would die soon) but it is using a jetstream instance url that isnt actually jetstream but it is actually a backfill server that implement the jetstream return shape and its growing in backfill size reallly quickly

okay so im trying something, so this is a custom feed that hydrates its own content, without relying on any appview to display it. for every new post that appears in the feed, it tracks its interactions to provide an independent and (best effort) hydrated getFeed and getPostThread apis

i am future me and i think i got it, red dwarf now caches almost everything into persistent memory (idk if thats a bad thing or not) and now can store your scroll position across page reload tangled.sh/@whey.party/...

new update to red dwarf, using the site should feel a lot faster now i migrated away from my custom cached fetch to tanstack react query and the results are great imo. also it now uses microcosm slingshot (pds edge cache) to reduce individual pds query load slingshot.microcosm.blue

just updated the #deadlock feed again after a long long while, it now includes posts talking about the new heroes. i dont play enough deadlock to know any other specific game or community terms to add to the regex though sorry

sorry it took this long and i still havent made the code any better the initial open source release of red dwarf is here tangled.sh/@whey.party/... it includes a readme that explains a bit about the project and how it works and its limitations

skylite View server now can show notifs (though slightly wrong and not timestamped) which is powered by spacedust

Excited to share some new stuff I've been I've been working on. It's an appview for building appviews called Slices. A slice reads your lexicons, indexes your records from the Jetstream, does backfill and provides a typescript client to interact with your lexicon .listRecords, .searchRecords, etc

gave Bounce a try on a fresh test acc @testhello.whey.party and i ran into some issues. bridging from fedi to bsky didnt seem to work. its still beta though, so im not too worried, itll probably smooth out over time

Today, we're launching the first Beta of Bounce, a tool that lets you migrate your social graph across protocols! We got such a positive response from our announcement, and we're so excited for folks to try it out. Here's what you need to know when you Bounce: blog.anew.social/bounce-beta-...

Actually how are custom feeds supposed to work with OAuth scopes? Are you supposed to have a billion seperate getFeedSkeleton scopes for each feed server? Does that mean asking for new scopes each time you open a new feed?

yknow i realized forumtest could be a great place for skylite discussion, except that its still barebones and kinda sucks. a discord server would probably make more sense, but eh idk well anyways i made a public docs site to gather my thoughts and write things down skylitedocs.whey.party

i realized that the index and view servers share some code but diverge in behavior. so right now i made it so if it can be handled by the index server, then it goes there, and everything else goes to view server. but maybe it should just be two servers with separate ports tangled.sh/@whey.party/...

What if the AppView was split into many pieces that are easier to self host? What if users can host independent indexes for cheap? And what if we can collect many self hosted indexes, and then layer our own choices for moderation and other contextual data on top?

this is the wrong website for it but i may as well post about it here too. i ported the misskey frontend to work on mastodon instances

trying to do red dwarf on the server side, and its feels really slow, even worse than red dwarf because everything needs to be fetched first before it can be sent to the app currently testing it from my laptop on did:web:local3768forumtest.whey.party with custom-appview.deer-social.pages.dev

dear bluesky dot app can you please get rid of the hardcoded bsky-aligned behavior on the PDS some day thanks

hello this is a cry for help im hosting both ForumTest (the SPA) and my PDS on subdomains of whey.party and i cannot login to the forum with accounts hosted on my own PDS this seems to be intentional so theres not much that i can do github.com/bluesky-soci...

finally ported ForumTest to use ESAV Live no new forum features yet tho forumtest.whey.party/f/@forumtest...

is it the fastest way to translate DID <-> handle? no but it's mine

got a new thing again, this time ESAV is Live (synced) statusphere.whey.party

tried to make use of the ESAV thing by making a forum test forumtest.whey.party

tried doing something today esav.whey.party/xrpc/com.exa...

Maaaaybe there's more to follow-removal than I thought. ATProto "zones of sovereignty" are maybe something. Streamplace has one for chat: your messages are `place.stream.chat.message` records on your PDS, but that's not YOUR chat, that's the STREAMER's chat. So the streamer can remove your messages.

It’s here! Germ DM is now an #ATProto messenger. Read our full announcement now.

just pushed a hack to fresh feeds that should eventually fix stale following lists over time, like give it a day or two for it to correct itself. still in the middle of refactoring everything, so this is all i can do for now. thanks for using fresh feeds

this was originally just meant to display the raw JSON, cuz getting that alone was already pretty annoying, but i somehow ended up building a RDF table renderer too oops

took too long getting an activitypub web explorer working. i had to make an actor (@[email protected]) just to fetch things because a lot of instances require signed headers. at least i was able to reuse signing logic from my atpub project activitypub-explorer.pages.dev?url=https%3A...

i think more feeds need to have a basic system that filters out posts you have definitely seen before. its a chore to scroll down all the posts you have seen before just to get to the unseen ones

Created "For You" feed which works like this: - we find all posts you liked - then we find other people who liked the same posts - then we find what else they liked to create the "for you" feed The aim of this algorithm is to be simple and transparent. bsky.app/profile/spac... Feedback welcome.

this is another cool approach to an independent bsky app experience, which uses only a generic network service (constellation) instead of a bsky-specific appview

got feeds to load, uhh and also i already feel really bad about directly querying the PDS for each post's text content and so i really dont want to fetch images or videos directly from them too so right now im just using the bsky cdn instead reddwarf.whey.party

i like that by using the new components i get working post interactions for free. also new url --> reddwarf.whey.party

managed to do a basic port of the universal post component from Testfront. most of the time went into converting custom css atoms to tailwind, and now i need to shim more data into the expected bsky api types especially for the embeds

yes, unfortunately the user information we receive when requesting the bluesky custom feed is not enough to ask bluesky for the personalized version of the sources. We have some ways to work around this, but it is currently a bunch of fragile work we are tabling.

cleaned up the styling a bit reddwarftest-1278.pages.dev

tried to do something here idk reddwarftest-1278.pages.dev

cool yay

appviewappviewappview - after 6 months, I'm running what is, afaik, the first full-network bluesky appview - you can use it at zeppelin.social, query it at bsky.zeppelin.social, read about it at whtwnd.com/futur.blue/3..., & help me keep it up for more than a few weeks at github.com/sponsors/fut...

Would there be any value in (partially) recreating the nostr model in atproto via queryable archival relays + appview-like (user scoped) processing on the client

how useful is it really to share your following feed to others? instagram lets you do it for reels and it should be relatively easy to do it here on bsky using custom feeds right?

Fresh feeds is back up, srry for the downtime. The disk filled up again and broke everything so im disabling likes tracking until the next release of Rinds