pleroma - Link to source

Announcing: Frog Protocols for Wayland 🐸

Let's create Wayland Protocols but much more iterative.

Wayland Protocols has long had a problem with new protocols sitting for months, to years at a time for even basic functionality.

This is hugely problematic when some protocols implement very primitive and basic functionality such as frog-fifo-v1, which is needed for VSync to not cause GPU starvation under Wayland and also fix the dreaded application freezing when windows are occluded with FIFO/VSync enabled.

We need to get protocols into end-users hands quicker! The main reason many users are still using X11 is because of missing functionality that we can be shipping today, but is blocked for one reason or another.

Check out the repo here! github.com/misyltoad/frog-prot…

and the Mesa MR that adds support for frog-fifo-v1 to fix these issues and goes into much more detail: gitlab.freedesktop.org/mesa/me…

in reply to Neal Gompa (ニール・ゴンパ)

mastodon - Link to source

Neal Gompa (ニール・ゴンパ)

In practice, it does not seem to be as hard as it looks to get wide agreement, it's just much harder to get *universal* agreement. It often seems like the latter is necessary to get anything done, and that's something we need to put more effort into squashing.

There also seems to be a fear of "dead batteries", but I don't think that's something we should be concerning ourselves. Things tend to naturally work themselves out over time anyway.

in reply to Neal Gompa (ニール・ゴンパ)

mastodon - Link to source

Neal Gompa (ニール・ゴンパ)

Wayland, as used today, is already not functional without things that aren't in wayland-protocols. On the GNOME side, there's both private protocols and a mixture of private and public D-Bus interfaces. On the KDE side, they use private protocols and third-party protocols. Most other Wayland environments follow the KDE approach too. A lot of them are the same third-party protocols. That says to me we're not doing a good job of integrating things that are commonly needed.

gotosocial - Link to source

Hello everyone! We've just made the first release candidate for version 0.17.0 of GoToSocial :under_construction: Adventurous admins who want to try the new features and help us spotting bugs can get the release from below:

github.com/superseriousbusines…

⚠️ This release contains several database migrations which will run the first time you start up this new version. Be sure not to interrupt this migration process. This will take anywhere between a few seconds and an hour or even more (on slower hardware / big databases). Please be patient! Back up your database file before updating! We had to rejig the entire statuses table to introduce interaction policies (see below). ⚠️

Release highlights:

  • Interaction policies: This release gives you the ability to set interaction policies on your statuses using the settings panel. Interaction policies let you determine who can reply to, like, or boost your statuses. You can accept or reject interactions as you wish; accepted replies will be added to your replies collection, and unwanted replies will be dropped. This feature is still a work-in-progress as we will almost certainly have some kinks to work out in terms of implementation etc, but we wanted to get it into people's hands as quickly as possible.
    User docs here: docs.gotosocial.org/en/latest/…
    Federation docs here: docs.gotosocial.org/en/latest/…
  • Much wider range of support for different media types: In this release we've embedded a webassembly build of ffmpeg into the GoToSocial binary, so that users can post many different types of media than previously, including mp3, flac, and other audio types, and many more video types. Admins: you don't need to have ffmpeg installed on your server for this to work.
  • Audio player: to complement the new media types, we adapted our current video player to also play audio, so people visiting your profile can play MP3s and FLACs. Album art is supported when embedded in the audio file!
  • Header/avatar alt text: You can now set alt-text for your avatar + header images, so that screenreader users visiting your profile can read a description of your beautiful face.
  • Better threading model for statuses: On the web view of a thread, conversations are now indented at different levels, to make it easier to see who's replying to whom.
  • Prefers-reduced-motion is now supported, so that folks with animations turned off in their operating system or browser aren't confronted with lots of animation when they open your profile.
  • Conversations view: You can now view a list of your direct message conversations, making it much easier to keep track of who you're talking to.
  • Import/export csv files: It's now possible to import Mastodon-compatible CSV files for accounts you follow and accounts you block, making it much easier to migrate across instances. Export of these files is supported too.
  • Exclusive lists: You can now mark lists as "exclusive", which means that posts from accounts in an exclusive list will show up only in that list and not in your home timeline.
  • Show/hide posts on your profile: Previously only Public posts were shown on your web profile. This is still the default, but you can now choose to show unlisted posts on your web profile too (the Mastodon default), or to show no posts at all.
  • Lots of new themes: solarized, brutalist, ecks pee, and more.
  • Store worker queue on restart: when you stop the instance, pending tasks are stored into the database, and loaded again when you start up the instance, so that no tasks get lost between restarts.

Thanks for reading!

reshared this

in reply to GoToSocial

gotosocial - Link to source

GoToSocial

Hiya! Third and hopefully final release candidate for v0.17.0 of #GoToSocial:

github.com/superseriousbusines…

Fixed a couple cheeky bugs related to status web views and pending replies not being marked pending correctly.

For instructions to update to this release candidate from versions prior to 0.17.0-rc1, please read the release notes for v0.17.0-rc1 carefully, but replace all occurrences of rc1 with rc3.

If updating from 0.16.0 to this release candidate, there are several config file changes and some very large database migrations that will have to run.

Thanks!

#GoToSocial
in reply to GoToSocial

gotosocial - Link to source

GoToSocial

So far we've seen that there may be some memory issues for FreeBSD users running their instances with SQLite. The issue is that memory usage is far higher than it should be on those specific setups. We're currently investigating why this might be happening.

If you are one of the unlucky folks running into this issue, could you please try using this alternative build of the GoToSocial release candidate that we just uploaded, which uses a different SQLite driver?

github.com/superseriousbusines…

If the issue is resolved with that build, please let us know :)

mastodon - Link to source

My wife Kirsten @MoonCat and I decided to give potential podcasting a go. I know, 'Not another one?' But we hope this might be a bit of light entertainment for you.
Consider this a pilot to see how things go.

In this first episode we discuss a somewhat annoying Tiktok trend I heard about in a video, the point of hugging and our love of the 'Cautionary Tales' podcast from Tim Harford.

StroongeCast E01: Will You Peel My Orange? youtu.be/XeVO8pTfrK8

Download: onj.me/media/stroongecast/01_-…

@Kirsten Louis
This entry was edited (1 year ago)

mastodon - Link to source

C2S server for matrix.org accounts is blocked in Russia using deep packet inspection (DPI). That means people can no longer access their accounts without resorting to censorship circumvention technology.

The website and S2S federation server are still reachable from Russia.

@ooni @matrix

#Matrix #Russia #Roskomnadzor #Censorship

OONI Explorer screenshot, showing that access to "matrix-client.matrix.org" is restricted in Russia since September. It's a bar chart, date on horizontal axis, number of measurements on vertical axis. The graph starts with green bars (means "OK") an then sees a spike in yellow ("Anomaly") and grey ("Error") bars.
#matrix #Russia #censorship #roskomnadzor @The Matrix.org Foundation @OONI

mastodon - Link to source

How effective are bug bounties in securing critical, open source infrastructure? On 30 Sep 2024 in Berlin, following a keynote by Sabine Grützmacher (MdB), Dr. Ryan Ellis will present his research and dive into FOSS, security, and the public interest with an expert panel. Details & agenda for the evening event: sovereigntechfund.de/programs/…

We’ve set aside 30 spots for interested FOSS community members. Register here: events.sovereigntechfund.de/bu…

45 unique black outlines of beetles and bugs in a grid, mostly in squares with a lilac background, but with white and green squares interspersed. The bugs are all generative art by bleeptrack.
in reply to Odón Elorza

gotosocial - Link to source

modulux

Me parece una postura interesante, y desde leugo estoy de acuerdo en la importancia de socializar los medios de comunicación y las redes sociales. Lo que veo menos claro es esa tendencia de separa las redes sociales corporativas de otras hegemonías en los medios de comunicación de masas. No hicieron falta rdes sociales para colar el timo de la conspiración del 11M al país, solo el poder de la prensa, radio, y tele de toda la vida.

Creo que hay una cierta lucha sectorial interburguesa entre los propietarios de editoriales, televisiones, y otros medios de comunicación contra los propietarios de centros de datos, cables submarinos de fibra, y demás; y en esa lucha soy bastante neutral, porque no me creo que el periódico sea bueno y democrático y TikTok malo y antidemocrático en contraste.

goblin - Link to source

Ok, I should be sleeping right now, but what's happening is SO FUCKING CRAZY.

Long story short: WPEngine is suing Matt Mullenweg, Automattic and the WordPress foundation for slandering them. In return, Matt is suing them for trademark violation.

But, BUT, WPEngine has fired their first shot. And what a shot it is, friends:
Image/photo

Link to the full letter

Some extracts:

Stunningly, Automattic’s CEO Matthew Mullenweg threatened that if WP Engine did not agree to pay Automattic – his for-profit entity – a very large sum of money before his September 20th keynote address at the WordCamp US Convention, he was going to embark on a self-described “scorched earth nuclear approach” toward WP Engine within the WordPress community and beyond. When his outrageous financial demands were not met, Mr. Mullenweg carried out his threats by making repeated false claims disparaging WP Engine to its employees, its customers, and the world. Mr. Mullenweg has carried out this wrongful campaign against WP Engine in multiple outlets, including via his keynote address, across several public platforms like X,YouTube, and even on the Wordpress.org site, and through the WordPress Admin panel for all WordPress users, including directly targeting WP Engine customers in their own private WordPress instances used to run their online businesses

During calls on September 17th and 19th, for instance, Automattic CFO Mark Davies told a WP Engine board member that Automattic would “go to war” if WP Engine did not agree to pay its competitor Automattic a significant percentage of its gross revenues – tens of millions of dollars in fact – on an ongoing basis. Mr. Davies suggested the payment ostensibly would be for a “license” to use certain trademarks like WordPress, even though WP Engine needs no such license. WP Engine’s uses of those marks to describe its services – as all companies in this space do – are fair uses under settled trademark law and consistent with WordPress’ own guidelines. Automattic’s CFO insisted that WP Engine provide its response to this demand immediately and later, on the day of the keynote, followed up with an email reiterating a claimed need for WP Engine to concede to the demands “before Matt makes his WCUS keynote at 3:45 p.m. PDT today.”

In parallel and throughout September 19 and 20, Mr. Mullenweg embarked on a series of harassing text messages and calls to WP Engine’s board member and also its CEO, threatening that if WP Engine did not agree to pay up prior to the start of Mr. Mullenweg’s livestreamed keynote address at 3:45pm on September 20, he would go “nuclear” on WP Engine, including by smearing its name, disparaging its directors and corporate officers, and banning WP Engine from WordPress community events.


They... they have text message captures. In the pdf. Matt Mullenweg was trying to extort them ... by text messages. They seem to have the entire thing in the writting.

In the final minutes leading up to his keynote address, Mr. Mullenweg sent one last missive: a photo of the WordCamp audience waiting to hear his speech, with the message that he could shift gears and turn his talk into “just a Q&A” if WP Engine agreed to pay up


They finish requesting Automattic to "preserve, and not destroy, any and all documents or information in their possession, custody, or control that may be relevant to any dispute between WP Engine and Automattic". They are going to war, big time.

All this crap is just because they refuse to pay his protection money. And the guy has been stupid enough to put everything in writting.

Holy. Fucking. Shit.

HOLY FUCKING SHIT.

They are going to toast him alive

#wordpress #automattic #wpengine

reshared this

mastodon - Link to source

35% of #bisexual men in a relationship *with another man* have never told that partner about their bisexuality. And only the minority of us are very or fairly open about our #bisexuality to our male partners. That's from ILGA Europe. The norm is for us bi #men to be quiet about our bisexuality, even in same-gender relationships. #Gay men, you can think about that one during #BiVisibilityDay.

#queer #lgbtq

ilga-europe.org/report/interse…

#queer #LGBTQ #gay #bisexual #bisexuality #men #bivisibilityday
⇧