//
sign in
Profile
by @danabra.mov
Profile
by @dansshadow.bsky.social
Profile
by @jimpick.com
AviHandle
by @danabra.mov
AviHandle
by @dansshadow.bsky.social
AviHandle
by @katherine.computer
EventsList
by @katherine.computer
ProfileHeader
by @dansshadow.bsky.social
ProfileHeader
by @danabra.mov
ProfileMedia
by @danabra.mov
ProfilePlays
by @danabra.mov
ProfilePosts
by @danabra.mov
ProfilePosts
by @dansshadow.bsky.social
ProfileReplies
by @danabra.mov
Record
by @atsui.org
Skircle
by @danabra.mov
StreamPlacePlaylist
by @katherine.computer
+ new component
Profile
Loading...
I strive to make great things that people can use and enjoy, all to the glory of God. Links & Bio Page: https://zicklag.dev GitHub: https://github.com/zicklag Making @roomy.space
Zicklag






Loading...
My favorite is totally deleting things, but I do believe both are crucial to being a good software engineer.
I love this breakdown. We can simplify by ignoring details that would distract from the system we are trying to design ( like APIs do ). Or we can simplify by totally deleting the pieces of the solution that are unnecessary to produce the desired behavior!
It feels like maybe there's an entire content discovery layer here waiting to be figured out. Or maybe this is just a non-moderation use-case for labelers. We need a blogosphere labeler for standard.site publications.
We can't distinguish it by lexicon alone in this case. And it's sort of always that case with, for example, spam. But this is not spam per se, it's just a different category of content that has the same semantic "shape", represented by the same lexicon.