Email or username:

Password:

Forgot your password?
6 posts total
Helge

So Fediverse, I made a weird bot. It's @even@dev.bovine.social and @odd@dev.bovine.social. That's the same actor with two handles.

Now the bot posts a random number between 0 and 1000. If the number is even, bot updates its preferred username to even, when it's odd to odd. A version of the source code is here. I changed the crontab to post at the 12th minute of every hour.

silverpill

@helge Can it be followed? I didn't get an Accept

Helge

Good morning Fediverse. It's a gray day.

In case, you need reading material, I wrote FEP-1311: Media Attachments.

Note: Codeberg is down right now. It's not my fault by posting this link. It also was before.

Helge

Good morning Fediverse. It's storming and raining.

I just realized that I'm running out of time to start something on my todo list. The prototype fund has a funding round with deadline January 2nd, 2025.

An interesting infrastructure problem to tackle would be Fediverse media server. I'll leave the technical discussion aside.

Question:

- Are there German instance owner, that would be interested in helping test/run/develop such a solution?
- Would you be willing to help write a proposal?
- Would you be willing to set up an entity to help run a media server collective long term?

Good morning Fediverse. It's storming and raining.

I just realized that I'm running out of time to start something on my todo list. The prototype fund has a funding round with deadline January 2nd, 2025.

An interesting infrastructure problem to tackle would be Fediverse media server. I'll leave the technical discussion aside.

Helge

Good morning Fediverse. It's a sunny day with a blue sky.

I've finally finished a first version: Recommended Media Attachment Format. My recommended format includes more properties than any current Fediverse application provides.

There are still a lot of work items, e.g. where did akkoma go? Or to write a FEP explaining how these properties are useful. However, I think that if we start working towards using these examples as a model for how to implement media attachments than whatever we can find in ActivityPub, we will make the Fediverse a better place. It will be a long road to there.

Good morning Fediverse. It's a sunny day with a blue sky.

I've finally finished a first version: Recommended Media Attachment Format. My recommended format includes more properties than any current Fediverse application provides.

There are still a lot of work items, e.g. where did akkoma go? Or to write a FEP explaining how these properties are useful. However, I think that if we start working towards using these examples as a model for how to implement media attachments than whatever we can find...

Helge

Good morning Fediverse. The sky is gray and so are my thoughts.

Anyway, this post by @silverpill triggered me to look at media attachments in the Fediverse again 😭😭😭

This resulted in inputs#48 and a general state of despair. The situation could be nice. One could provide a recommendation on how to do media attachments. They could include stuff like the width and height of an image, that has been broken and reported in ActivityStreams for over 5 years. One could include a file size and digest, because one cares about bandwidth and integrity (ActivityStreams doesn't).

Instead one gets this and that. I'm not going to detail everything wrong about this. 🤷‍♂️ It would take more time than writing a proper specification document.

If you have opinions, in particular on the digest format and what to use to represent file size, please comment. A note on digest. digestMultibase seems like a footgun to me due to the inclusion of the length byte. Not sure if there is something better.

Good morning Fediverse. The sky is gray and so are my thoughts.

Anyway, this post by @silverpill triggered me to look at media attachments in the Fediverse again 😭😭😭

This resulted in inputs#48 and a general state of despair. The situation could be nice. One could provide a recommendation on how to do media attachments. They could include stuff like the width and height of an image, that has been broken and reported in ActivityStreams for over 5 years. One could include a file size and digest,...

silverpill

@helge An alternative to digestMultibase is digestSRI (mentioned in VC spec), but digestMultibase seems to be more popular among VCDI spec authors and unlike digestSRI, it is now in security context.

Regarding width, height, digest and others: perhaps these properties should be added to url? One image may have multiple representations, for example low res and high res. IIRC PeerTube provides videos in multiple variants and has a long array of links in url.

{
  "type": "Image",
  "url": [{
    "type": "Link",
    "href": "https://example.social/image.png"
    "height": 2000,
    "width": 2000,
    "digestMultibase": "zQm1"
  }, {
    "type": "Link",
    "href": "https://example.social/image_thumbnail.png",
    "height": 100,
    "width": 100,
    "rel": "https://example.social/ns/thumbnail",
    "digestMultibase": "zQm2",  <- different digest!
 }]
}

@helge An alternative to digestMultibase is digestSRI (mentioned in VC spec), but digestMultibase seems to be more popular among VCDI spec authors and unlike digestSRI, it is now in security context.

Regarding width, height, digest and others: perhaps these properties should be added to url? One image may have multiple representations, for example low res and high res. IIRC PeerTube provides videos in multiple variants and has a long array of links in url.

Helge

I wrote a new fediverse-idea: configurable following on how to improve the followers dynamic in the Fediverse.

The basic idea is: Users should have more control in how their content is shared. This idea gives more fine grained control related to the followers collection.

Go Up