Modalità di lettura

Looking in the peertube_prod db

Bonjour !

Thanks for this great application.

Inspecting with psql the peertube_prod db instance, I noticed the number of channels (~1300) and videos (~42K) is huge and does not equal to the numbers of local channels (~8) and local videos (~5300).
I guess it’s because of the Federation enabled in the instance (https://video.triplea.fr). Due to administration small time and policy of avoiding to mix curated contents with complotist videos, Federation was disabled. Is is possible and safe to clean manually the un-local channels and videos in the postgresql tables?

Even if the Federation feature is disabled, I had a lot to clean in /admin/overview/comments/list (curiously positive and worthless, seeming like slop). Curious to have local comments to admin for videos that are not.

2 messages - 1 participant(e)

Lire le sujet en entier

  •  

I can't subscribe to some channels

Hello!
I’ve been using PeerTube for quite a while now and haven’t had any major issues so far.
Now I’m facing a problem that I can’t quite explain myself.
I can’t subscribe to some channels on other instances.

For example, when I search for the following channels on my own instance:
heise_ct_videos@ peertube. heise. de
hakendran_videos@ peertube. heise. de
ct_uplink_videos@ peertube. heise. de
ct_3003@peertube. heise. de
medienecho@ digitalcourage. video
I can find it and click “Subscribe”.
The website itself tells me that I’ll now be notified when new videos are posted.
Everything seems normal.

But when I reload the PeerTube page, I can click “Subscribe” again.
So it didn’t save the subscription.

When I search the PeerTube log on the server for information, I don’t find anything unusual.
After searching for the channel, the log shows that the current video information is being retrieved.
As soon as I click Subscribe, the log only shows that it appears to have worked so far.
But apparently, it didn’t.

I’ve tried this several times on different days.
I’ve also tried it with the latest versions of PeerTube to rule out a bug in the software.

May 30 10:52:35 VM-PeerTube peertube[489]: [``peertube.hoerli.net:443``] 2026-05-30 10:52:35.299 info: Processing ActivityPub follow in job 79.
May 30 10:52:35 VM-PeerTube peertube[489]: [``peertube.hoerli.net:443``] 2026-05-30 10:52:35.321 info: Creating job to send follow request to heise_ct_videos - Videos von heise online .
May 30 10:52:35 VM-PeerTube peertube[489]: [``peertube.hoerli.net:443``] 2026-05-30 10:52:35.324 info: Processing ActivityPub unicast in job 9951.
May 30 10:52:35 VM-PeerTube peertube[489]: [``peertube.hoerli.net:443``] 2026-05-30 10:52:35.417 info: Updating 1 good actor follows and 0 bad actor follows scores in cache. {
May 30 10:52:35 VM-PeerTube peertube[489]: « badInboxes »:
May 30 10:52:35 VM-PeerTube peertube[489]: }

Where could the problem be?
Other channels on other platforms work without any issues.

2 messages - 1 participant(e)

Lire le sujet en entier

  •  

NixOS 26.05 ‘Yarara’ Released with Systemd Initrd by Default and Major Infrastructure Updates

NixOS 26.05 ‘Yarara’ Released with Systemd Initrd by Default and Major Infrastructure Updates

The NixOS project has officially released NixOS 26.05, codenamed “Yarara,” continuing the distribution’s unique approach to Linux system management through declarative configuration, atomic upgrades, and reproducible deployments. The release introduces several important platform-level changes, modernized infrastructure components, and continued refinement of the Nix ecosystem.

As one of the most distinctive Linux distributions available today, NixOS continues attracting developers, DevOps engineers, and advanced Linux users who value predictable system behavior and highly reproducible environments.

What Makes NixOS Different?

Unlike traditional Linux distributions that install packages directly into shared system locations, NixOS is built around the Nix package manager, which stores software in isolated, versioned paths and generates complete system configurations declaratively.

This architecture provides several advantages:

  • Atomic system upgrades
  • Reliable rollback capabilities
  • Reproducible environments
  • Easier infrastructure automation
  • Reduced dependency conflicts

These features have helped NixOS gain popularity among developers managing complex systems and cloud infrastructure.

Systemd-Based Initrd Becomes the Default

One of the most significant changes in NixOS 26.05 is the move to a systemd-based Stage 1 initrd by default. The older scripted implementation is now deprecated and scheduled for removal in NixOS 26.11.

The initrd (initial RAM disk) is responsible for preparing the system during early boot before the main operating system loads.

According to the release notes:

  • Systemd now handles Stage 1 initialization by default
  • The previous scripted implementation remains temporarily available
  • Users can still revert using boot.initrd.systemd.enable = false
  • Long-term migration toward the systemd-based approach is encouraged

This change is expected to improve consistency and simplify maintenance across modern NixOS deployments.

Continuing the Twice-Yearly Release Cycle

NixOS continues its established release cadence of publishing stable versions twice per year—typically around May and November. The 26.05 “Yarara” release follows the previous 25.11 “Xantusia” release and continues the project's steady development rhythm.

The 26.05 development cycle involved extensive staging, package testing, and release management work coordinated through the NixOS community.

Large-Scale Package and Infrastructure Updates

Like previous NixOS releases, 26.05 includes a massive collection of package updates across the software ecosystem.

  •  

GNOME 51 Development Officially Begins as ‘A Coruña’ Cycle Gets Underway

GNOME 51 Development Officially Begins as ‘A Coruña’ Cycle Gets Underway

The GNOME Project has officially opened the development cycle for GNOME 51, the next major release of one of Linux’s most widely used desktop environments. Following the recent launch of GNOME 50 “Tokyo,” developers are already shifting focus toward the next chapter of the desktop’s evolution, which will carry the codename “A Coruña.”

While it’s still very early in the process, the release schedule is now taking shape, giving Linux users and developers an early look at what to expect over the coming months.

GNOME 51 “A Coruña” Is Now in Development

The new release is named A Coruña, after the Spanish city that will host GUADEC 2026, the annual GNOME Users and Developers European Conference. The event serves as one of the most important gatherings for GNOME contributors, where future desktop plans, technologies, and development priorities are discussed.

As soon as GNOME 50 was finalized, development work for GNOME 51 officially began, continuing GNOME’s well-established six-month release cadence.

Release Schedule Already Published

The GNOME team has outlined the preliminary roadmap for the GNOME 51 cycle.

Current milestone dates include:

  • GNOME 51 Alpha: June 27, 2026
  • GNOME 51 Beta: August 1, 2026
  • GNOME 51 Release Candidate (RC): August 29, 2026
  • GNOME 51 Final Release: September 16, 2026

These milestones provide time for:

  • Feature integration
  • Public testing
  • Bug fixing
  • Performance optimization
  • Final stabilization before release

As always, dates may shift slightly depending on development progress.

Still Too Early for Major Feature Announcements

Because the development cycle has only just started, GNOME developers have not yet revealed a finalized feature list. Most major design discussions and merge requests are still in their early stages.

However, several areas are already attracting attention.

Wayland Improvements Are Likely a Major Focus

One of the biggest transitions in recent GNOME history happened with GNOME 50, which completed the project’s move away from X11 by removing remaining X.Org support from the desktop environment.

Because GNOME is now fully committed to Wayland, many observers expect GNOME 51 to focus heavily on:

  •  
❌