Notices by grindhold (grindhold@23.social)

@silverpill @Profpatsch @sabrinkmann

i think vendor prefixes is a fad too specific. how about type-specific prefixes like e.g. "proposal:foobar". if you give single vendors the possibility to mess with the standard it'll end with everybody cooking up their own soup. and maaaybe if you're lucky, one of them becoming the de-facto standard, totally bypassing what AP wants to achieve: a common protocol for all to agree on.

@silverpill @Profpatsch @sabrinkmann
so people, if they develop extensions to AP would at least be forced to think about how to integrate their stuff into the existing AP-ontology. at least thinking about where they need a new type, what fields it needs .e.t.c.

i mean, we did the vendor-prefix thing with flohmarkt. because i saw no other way and i found it ugly from the start :D (and i hadn't had the idea to pack a non-Note-object into an attachment yet)

@silverpill @sabrinkmann @Profpatsch in this particular case you are right. in the general case, as the fediverse is a decentral system, it might occur, that developer group A creates APObjectTypeA with a field named "foo" that does a specific thing. developer group B will create APObjectTypeB with a field named "foo" that does another thing. these object types will not be composable. as only one meaning of "foo" can exist simultaneously in a specific object.

@silverpill @sabrinkmann @Profpatsch

the biggest problem with the duck typing approach imo is, that there might occur situations in which different definitions exist for the same field.

e.g. we had this situation where content was defined as a Proposal as string, whereas in Note it was common to have a mapping from lang-code to a string in the according language as content.

In this case we could figure it out but there might be more complicated cases and not every type might end up mixable

@silverpill @sabrinkmann @Profpatsch when the fediverse and the FEP-database gets bigger the need to check for these conflicts will rise quadratically. So you either:
- need to include type-definitions for fields with specific names
- use ap-object-types
or
- end up with incompatibilities and accept that as a fact which leads to bloaty (and potentially slow) unmarshalling logic on the implementation side.

@silverpill @sabrinkmann i am okay with the value being a string representing a float or a decimal. i just want to know that this intentional and we are all on the same page.
maybe we should define whether this is a float or a decimal.

@silverpill @sabrinkmann
as we're talking about real-world values tied to commerce i deem decimal more fit for the purpose

@silverpill @midzer @Profpatsch @nlnet

it is an outspoken and official point in our agenda, however, we will most likely only be able to adopt proposals and intents, not agreements.

🥂 i can happily announce that the #flohmarkt project has been selected for being supported by @nlnet !

@midzer @Profpatsch and myself will program a lot in the next few months and we hope to bring you everything we teasered in my talk at #fediday in berlin :)

PSA to flohmarkt admins: I know that some of you roll out master to systems with users. This is generally a bad idea and will be a much worse idea in the next few months. You have been warned 🙃

#flohmarkt 0.6.0 has been published 🎉 https://codeberg.org/flohmarkt/flohmarkt/releases/tag/0.6.0

@linos @MastodonEngineering @dansup @pfefferle @helge @mkljczk @laurin objects and their types respectively have a N:1-relation. which scenario would require it to be a N:M relation? is this a "the fields of my object fulfill the interfaces of more than one type"-thing?
is this mentioned anywhere in the specs?

every single cent the EU seizes from bigtech in penalties should be redirected to fund @NGIZero

anyone with me?

in case you haven't heard yet: EU is planning wild budget cuts in the area of open source funding in their HORIZON program. This directly affects NGI big time.

dear @EUCommission , please continue funding NGI . If you don't there will be less and less tech and people left that are willing to develop and run europe's vision of a free and democratic internet.

#flohmarkt is growing:

- today we celebrate flohmarkt's arrival in the #yunohost app store thanks to @me for doing all the integration work
- we have a new contributor @blackoverflow who has started working towards automated tests and has already improved code quality greatly
- flohmarkt has a new feature that nudges you via email when you have new messages on your items, so you don't have to lurk on the platform all the time.

towards 0.1 we go.

you find flohmarkt on https://codeberg.org/flohmarkt/flohmarkt

ein vielerseits erwartetes feature ist gelandet: in #flohmarkt könnt ihr jetzt itemnamen, preise und die beschreibungen ändern. die änderungen werden föderiert und all eure interessenten werden automatisch über die änderung benachrichtigt.

https://codeberg.org/flohmarkt/flohmarkt

P.S.: news zum activitypub #flohmarkt funkt ab sofort @grindhold