Untitled attachment

Notices where this attachment appears

1. Embed this notice
   dansup (dansup@mastodon.social)'s status on Wednesday, 12-Nov-2025 00:15:00 JST dansup

   For the Loops For You algorithm to work properly, we need data.

   It's tricky when it comes to remote video posts because we can't properly track the metrics we use in the algo.

   This is why I'm considering limiting the For You feed to videos from Loops only (local or remote), while allowing you to see non-loops videos in your Following feed.

   Wdyt? Feedback greatly appreciated ❤️

   #loops #askFedi #loopsDev

2. Embed this notice
   Weekend Editor (weekend_editor@mathstodon.xyz)'s status on Friday, 31-Oct-2025 20:52:12 JST Weekend Editor

   in reply to

   @cstross

   I once saw something almost exactly like this.

   It was at Symbolics (lisp machines) back in the 80s. We had a machine configured to be a file server, and another to be a namespace server. ("Namespace" was what we called the equivalent of DNS in the lisp machine world, probably before DNS existed or at least before it became popular.)

   Somebody put the namespace server's data files on the file server, because hey, it's for storing files, right?

   Things went swimmingly until there was a power cut.

   Then it was deduced that there was no feasible boot order:
   - The file server needed namespace service to figure out who it was.
   - The namespace server needed file service to get at the files containing its data.

   It was... "interesting".

3. Embed this notice
   🌈 BarbaPulpe 😇 ᴹᵃˢᵗᵒᵈᵒⁿ (barbapulpe@gayfr.social)'s status on Sunday, 26-Oct-2025 06:34:53 JST 🌈 BarbaPulpe 😇 ᴹᵃˢᵗᵒᵈᵒⁿ

   in reply to

   🇬🇧 Official launch of our LOOPS server!

   What is it? It's the latest app from the Fediverse for sharing short videos, similar to TikTok, but free, ethical, algorithm-free, and respectful of your personal data.

   It's brand new, from the developer of Pixelfed (thanks @dansup !) and I thought you might be interested in this new format, which is federated and connected to the rest of the Fediverse. Give it a try, there's no risk!

   Sign up for free at: https://videos.gayfr.social

   Follow me on Loops from here at: @barbapulpe@videos.gayfr.social

   Brand new and developing rapidly, there are still a few bugs but it works very well, and new features will be added regularly.

   The federation has just started, so interconnection with other servers will build up gradually. The more you interact with it, the faster it will go.

   Have fun!

   #gayfr #Loops #LoopsApp #LoopsVideo

4. Embed this notice
   YK Hong (ykhong@mas.to)'s status on Sunday, 10-Aug-2025 12:58:19 JST YK Hong

   Meta and Google, in league with
   period tracking app Flo, shared and violated Flo users’ data.

   It goes without saying, that not only is this illegal, but it breaches privacy, and puts people at profound risk.

   Google, Flo, and data analytics firm, Flurry, settled prior. Meta proceeded to trial, and a jury just concluded that they tapped in on and violated Flo users’ privacy globally.

   Not all apps are always trying to steal your data, but most of them do.
   And Big Tech always does.

5. Embed this notice
   Zenie (zenie@piaille.fr)'s status on Monday, 21-Jul-2025 12:58:26 JST Zenie

   @sacha

   I recently contributed a bunch of code to #Emacs #EMMS. As a result I was invited to join the development team which I'm excited to be a part of.

   My code was merged last week for version 23 of EMMS. There was a small breaking change.

   There is now an entire system for searching and filtering tracks. It's backwards compatible with the old browser filters, but very different and very powerful. It is interactive and all filters can be represented as data.

   It's super cool and very enjoyable to use.

   I wrote a post to give an overview to it on my shiny new website here.

   https://zeniesqis.statichost.eu/code/2025-07-14-the-emms-filter-system/

6. Embed this notice
   Ed Summers (edsu@social.coop)'s status on Saturday, 09-Nov-2024 02:04:20 JST Ed Summers

   I'm watching the anxiety level around .gov web resources grow after the election (for good reason) and am reminded of the #DataRefuge and #EDGI web monitoring work that started in 2016.

   In theory the End-Of-Term #WebArchiving project pulls in lots of resources that could be at risk. https://eotarchive.org/ But it can be challenging to verify and get a sense of how good coverage is, e.g. for GIS data.

   It feels like it could potentially be made easier?