#Smithereen 0.11 is out
Uncategorized
14
Posts
3
Posters
124
Views
-
@julian do you mean fetching the `replies` collections to make threads as complete as possible? I've been doing that for a long time already :D
Never seen those FEPs, will take a look
-
@julian do you mean fetching the `replies` collections to make threads as complete as possible? I've been doing that for a long time already :D
Never seen those FEPs, will take a look
grishka@mastodon.social this would be in addition to replies collection fetching 🙂
You'd poll one endpoints to get all of the replies in the tree. Mastodon will support serving this collection soon!
-
@julian do you mean fetching the `replies` collections to make threads as complete as possible? I've been doing that for a long time already :D
Never seen those FEPs, will take a look
-
evan@cosocial.ca I think it's time to start drafting a SWICG report on backfill approaches hmm
-
@evan @julian yeah, that makes sense. Though implementing FEP-f228 as specified would be complicated for me because I don't store AP objects as-is — I treat ActivityPub like an API, so to return chronologically ordered replies mixed with likes, I would have to make database queries that would get very inefficient very fast (something like SELECT ... FROM wall_posts ... UNION SELECT ... FROM likes ... ORDER BY time ASC LIMIT x OFFSET y).
-
@evan @julian yeah, that makes sense. Though implementing FEP-f228 as specified would be complicated for me because I don't store AP objects as-is — I treat ActivityPub like an API, so to return chronologically ordered replies mixed with likes, I would have to make database queries that would get very inefficient very fast (something like SELECT ... FROM wall_posts ... UNION SELECT ... FROM likes ... ORDER BY time ASC LIMIT x OFFSET y).
grishka@mastodon.social most implementations just return the object IDs. Sending the entire activity stream is more difficult, although some do do it (e.g. silverpill@mitra.social's Mitra)
So "collection of posts".
-
@evan @julian yeah, that makes sense. Though implementing FEP-f228 as specified would be complicated for me because I don't store AP objects as-is — I treat ActivityPub like an API, so to return chronologically ordered replies mixed with likes, I would have to make database queries that would get very inefficient very fast (something like SELECT ... FROM wall_posts ... UNION SELECT ... FROM likes ... ORDER BY time ASC LIMIT x OFFSET y).
@evan @julian I solve the problem of running into deleted replies by never fully deleting replies that have replies, instead clearing most of the data. So, for such a reply, I return a Tombstone that still allows the traversal of the thread.
I agree that this is still not optimal though. Running into a reply from a server that no longer operates would still break things. And you still have to make tons of requests (although Java's virtual threads make that reasonably fast).
-
@julian @silverpill that I can do fairly trivially
-
@julian @silverpill that I can do fairly trivially
grishka@mastodon.social yes, you and I don't store all ActivityPub objects, and neither does Mastodon. That's why attempting to serve activities is a non-starter.
Mastodon will serve the object IDs.
Lemmy (not released yet) and Piefed (v1.2) also implement this collection, so having another implementor be able to use them would be great.
-
grishka@mastodon.social yes, you and I don't store all ActivityPub objects, and neither does Mastodon. That's why attempting to serve activities is a non-starter.
Mastodon will serve the object IDs.
Lemmy (not released yet) and Piefed (v1.2) also implement this collection, so having another implementor be able to use them would be great.
@julian I have this convention where I return IDs for remote objects (obviously, how else would you authenticate them if not by fetching from the origin servers) but complete objects that are local, to save resources. IIRC I saw Mastodon do it for replies so just copied this behavior
-
@julian I have this convention where I return IDs for remote objects (obviously, how else would you authenticate them if not by fetching from the origin servers) but complete objects that are local, to save resources. IIRC I saw Mastodon do it for replies so just copied this behavior
grishka@mastodon.social that's a really interesting question, and I put those thoughts in a new topic :)
-
@julian doooooo iiiiiiit
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
Brown line under glass
-
@ulquiro @leobm @toxi @korkeala @jack @woo @ahab @richardazia @postmarketOS @Fairphone @made wow a phone with partial support for phone calls
-
@garretpolk which game
-
Sunset Kodak DC120 (~1MP, 1996) #SooC #ShittyCameraChallenge
-
figured out the composition and characters mostly! now i can draw it all once more in a cleaner comp later...
-
Print-in-Place Gripper Does It With a Single Motor
[XYZAiden]’s concept for a flexible robotic gripper might be a few years old, but if anything it’s even more accessible now than when he first prototyped it. It uses only a single motor and requires no complex mechanical assembly, and nowadays 3D printing with flexible filament has only gotten easier and more reliable.
The four-armed gripper you see here prints as a single piece, and is cable-driven with a single metal-geared servo powering the assembly. Each arm has a nylon string threaded through it so when the servo turns, it pulls each string which in turn makes each arm curl inward, closing the grip. Because of the way the gripper is made, releasing only requires relaxing the cables; an arm’s natural state is to fall open.
The main downside is that the servo and cables are working at a mechanical disadvantage, so the grip won’t be particularly strong. But for lightweight, irregular objects, this could be a feature rather than a bug.
The biggest advantage is that it’s extremely low-cost, and simple to both build and use. If one has access to a 3D printer and can make a servo rotate, raiding a junk bin could probably yield everything else.
DIY robotic gripper designs come in all sorts of variations. For example, this “jamming” bean-bag style gripper does an amazing, high-strength job of latching onto irregular objects without squashing them in the process. And here’s one built around grippy measuring tape, capable of surprising dexterity.
-
3 February 1916 | Italian Jew, Alberto Cassin, was born in Busca.
He was deported to #Auschwitz from Fossoli on 22 February 1944.
He did not survive.
---🎧 Listen about the development of the mass murder infrastructure at Auschwitz: https://www.auschwitz.org/en/education/e-learning/podcast/transformation-of-auschwitz-concentration-camp-/
-
@aeva final form capitalism
i'm imagining some kind of voltron spaceballs robomaid thing here
