Yeah. Itβs necessary for a project weβre working on.
Thought about untyped collectionsβ¦great if just for us, but less so for other consumers of the structured records.
@yesthatwes
Recovering tech exec. Brooklyn NYC Baking things, building indie tech, and capturing street photos. Working on a new way to web because... π Any system that requires dependence cannot ultimately produce independence.
Yeah. Itβs necessary for a project weβre working on.
Thought about untyped collectionsβ¦great if just for us, but less so for other consumers of the structured records.
Thatβs exactly what weβre exploring. Weβre working on a fascinating concept for the ecosystem.
Loving this feature more than I thought I would.
Frustrating indeed.
Have you tried creating a feed that curates the experience you're looking for?
Been seeing the same for some time; since ~mid-July. I have an open todo to look into this more.
Couldn't agree more. So much so that built a feed generator that addresses your point. Have a look at any of my pinned feeds and you'll see what you're describing in action.
DM or drop a comment and I'd be happy to create a test feed for you.
"Less like this" takes time because the system must first learn what "this" means to the individual. But a feed based on your follows that excludes [US] politics is totally doable.
I need to be better at catching up with my DC feed. I almost missed this one; happy I didn't. Thanks for sharing.
I appreciate your opinion.
Iβll also share that I was indeed able to trust that your post was *not* meant to intentionally encourage such.
Trying hard to read this as if it's *not* encouraging people to blindly subscribe to something. Tech or otherwise, such conditioning is exactly what we *donβt* want to encourage these days.
Bingo! It's like yeah, we get it. Internet tech is evolving; decentralized probably makes sense right about now.
...And that looks like what exactly; in practice? What are those practical desired outcomes we're all going to benefit from when everything's decentralized??
damn! but, right?!
HTTP enabled the World Wide Web -> web. AT Protocol enables apps like Bluesky, [x]sky, etc. Calling that layer "Sky" seems fitting somehow. Connects nicely with all things "cloud" too.
Indeed. 'Free to leave' is a step toward data independence.
We can (and should often) grab our data repositories from Bluesky proper. Owning them from the start without the storage unit contract is the dream.
Thoughtful piece. Made me think about the friction between decentralization in theory and data sovereignty in practice. Keys living in someone elseβs domain isn't true dominion. Real ownership means having "you" from the start, though the freedom to grab your data at will is a good start.
Is Russiaβs stance really about attacking education by rejecting globalized educational systems? Or is it more nuanced; perhaps a rejection of the *idea* that 'international' education, as such, is framed through Western defaults, with all other perspectives filtered through that scaffolding?
A vintage Japanese boro jacket displayed on a dress form, shown from the front. The garment is pieced together with large panels of faded indigo and muted plum fabric, stitched vertically and horizontally. Areas of wear and repair are visible, with fraying edges and hand-sewn reinforcement, giving the jacket a patchwork, weathered look.
The back of a vintage Japanese boro jacket displayed on a dress form. The indigo-dyed cotton is patched with layers of fabric in varied shades of blue, from deep navy to faded sky tones, with visible stitching and frayed edges. The patchwork forms a rough grid of stripes, plaids, and solids, showing extensive wear and repair.
A vintage Japanese boro jacket displayed on a worn dress form. The indigo-dyed cotton garment is heavily patched and quilted with layers of fabric in varying shades of deep blue, teal, and faded navy. Frayed edges and visible stitching highlight the garmentβs age and history of repair.
The back of a vintage Japanese boro jacket displayed on a dress form. Large panels of faded indigo and muted rose fabric are stitched together in a patchwork pattern. The cloth shows wear, visible hand stitching, and areas of fraying, emphasizing the garmentβs age and history of repair.
Sorting through a few photos from a recent project shoot. Thought it would be neat to work with Lomo Metropolis film loaded in the LC-A. I like the results a lot. The character of the vintage Japanese boro really came through. Def gonna do more studio project work with the LC-A.
Indeed. Tech lays the foundation; people shape the outcomes. I've wondered if the transactional IFTTT approach is a solid foundation to deliver engaging feeds.
Curious if an IFTTT-style approach could actually lead to more intentional feed outcomes. From what Iβve seen, making feeds contextual and engaging is 1 part tech, 3 parts craft.
Oh Ooni. Why do you do this to me?
I like the versatility and compact size of this new Ooni Volt 2 but unlike the original (and great!) Volt 12, this one's indoor use only.
If you're considering this or any countertop Neapolitan pizza oven, absolutely do yourself a favor and grab a Biscotto stone!
Such a wonderful post. Made me smile! Thanks for sharing.
... @atproto.com, @rude1.blacksky.team, and a bunch of other people building in this space. Many will never understand how impactful and necessary the work here is, and that's ok. But I know. And My Jam! and a few other feeds I have cooking were not possible before now, and I am so proud of us all.
I've been building social tech for a minute and I've long wanted to power feeds via people and context, anchor them on voices that usually fall into the background, and let the *tech* be silent so we can sit back and enjoy the results. And you know what? Now we can thanks in part to the work of...
Just saw your post in the Yes Chef feed. Can't wait to give your chicken soup recipe a go as the weather cools. Thank you!
Advice to team Bluesky: Nuance matters here in both enforcement *and* framing. "Community Guidelines" reads cushy, but in reality you're establishing *House Rules*. Yes, we are guests in your house. Frame the "guidelines" that way and any pushback will be about the rules not about feeling sidelined.
Yeah, they owe you one. Checked out their menu; will be there very soon.
The tech piece has already been solved. The remaining challenges are ecosystem dogma and solution discovery. These should sort themselves out as the ecosystem matures.
This is a great foundational move for the AT Protocol ecosystem. DNS went through a similar handoff back in the 90s, shifting stewardship from a basement project to ICANN. If AT Protocol really takes off, the PLC directory could play a similar role as trusted protocol infrastructure.
Case in point: My ATProto Expo feed presents posts around all things AT Protocol and *nothing more*. The beauty here is that the feed stays broad in that specific context because its signals are people and their ATProto-adjacent posts, not hashtags or keywords that let noise slip through.
β¦because most feeds chase hashtags and keywords while the real signal comes from people and context. Trying to wrestle away the noise is a constant mess and not worth the effort. My take is that sparse, follow-graph-powered feeds that reflect what you want to see are a better way forward.