I've been saying this
Uncategorized
30
Posts
9
Posters
0
Views
-
@alexia Actually @gabboman is already in the Matrix chat, so I think we've got wafrn covered! I was thinking moreso about projects like Sharkey and Akkoma, where I don't believe I know anyone except in very distant passing. Plus, drafting RFC-style documentation isn't everyone's deal.
My stance on participation in the FEP at this stage has been “not public yet, but open door,” so anyone who would like to contribute (or has strong opinions) is welcome. 🙂
@julian @alexia @gabboman hey @julia (Sharkey maintainer) and @FloatingGhost (maintainer of Akkoma) are either of you interested in participating in drafting a Comment Controls FEP or have any points that should be kept in mind specific to either of your projects?
-
@julian @alexia @gabboman hey @julia (Sharkey maintainer) and @FloatingGhost (maintainer of Akkoma) are either of you interested in participating in drafting a Comment Controls FEP or have any points that should be kept in mind specific to either of your projects?
@liaizon@social.wake.st @FloatingGhost@ihatebeinga.live @julian@fietkau.social @alexia@app.wafrn.net @gabboman@gabboman.xyz there isn't really need for a specific comment controls FEP? The GoToSocial interactionpolicy already provides this, albeit without the stamp system of the quote authorization FEP. is that what you're suggesting?
Wouldn't be opposed to such a feature on the fediverse, though Sharkey wouldn't be in a great place to be a first implementer of it- we're behind on things as is. -
@liaizon@social.wake.st @FloatingGhost@ihatebeinga.live @julian@fietkau.social @alexia@app.wafrn.net @gabboman@gabboman.xyz there isn't really need for a specific comment controls FEP? The GoToSocial interactionpolicy already provides this, albeit without the stamp system of the quote authorization FEP. is that what you're suggesting?
Wouldn't be opposed to such a feature on the fediverse, though Sharkey wouldn't be in a great place to be a first implementer of it- we're behind on things as is.@julia The goal for this FEP is to generalize the GTS approach. Their docs leave a few TBDs and underspec interactions with features that GTS does not have, such as conversation backfilling and context management.
Basically I started with a copy & paste of the GTS document and have been toiling away at potholes. 🙂 (That's why I thought it would be a quick adventure, how naive I was.)
-
@liaizon@social.wake.st @FloatingGhost@ihatebeinga.live @julian@fietkau.social @alexia@app.wafrn.net @gabboman@gabboman.xyz there isn't really need for a specific comment controls FEP? The GoToSocial interactionpolicy already provides this, albeit without the stamp system of the quote authorization FEP. is that what you're suggesting?
Wouldn't be opposed to such a feature on the fediverse, though Sharkey wouldn't be in a great place to be a first implementer of it- we're behind on things as is.We needed to extend a feature: “yo ask the op of the thread instead of me for permission to reply”
Reason:
i make a post marked as “only people I follow”
Then person2 replies in “only people I (person2) follow”
Now, “Mr replyguy who is followed by person2” joins the chat and honors his name
-
We needed to extend a feature: “yo ask the op of the thread instead of me for permission to reply”
Reason:
i make a post marked as “only people I follow”
Then person2 replies in “only people I (person2) follow”
Now, “Mr replyguy who is followed by person2” joins the chat and honors his name
"Permission to reply" or "Reply not accepted"? Those are two different things. The former would be really nice, but I don't think is likely. The latter is where are today, albeit with patchwork implementation, I think.
-
@julia @gabboman I would consider this part of context management. Reply interactability is one part, reply visibility is another famous one.
The current scope of the FEP is to make sure the door is open for FEP-7888 / FEP-11dd contexts, but we'll probably not fully spec it out, since GTS as the “reference implementation” can't provide it. May punt the details to a future FEP.
Gabbo wants to solve it quickly though, so who knows how this will go in practice. 😄
-
@julia @gabboman I would consider this part of context management. Reply interactability is one part, reply visibility is another famous one.
The current scope of the FEP is to make sure the door is open for FEP-7888 / FEP-11dd contexts, but we'll probably not fully spec it out, since GTS as the “reference implementation” can't provide it. May punt the details to a future FEP.
Gabbo wants to solve it quickly though, so who knows how this will go in practice. 😄
Ill just copy what mastodon did with quotes as a “good version” and meanwhile (by meanwhile I mean “mastodon doesn’t do it” ill use the collection replies. Probably
#I-actually-need-to-implement-that-too -
You can check our blog for the work we do. I try to share our efforts pretty regularly.
https://socialwebfoundation.org/blog/
Long-form text was one of our first projects. You can see our work on FEP-b2b8 and the conformance tests we did with producers and consumers.
Please lmk if you have other questions!
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
Brescia: per la destra è vietato criticare il questore. “l’obiettivo è criminalizzare il dissenso”
@anarchia
Per la destra non si può criticare l’operato di funzionari pubblici e forze di polizia. Lo hanno dichiarato, in maniera esplicita, le deputate bresciane Cristina Almici (di Fratelli d’Italia) e Simona Bordonali (della Lega) commentando la
-
-
@fucinafibonacci @ambiente molto interessante per le spiegazioni sulla complessità della rete e sui costi di gestione!
-
@ryan @tikaro depending on where you live², IKEA duvet cover¹ are an excellent source for fabric that is cheap, easy to work with, often has nice prints, is usually 100% cotton (or at most rayon / lyocell) and is actually usable for things that will get worn (mostly tops, or very lightweight bottoms) and/or used.
And speaking of cotton, one think that will make the difference in the way your clothing will look is pressing all seams as you sew them: you don't need a fancy iron, but an iron is necessary. And cotton and other natural fibers (plus rayon) will work with you under the iron, synthetics will work against you, and will cause you lots of suffering.
¹ other than the very cheapest ones, that tend to be quite lightweight and transparent, and the fancy ones, that are probably good for everything listed above, but not cheap.
² some countries apparently have shops with cheap cotton. I don't live on one of those :D
-
meloni vuole pagare sondaggisti perchè non dicano questo
-
@mos_8502 oh and another more modern choice you could make too, depending on application: disregard package management entirely and treat the entire OS as an immutable image that's built as an atomic unit, with updates being done by having a pair of A/B partitions. You boot off the current active partition, and to update the OS you write out the entire new image to the inactive and reboot onto it.
The Fedora Atomic distros do this, as do the Universal Blue ecosystem (they're essentially running the "new" atomic stack that future Fedora will use). CoreOS was arguably the OG at this for widely known distros, although this is how a large swatch of embedded linux operates, using either buildroot to generate images or Yocto (whose build system is a horrific crime, but it's also very powerful, can generate whole disk images _and also_ a stream of delta updates for efficient upgrading, and is widely supported by embedded linux hardware and software vendors so a lot of stuff ends up using it, even though I find it horrible every time I try touching it)
-
@mos_8502 if you're Ubuntu, you just start with Debian, and then make it worse.
That's also how I do it for the OS my employer ships on our robots. I start with Ubuntu and mostly make it worse, but also make it better by replacing snap packages with regular debs.
-
@mos_8502 The biggest pains, if you're not reusing someone else's package manager: how do you express dependencies between packages? Can you have optional deps like debian's "recommended" ? Can you have virtual packages that can be provided by multiple concrete packages (I don't have an example on tap but debian, arch, gentoo all support this for stuff like swapping out libc implementations or pulseaudio vs. pipewire), how do you version packages where the upstream might have an unhelpful or missing versioning scheme of its own, how do you handle the million different build systems that upstream uses, how fancy is your dependency resolution algorithm (can be anything from "unhelpfully useless" to "NP-hard and sometimes takes hours to compute a solution" - most useful distros land somewhere in the middle).
None of this _has_ to be hard, at every step you can make some simplifying assumptions/decisions that cut off some flexibility from your distro in exchange for a simpler system to build/use/maintain. There not being any "correct" answer is why there's a million distros with more showing up all the time.
