@cassidy@mastodon.blaede.family there was a presentation yesterday about LLMs and open source security that I really wanted to attend but I think it conflicted with @benpate@mastodon.social's talk.
I'll have to check out the recording though!
There was an earlier slide about "benefits", but here are Matt's list of drawbacks of being in a walled garden.
Add in enshittification and the list is complete.
Next up we've got @matt@writing.exchange, who'll be talking about WriteFreely and write.as!
Blogs have been around just as long as forums (although I think BBSes might beat us both).
@benpate@mastodon.social arguing that we're losing the plot with fediverse onboarding. We sign up, and then we dump them on the index page.
(He was looking for bagpipes, by the way.)
Vagrant Cascadian is on stage now after lunch, talking about hyper local networks and "Off-Grid Inter-Neighborhood Networks"
Much of it is well beyond my limited comprehension
EmojiReact vs. Like w/ content?
@silverpill@mitra.social lost signal only if the UX for both emoji reactions and likes are collapsed.
Otherwise, right signal for the right intent?
FEP-c0d0: Context Locking
@silverpill@mitra.social thanks for the early feedback:
Undo(Like) is the inverse of the Lock activity now
A prior art section has been added to address the conflict between this FEP and Lemmy's implementation
@skavish@welley.social definitely not, I think it's just a common sense approach to handling abandoned/unmanaged instances.
There were calls for this last year when spammers took advantage of abandoned servers with open registration and went absolutely nuts.
Does it rise to the level of an FEP? Maybe if combined with a couple other common sense approaches to forum admin got any other ideas?
@atomicpoet@atomicpoet.org@iftas@mastodon.iftas.org may have some additional thoughts.
@benpate@mastodon.social says "There's the outside of the sausage and the inside of the sausage. We need to make the outside look nice. You don't want to see what's inside"
A pretty apt metaphor, actually.
FEP-c0d0: Context Locking
Thanks for sharing that! I did not know that the Lock activity could be applied to children, although it makes sense logically.
This FEP only deals with topic/context-level locking, so Lemmy and Piefed's implementation would go further than this. It's definitely worth mentioning within as well.
FWIW both Lemmy and Piefed have the concept of contexts, it's just not exposed in the UI. It's pretty trivial to support this FEP with little to no new logic.
<p>Anyone have suggestions on a good music player on android for mp3 files?</p> <p>I have decent (if proprietary) options for podcasts and streaming music, but I have some mp3s that I'd like to listen to as well.</p> <p>I've tried VLC, and it's kind of meh. I'd like to be able to jump back 5-10 seconds at the press of a button if possible. Bonus points if it integrates with notification tray and android auto ...</p>
Music player (mp3s) for Android
Anyone have suggestions on a good music player on android for mp3 files?
I have decent (if proprietary) options for podcasts and streaming music, but I have some mp3s that I'd like to listen to as well.
I've tried VLC, and it's kind of meh. I'd like to be able to jump back 5-10 seconds at the press of a button if possible. Bonus points if it integrates with notification tray and android auto ...
<p>Hm... <a href="https://w3id.org/fep/c0e0" rel="nofollow ugc">FEP-c0e0: Emoji reactions</a> details two ways to federate an Emoji reaction:</p> <ol> <li><code>EmojiReact</code> activity</li> <li><code>Like</code> with <code>content</code> (as opposed to a regular <code>Like</code>, which has no content)</li> </ol> <p>In testing, I noticed that misskey (or at least, the site I was testing with, <code>birb.space</code>) sends the latter. I don't know what sends the former, and if NodeBB were to start federating out <code>EmojiReact</code>, would it be broadly understood?</p> <p>Perhaps I should federate out both at once.</p> <p>cc <a href="https://mitra.social/users/silverpill">@<bdi>silverpill@mitra.social</bdi></a></p>
EmojiReact vs. Like w/ content?
Hm... FEP-c0e0: Emoji reactions details two ways to federate an Emoji reaction:
EmojiReact activity
Like with content (as opposed to a regular Like, which has no content)
In testing, I noticed that misskey (or at least, the site I was testing with, birb.space) sends the latter. I don't know what sends the former, and if NodeBB were to start federating out EmojiReact, would it be broadly understood?
Perhaps I should federate out both at once.
cc @silverpill@mitra.social
<p>This is the main discussion thread for the draft FEP-c0d0: Context Locking</p> <h2>Summary</h2> <p>Context locking (and its inverse, unlocking) refer to the action whereby a topic no longer accepts new replies.</p> <p>This proposal introduces a <code>locked</code> property on the context object, and a new activity type, <code>Lock</code>, to signal changes to a topic's locked state across the fediverse. Unlocking is expressed with the standard ActivityStreams <a href="https://www.w3.org/TR/activitystreams-core/#activity-undo" rel="nofollow ugc"><code>Undo</code> activity</a>, applied to the original <code>Lock</code>. [...]</p>
FEP-c0d0: Context Locking
This is the main discussion thread for the draft FEP-c0d0: Context Locking
Summary
Context locking (and its inverse, unlocking) refer to the action whereby a topic no longer accepts new replies.
This proposal introduces a locked property on the context object, and a new activity type, Lock, to signal changes to a topic's locked state across the fediverse. Unlocking is expressed with the standard ActivityStreams Undo activity, applied to the original Lock. It builds on FEP 1b12: Group federation for audience identification (the audience property) and the Announce wrapping pattern, and on FEP fe34: Origin-based security model for authorization.
This FEP is a sibling of FEP f15d: Context Relocation and Removal, which covers the Move and Remove moderation actions.
The full FEP text can be found at https://w3id.org/fep/c0d0
FEP-c0d0: Context Locking
I don't see much in 171b re: access/reply controls.
That said 171b also is an opinionated departure from 1b12 so might be we'd want access controls split off from 171b perhaps, so they can be shared?
cc @julian@fietkau.social
MicroSD card on carrier pigeon 
got any other ideas?
and :+1: into a like?