DJ2LS

Another question is then the implementation of custom filters. How could this achieved? If the pointer to the filter on init would be used everywhere internally, this part could be...

> @DJ2LS - I've just pushed a feature that dumps the OFDM config using the new `freedv_ofdm_print_info` function: > > ``` > ./src/freedv_data_raw_tx --bursts 3 --testframes 3 custom /dev/zero -...

@DJ2LS I got the tx bpf working.

@frspin how should the "get by callsign" api endpoint act? We can add an endpoint, which is getting all messages, filtered by a callsign, but the question is then, how...

I would suggest something like this: /freedata/messages/{call} or what about adding a filter, like `/freedata/messages?byCall={callsign}` `/freedata/messages?byCall={callsign}&direction={to/from}` `/freedata/messages?byID={message-id}` This would simplify the endpoints.

No filter for direction would fetch all directions Von meinem iPhone gesendetAm 22.05.2024 um 16:51 schrieb frspin ***@***.***>: Il 22/05/24 16:06, DJ2LS ha scritto: > I would suggest something like...

We are just trying to publish a new release. So we can add this one to the next release I think. Von meinem iPhone gesendetAm 22.05.2024 um 17:15 schrieb frspin...

I'm working on this in "dev-filter-messages" Possible filters: ``` filters = { 'id': request.args.get('id', default=None, type=str), 'callsign': request.args.get('callsign', default=None, type=str), 'origin_callsign': request.args.get('origin_callsign', default=None, type=str), 'via_callsign': request.args.get('via_callsign', default=None, type=str), 'destination_callsign': request.args.get('destination_callsign',...

``` def freedata_message_db_change(self, message_id=None): self.broadcast({"message-db": "changed", "message_id": message_id}) ``` has been updated as well, the change event contains now the corresponding message id

retransmit message now with: `PATCH: /freedata/messages/{id}/retransmit ` set message as read: `PATCH: /freedata/messages/{id} --> payload: "is_read: True"` where the last one is a endpoint for modifying every message content