Trakt was popular in the past, and has integrations with Jellyfin, although some people may have left after their pricing/feature changes earlier this year.

Here is a relevant thread you might find helpful: https://lemmy.ca/post/38746526

Your account is marked as a bot, you can change that toggle in your account settings

What are your long term plans for it? Are you leaning towards open source / self hosted, paid plans, ads, etc

I guess everyone just browses all anyway, for now. So they don’t want things removed that have comments regardless of where it’s posted.

Yea I’ve seen this as well. I think part of the problem is a lack of an automod, since rule breaking content sticks around for hours accumulating comments before a mod sees it. Users are good about reporting spam, since it’s very obvious, but not everyone is familiar enough with community rules to report based on those.

From the comments of the article

Deleting it and re-installing from the new uncompromised release is not a big deal, but having to go and factory reset all one’s streaming devices and re-configure them from scratch is rather time consuming (I have several).

In yuliskov’s github announcement, he doesn’t come across as this being particularly urgent, and is NOT making statements like “reset all your devices, change all your streaming account passwords”. He just said going forward there won’t be updates and it will have to be re-installed from the new tree.

It seems at this point for most people, if google and amazon haven’t uninstalled it and you are not running 30.43 or 30.47, then keep using it, and when the new version is released, remove the old one and install the new one.

Factory resetting is likely overkill. Android apps are, theoretically, sandboxed, so they shouldn’t be able to affect the system or other apps. Uninstalling the infected app should be enough to clean up, but a factory reset is a guaranteed way, which is why I mention it.

It seems to be one person that’s doing it manually across a number of communities?

I think the website is old, and the blurry bits were a prediction

The new cycle is expected to start late in 2019 or in 2020, with solar maximum to be reached between 2023 and 2026 and the maximum (smoothed) sunspot number in the 95 to 130 range.

A different color and a legend would have been nicer imo

Appreciate the write-up, thanks!

I found this diagram, and this should mean that the levels will drop by around 2030?

Source: https://www.stce.be/news/453/welcome.html

Adjective-Noun-# is the usual format for those. This looks different, like someone put in a list of wholesome / floral / nature-y terms into the name generator, in order to have wholesome looking accounts

They must have been editing the article back and forth. I also only saw “WebRender Layer Compositor”, but it’s organized nicely now

You mentioned being frustrated at Plausible. What did you not like about it?

I haven’t tried Plausible, but it seemed popular

Sounds like they joined a large group chat as a member

The FBI, the documents show, gained access to conversations in a “courtwatch” Signal group that helps coordinate volunteer activists who monitor public proceedings at three New York federal immigration courts. The US government has repeatedly been accused of violating immigrants’ due process rights at those courts.

Now we need a windows compatibility program called “com-plain”

Simplified communication, components, compatibility, whatever makes the backronym work

Hi Sarah,

Sorry for the delay in getting to this. We really appreciate the feedback! We’re currently working on an update to our site, and will continue to incorporate feedback over time.

We’ve iterated over these pages a few times, and while there is definitely more that we can do to improve it, I feel that we need a few different guides for each target demographic or use case. Ideally, someone will find their way to the appropriate resource, depending on the level of detail or transparency that they are looking for. The goal of the two guide pages above were mainly to explain what it is that our non-profit is doing, and how it differs from traditional social media. A lot of alternative social media platforms advertise transparency and a positive user experience, and so the guide pages above were intended for people who want an explanation on how the Fediverse can actually deliver on those promises.

Right now, the page we have for users that simply want to sign up for a platform is here: https://fedecan.ca/en/guide/fedecan/our-platforms

We can certainly improve the flow for users that want to get to that page, and the page itself. We haven’t prioritized that aspect, since we figured that users who are learning about one of the platforms might be going to it directly, instead of through our non-profit’s site.

Would you have some suggestions on what a page like that should include, or what you would like to see in the guides instead?

I have students who can help you with this stuff for free. If you’re interested, DM me.

We’d love the help and feedback, especially if it’s something that would complement their studies! Thank you for offering :)

Good point, I didn’t see the list of which instances were still up when making the meme. A number of fairly large instances were still up

It might be cool to put together a list of what each instance depends on, for reference during future outages. CloudFlare, hosting providers, etc.

You can view the source for my comment and copy paste :)

Do this in order:

1. Install with LUKS full-disk encryption and Btrfs subvolumes for @ and @home so snaps are atomic.

2. Enable automatic snapshots with Timeshift or snapper.

3. Export your package lists:

   • Debian/Ubuntu: dpkg --get-selections > packages.txt
   • Arch: pacman -Qqe > pkglist.txt
   • also flatpak list --app > flatpaks.txt

4. Put your dotfiles under version control and manage them with chezmoi or GNU Stow.

5. Use Flatpak for GUI apps, containerized toolchains (podman) for dev environments, and keep only system-critical packages in the distro manager.

6. Back up with Borg: borg init --encryption=repokey /path/to/repo ; borg create repo::$(date +%F) /home /etc --stats ; borg prune --keep-daily=7 --keep-weekly=4 --keep-monthly=6

7. Keep a small, bootable USB with the exact kernel/tools you use so you can unlock LUKS and mount Btrfs snapshots.

8. Test restores quarterly: restore a snapshot to a spare partition and boot it. Do that for a year and tell me reinstalling is fun again.

Why post something in the first place then?

The other user asked you for more context because they want to understand/ learn from what you’ve shared.

Your post is missing context.

While I don’t have a direct answer, I know that my university had some courses dedicated to this topic. I think these are some of them:

https://www.students.cs.ubc.ca/~cs-311/2025W1/nav/goals.html

https://www.cs.ubc.ca/course-section/cpsc-411-201-2020w

https://www.cs.ubc.ca/~rxg/cpsc509-spring-2024/

The second one is described as

The goal of this course is to give students experience designing, implementing, and extending programming languages. Students will start from a machine language, the x86-64 CPU instruction set with Linux system calls (x64), and incrementally build a compiler for a subset of Racket to this machine language. In the process, students will practice building, extending, and maintaining a complex piece of software, and practice creating, enforcing, and exploiting abstractions formalized in programming languages.

The course assumes familiarity with basic functional programming in Racket, and some simple imperative programming in assembly.

Those links might give you something to search off of?

And what’s the purpose of developing more languages anyway?

At some level, I think it’s this:

https://xkcd.com/927/

Looks good!

I have one suggestion, the white text on bright green on the website is hard to read. Maybe you can pick different colors, or put borders around the characters.

Linux Foundation

The slide people are mentioning

In text:

This is a brief summary of Servo’s project history. The project was started by Mozilla in 2012, at that time they were developing the Rust language itself (somehow Mozilla used Servo, a web rendering engine, as a testing project to check that Rust language was good enough). In any case we cannot consider it really “new”, but Servo is way younger than other web engines that started decades before.

In 2020, Mozilla layoff the whole Servo team, and transferred the project to Linux Foundation. That very same year the Servo team had started the work in a new layout engine. The layout engine is an important and complex part of a web engine, it’s the one that calculates the size and position of the different elements of the website. Servo was starting a new layout engine, closer to the specifications language and with similar principles to what other vendors were also doing (Blink with LayoutNG and WebKit with Layout Formatting Context). This was done due to problems in the design of the original layout engine, which prevented to implement properly some CSS features like floats. So, from the layout engine point of view, Servo is quite a “new” engine.

In 2023, Igalia took over Servo project maintenance, with the main goal to bring the project back to life after a couple of years with minimal activity. That very same year the project joined Linux Foundation Europe in an attempt to regain interest from a broader set of the industry.

A highlight is that the project community has been totally renewed and Servo’s activity these days is growing and growing.

The WPT scores should give an idea of how “ready” it is: https://servo.org/wpt/

It shows that the situation in 2023 was pretty bad, but today Servo is passing more than 1.7 million subtests (a 92.7% of the tests that we run, there are some tests skipped that we don’t count here).