[Discuss] Meet.jit.si limits meetings to 95 minutes

[abreauj at gmail.com (John Abreau)]

If we self-host a jitsi instance, it should be on sugarloaf, not driftwood.
After the InstallFest, we should arrange a time to deploy sugarloaf at the
Waltham colo site.



On Mon, Oct 19, 2026 at 12:51?PM Jerry Feldman <gaf.linux at gmail.com> wrote:

> We probably should host jitsi, but only for blu and natick FOSS meetings
> so we can determine if the bandwidth is ok.
>
> Jerry Feldman <gaf.linux at gmail.com>
> Boston Linux and Unix
> http://www.blu.org/
>
> On Oct 18, 2026 1:57 PM, John Abreau <abreauj at gmail.com> wrote:
>
> Hi Randall,
>
> Thanks for pointing that out. Edward Piecewicz mentioned it as well.
>
> Upon looking into it, I found that we can continue our meetings in a new
> session.
>
> At our recent BLU meeting, we tested a new mechanism I developed for
> reliably recording our Jitsi meetings. It records a Chromium tab and saves
> the output into .webm files in 10-second chunks, which I then assemble into
> a single file using ffmpeg after the meeting. The recording persists across
> a migration to a new Jitsi session, provided it stays in the same Chromium
> tab.
>
> To support this, I set up a cron job to generate random Jitsi session URLs.
> It runs on the third Wednesday of each month with the following schedule:
>
>   - 6:30 PM: Writes the primary blu.org meeting URL.
>   - 7:45 PM & 8:45 PM: Writes randomized meeting URLs.
>   - 9:45 PM: Displays a notice that there is no active BLU meeting.
>
> This setup prevents anyone from joining a new session early and thereby
> cutting short its expiration time.
>
> You can view the live result at https://blu.org/jitsi-id.
>
> For this week's meeting, we plan to switch to the new session at 8:00 PM,
> and if needed, switch again at 9:00 PM.
>
> Best regards,
> John Abreau
>
> On Sat, Oct 17, 2026 at 1:29?PM Randall Rose <rrose at pobox.com> wrote:
>
> > Jitsi announced that they have recently imposed a 95-minute limit to
> > meet.jit.si, which BLU has been using.  Apparently the new rule is that,
> > for any given meeting URL on meet.jit.si, sessions end after 95 minutes
> > and cannot be restarted until after a 24-hour cooloff period.
> > https://community.jitsi.org/t/changes-coming-to-meet-jit-si/142673
> >
> >
> https://community.jitsi.org/t/update-on-meeting-reusability-after-the-95m-limit/142722
> >
> >
> https://community.jitsi.org/t/update-on-meeting-reusability-after-the-95m-limit/142722/4
> >
> > Self-hosted Jitsi Meet (not on meet.jit.si) would be one way to avoid
> > this limit.
> > _______________________________________________
> > Discuss mailing list
> > Discuss at lists.blu.org
> > https://lists.blu.org/mailman/listinfo/discuss
> >
>
> --
> John Abreau / Executive Director, Boston Linux & Unix
> Email: abreauj at gmail.com / WWW http://www.abreau.net / PGP-Key-ID
> 0x920063C6
> PGP-Key-Fingerprint A5AD 6BE1 FEFE 8E4F 5C23  C2D0 E885 E17C 9200 63C6
> _______________________________________________
> Discuss mailing list
> Discuss at lists.blu.org
> https://lists.blu.org/mailman/listinfo/discuss
>
>
>

-- 
John Abreau / Executive Director, Boston Linux & Unix
Email: abreauj at gmail.com / WWW http://www.abreau.net / PGP-Key-ID 
0x920063C6
PGP-Key-Fingerprint A5AD 6BE1 FEFE 8E4F 5C23  C2D0 E885 E17C 9200 63C6