Home | Notifications | New Note | Local | Federated | Search | Logout
Note Detail
Reply to @sabrinkmann@hachyderm.io
Samuel Brinkmann@sabrinkmann@hachyderm.io (2026-06-02 04:15:16)
The software is built with @fedify and uses Nuxt for the server and server-side rendering. This is my first bigger Fedify project, so I'm looking for improvements and best practices.
The Fediverse data structure is built on top of: https://codeberg.org/fediverse/fep/src/branch/main/fep/0837/fep-0837.md.
From the data point of view, this includes the proposal and resourceConformsTo field, which links to an URI. Like: https://mensa.mahlzeitheute.de/users/fl-ca1/menu-items/currywurst-currysosse-und-pommes.
Behind this is a JSON LD with a description of the food. As someone who is gluten intolerant, the allergen information is quite relevant and interesting. I'm not sure if this is the best way, and I'm interested what others would do. [2/4]
---Reply---
Samuel Brinkmann@sabrinkmann@hachyderm.io (2026-06-02 04:15:16)
Technically, this use case of daily changing meals is really interesting for the Fediverse because it is not static, most restaurant menus. One weird thing for me is that the Marketplace software that aggregates all meals wants to have the information as soon as it is available. For normal eaters who are just following the menu shop on an other service, this information is mostly useful for that day. Otherwise, I will just get all new dishes on Monday morning (or some other time of the week). This problem is a little bit similar with events.
I wonder if there is good solutions for that? Or is it just the price we pay for living in a Mastodon centric fediverse? [3/4]
Reply
---Replies---
Samuel Brinkmann@sabrinkmann@hachyderm.io (2026-06-02 04:15:17)
For small businesses, the Fediverse can be so interesting. Nowadays, a lot of small (food) businesses only have an Instagram page. The menu and other data is part of images and really badly structured. Especially information about allergens are often missing. In the fediverse, you can have this really nice looking view of your data and still provide your data to marketplaces, which aggregate all food information.
All of this is currently only a side project, and I hope we get some funding for the main project, currently called #economiverse: https://codeberg.org/54GradSoftware/economiverse.
I think marketplaces can be really interesting for the Fediverse. But I also learned in this project that the Fediverse is a lot of work, even with a good framework. In this software there are still missing pieces like editing or deleting dishes. Uploading pictures for profiles, and so on.
If you have any feedback, feel free to send it here or create an issue in the Codeberg Repo: https://codeberg.org/54GradSoftware/menuverse [4/4]