There are tons of different feed aggregators in addition to newspipe:
nextcloud news, tiny-tiny rss, freshrss, miniflux, newsblur, inoreader
etc.

Each aggregator maintain its own API, so this is a nightmare for client
developpers, as it is needed to implement, and maintain, all the APIs
for all the different aggregators.

There is a draft called microsub [1], that aims to standardize the
communications between clients and aggregators. It is still a draft,
but there are already clients and servers implementing it. Plus, people
behind microsub do call for feedbacks, so there is room for discussion
if there are missing things in the API to fit newspipe needs.

Hi.
First of all thank you for your work on newspipe. Being a simple rss
aggregator written in python+flask is pretty exactly what I was looking
for.

One feature I miss though is the ability to authenticate with an OpenID
Connect server.

Would you accept such a contribution?

There are libs out there like authlib [1] that makes it really to deal
with the redirections dance, and to validate and decypher the JWTs. In
the end the main work would be to dynamically create new users, and
update old users profile when they authenticate.

Latest OpenSMTPD version correctly handle the tilde character [1]. Here is a
patch of a working piece of configuration. This follows an old
discussion [2].

Éloi

 [1] https://github.com/OpenSMTPD/OpenSMTPD/issues/1026
 [2] https://lists.sr.ht/~sircmpwn/sr.ht-discuss/%3C369e6e3efa0f66b79ff0049fd7c11acdcb9631fd.camel%40aquilenet.fr%3E

---
 lists.sr.ht/configuration.md | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/lists.sr.ht/configuration.md b/lists.sr.ht/configuration.md
[message trimmed]

For the record, reinstalling sourcehut on a UTF-8 db solved the issue.
Thank you

It seems you are right:

   $ sudo -u postgres psql
   psql (13.4)
   Type "help" for help.
   
   postgres=# SHOW client_encoding;
    client_encoding
   -----------------
    UTF8
   (1 row)
   
   postgres=# SHOW server_encoding;
    server_encoding

Le mardi 14 septembre 2021 à 14:36 +0700, Ngô Ngọc Đức Huy a écrit :
> Hi, I make commits with my name (having accents) without any problem.
> 
> Is this commit done on sr.ht or your own instance?  This looks like the
> SQL server was configured to use the ascii codec instead of one
> supporting Unicode characters, such as utf-8.

This is done with my own instance, with the Alpine packages. Thank you for
sharing this, since that means the problem is on my side. I will look at
postgresql encoding then.

I encounter a similar error with lists.sr.ht if I send an email with accents
either in the subject or the message.

https://paste.sr.ht/~azmeuk/5b3a95d797964b81aa81d97bc7e4a7728dda5d6f

Hi. When the author commit name contains an accent (like "Éloi
Rivard"), pushing the commit generates this traceback [1] in
man.sr.ht.log. Removing the accent solves the issue.

  [1]
https://paste.sr.ht/~azmeuk/ea77ff9bf95c68420a4b519ade15ffa3ac798323

For the record, it seems the issue what due to the missing /dev/shm in
my Alpine lxc container. I could solve this with

    sudo rc-update add devfs boot

> Any logs from the api service? I think they should be in
> /var/log/meta.sr.ht-api.log

meta.sr.ht-api.log seems ok, but there seems to be issues with celery

meta.sr.ht-api.log

   2021/05/25 10:37:31 Running on :5100
   2021/05/25 10:37:31 Prometheus listening on :35551
   2021/05/25 10:37:33 "GET http://localhost:5100/query/api-meta.json
   HTTP/1.1" from 127.0.0.1:51856 - 200 66B in 854.554µs
   2021/05/25 10:37:37 "GET http://localhost:5100/query/api-meta.json
   HTTP/1.1" from 127.0.0.1:51892 - 200 66B in 58.445µs
   2021/05/25 10:37:42 "GET http://localhost:5100/query/api-meta.json