Loading...
Det er tydeligvis noe italienske feriegreier som heter #ferragosto.
Dette minner meg om filmen som på norsk heter «Sommerlunsj i Roma» https://www.imdb.com/title/tt1277728/ og som jeg tror jeg så på #Tromsø internasjonale filmfestival ( #TIFF) i 2010.
What other types should we implement first?
taps mic hello!
Hello world
4 media
What other types should we implement first?
I’m extremely annoyed by Twitter restricting profiles from users who aren’t logged in. So many, many academics post updates regularly on Twitter 😭 I don’t want to create a new Twt account.
Ice Runner
Ice Runner è un simpatico gioco puzzle/platform con grafica pixelosa! Sacrificate cubetti di ghiaccio per raggiungere l'agognata bevanda!
LINK --> https://www.lealternative.net/2023/08/15/ice-runner/
@jor Ses arguments sont juste factuellement faux. C'est étrange pour un juriste...
L'extrême-droite est ce qu'elle prétend combattre et combat ce qu'elle prétend être
Des enquêteurs en Géorgie ont constaté que Trump avait accédé aux logiciels de machines de vote électronique. Je crois qu'il a prétendu que l'élection était truquée en faveur d'Hillary Clinton mais je suis sûre qu'il a dit qu'elle lui avait été volée lorsqu'il a...
Océane ⏚
no, we added filters and sorting option for feeds and threads.
At the top left of the page you can select the feed (my feed, local, remote, ...) on the top right you can choose how to sort posts (chronological, by amount of replies, by amount of boosts, ...) and filter by time (posts created in the last day, week, month, year, all time)
You probably are on "My Feed" - looking at posts created only in the last week (which is the default settings)
in next iterations we will make those defaults configurable in user preferences.
Are the old posts gone?
no, we added filters and sorting option for feeds and threads.
At the top left of the page you can select the feed (my feed, local, remote, ...) on the top right you can choose how to sort posts (chronological, by amount of replies, by amount of boosts, ...) and filter by time (posts created in the last day, week, month, year, all time)
You probably are on "My Feed" - looking at posts created only in the last week (which is the default settings)
In terms of future commitments: the largest thing we have identified as a blocker for launching additional community services (such as Lemmy or kbin, for example) is the lack of a single sign-on infrastructure for Treehouse.
We discussed SSO options for a while, such as LDAP/Kerberos and Keycloak.
We concluded that there was not really any pre-existing solution that was developed on a stack that we felt confident maintaining (for example: we are not going to deploy Active Directory because we do not have the resources to manage a Windows machine, and Keycloak is a giant pile of barely-maintained Java), so we are considering writing our own light-weight OIDC/SAML single sign-on solution.
Although there is interest in deploying a Lemmy or kbin instance for discussion boards, this will roll out before we deploy a Lemmy or kbin instance. This also allows Lemmy and kbin to mature a little more before we pick and deploy one of them.
The other key thing we need to work on is setting up external monitoring of the infrastructure, so people can understand when infrastructure is down, and possibly why it's down, etc.
In terms of future commitments: the largest thing we have identified as a blocker for launching additional community services (such as Lemmy or kbin, for example) is the lack of a single sign-on infrastructure for Treehouse.
We discussed SSO options for a while, such as LDAP/Kerberos and Keycloak.
We concluded that there was not really any pre-existing solution that was developed on a stack that we felt confident maintaining (for example: we are not going to deploy Active Directory because we do not have the resources to manage a Windows machine, and Keycloak is a giant pile of barely-maintained Java), so we are considering writing our own light-weight OIDC/SAML single sign-on solution.
Although there is interest in deploying a Lemmy or kbin instance for discussion boards, this will roll out before we deploy a Lemmy or kbin instance. This also allows Lemmy and kbin to mature a little more before we pick and deploy one of them.
The other infrastructure issue is e-mail deliverability. Originally, Treehouse used my own personal e-mail infrastructure, which had excellent IP reputation and good deliverability.
Earlier this year I decided to decommission that infrastructure, and Treehouse now acquires its e-mail infrastructure from MXroute. Due to the providers that MXroute uses for its own infrastructure, we have had less than stellar e-mail deliverability.
We are open to suggestions from the general public on how to proceed with solving the e-mail problem.
What is not going well?
In a short word: Infrastructure.
Basically, Treehouse's community services have come about through experiments.
As a result of this, the infrastructure is entangled with my own personal infrastructure, although it is becoming less entangled over time due to the adoption of OpenStack on the hosts: Treehouse infrastructure now has its own dedicated kubernetes cluster, but further isolation work needs to be done before access can be given to more of our volunteers.
At present, the plan is to abstract most of these problems away with service accounts and IaC. Once the infrastructure is fully detangled, more "break glass" access will be given as needed to trusted volunteers.
The other problem is that we use kubernetes, and specifically the knative framework on top of kubernetes, with a custom traefik ingress setup. This setup is not particularly well-supported by upstream knative, although I am working on plans to upstream that work into knative directly, which should help a lot.
We were going to consider switching to Nomad, but Hashicorp decided to change the license, so we're probably not going to do that now.
What is not going well?
In a short word: Infrastructure.
Basically, Treehouse's community services have come about through experiments.
As a result of this, the infrastructure is entangled with my own personal infrastructure, although it is becoming less entangled over time due to the adoption of OpenStack on the hosts: Treehouse infrastructure now has its own dedicated kubernetes cluster, but further isolation work needs to be done before access can be given to more of our volunteers.
At present, the plan is to abstract most of these problems away with service accounts and IaC. Once the infrastructure is fully detangled, more "break glass" access will be given as needed to trusted volunteers.
The other problem is that we use kubernetes, and specifically the knative framework on top of kubernetes, with a custom traefik ingress setup. This setup is not particularly well-supported by upstream knative, although I am working on plans to upstream that work into knative directly, which should help a lot.
We were going to consider switching to Nomad, but Hashicorp decided to change the license, so we're probably not going to do that now.
