otter

joined 2 years ago
MODERATOR OF
[–] otter@lemmy.ca 15 points 7 hours ago

Supposedly the outcry caused them to "put a pause on this launch for the time being", as of a few hours ago

Hey Mods, first thanks to all of you for all the feedback on this launch today - we really appreciate it. We're taking it all in and will be putting a pause on this launch for the time being.

For now, I suggest filling out the form if you don't want to be opted in. We'll keep all of you posted on our next steps, including the revised launch date.

 

The modmail has been copied below. The announcement is linked in the first comment, and people are justifiably annoyed.

Hi Mods,

We are in the process of rolling out a big overhaul to Subreddit Wikis, including a new layout, tools, discoverability, and more.

TL;DR - We’ve given wikis a makeover. The improved wiki (launching next week) includes: new tools and layout, additional safety features, more edit access options, and improved discoverability. For those with wikis built on old.reddit, we’ll move your existing content over, so that everything is preserved. Edits made via old.reddit after the migration won’t sync to the new system and vice versa.

Keeping a wiki fresh and up to date can be time-consuming, and mods shouldn’t have to do it all alone. As part of this update, “successful contributor access” will be enabled by default for your community wiki the week of July 14.

The entire wiki or individual pages can be restricted to “mod-only” editing at any time (after the above changes are made) within “Wiki settings” found in Mod Tools on desktop.

This setting manages for quality and safety while enabling more Wiki maintenance support and relevant content creation. In early testing, subreddits with this setting enabled did not require mod revisions.

To opt out of this setting being turned on in your community before July 14, please let us know via this form.

[–] otter@lemmy.ca 3 points 19 hours ago

We made a post about our actions here

https://lemmy.ca/post/44214013

[–] otter@lemmy.ca 3 points 1 day ago* (last edited 1 day ago) (2 children)

I think the title may be causing the downvotes, the first part of it sounds like a confirmation/ exposé rather than a personal analysis by the OP, which isn't necessarily a bad thing but might be misleading at first glance

Something like this might have done better

I didn't like how Mark Carney behaved at the stampede, and so I looked at the clip carefully to pick out a few points that may extend to how he treats the people around him

Note: I haven't had a chance to read the article yet, I'm hypothesizing based on the comment section on why people didn't like it

[–] otter@lemmy.ca 4 points 2 days ago

Neat

In practice, SUSE's Sovereign Premium Support is tailored for enterprises and public sector organizations that require strict data residency, privacy, and operational control within the EU. The service ensures that:

  • All support personnel and data are based in the EU, with named premium support engineers and service delivery managers assigned to each customer.
  • Customer support data is stored exclusively on EU-located networks and servers, addressing both regulatory and geopolitical concerns.
  • Access to sensitive data is strictly limited to EU-based staff, with a commitment to encrypting all data required for troubleshooting.
[–] otter@lemmy.ca 44 points 2 days ago (2 children)

Neat

In practice, SUSE's Sovereign Premium Support is tailored for enterprises and public sector organizations that require strict data residency, privacy, and operational control within the EU. The service ensures that:

  • All support personnel and data are based in the EU, with named premium support engineers and service delivery managers assigned to each customer.
  • Customer support data is stored exclusively on EU-located networks and servers, addressing both regulatory and geopolitical concerns.
  • Access to sensitive data is strictly limited to EU-based staff, with a commitment to encrypting all data required for troubleshooting.
13
Mastodon 4.4 (blog.joinmastodon.org)
 

cross-posted from: https://lemmy.ml/post/32887973

[–] otter@lemmy.ca 1 points 3 days ago (1 children)

Cool! You could post them here one at a time if you haven't already

[–] otter@lemmy.ca 6 points 3 days ago

It makes it more accessible, but part of it might also be SEO bait

I skipped to the second section

[–] otter@lemmy.ca 3 points 3 days ago (2 children)

Odd, something may have broken with the registration submission. We'll look into it

 

This article is divided into two chapters.

  • The first one, starting with section “Introduction to naming in programming” presents a review of scientific literature present on the topic. That section will deepen your understanding of the current body of knowledge on naming things.
  • The second chapter, starting with section “Guidelines for naming conventions in programming” presents actionable recommendations to improve your skills in choosing thoughtful class, function or variable names. If you’re looking for tips, go there.

There are only two hard things in Computer Science: cache invalidation and naming things.

[–] otter@lemmy.ca 2 points 4 days ago

!aardman@sh.itjust.works

[–] otter@lemmy.ca 19 points 4 days ago

Your post is being downvoted and I think it's because this isn't the right community for your question. This community is for linking to high quality comments and posts on the fediverse

This question is better for one of these

31
submitted 1 week ago* (last edited 1 week ago) by otter@lemmy.ca to c/retrocomputing
 

This is the same SDF that runs the instance that this community is on. Here is more info from the newsletter:

As SDF celebrates its 38th year we thank you for your continued support and we are grateful to have you as part of our community.

While SDF has a long history, we've always focused on building upon the UNIX platform to facilitate and implement your new ideas. Notably, much of that has focused on expanding our Fediverse offerings, but many of you have expressed interest in looking at the past: particularly retrocomputing.

SDF Vintage Systems has spawned a new charitable non-profit organization:

The Interim Computer Museum, located South of Seattle in Tukwila Washington!

https://icm.museum/

The Interim Computer Museum features self hosted and SDF co-located, membersupported, vintage systems of which 26 are accessible remotely.

Remote guest access to our vintage systems is free to all and you are welcome to try the machines out at https://connect.sdf.org/ or 'ssh menu@tty.sdf.org'. If there's a system you'd like to see, let us know!

Additionally ICM has begun work in the area of machine restoration and software preservation with a group of volunteer engineers. This work is being documented in a status blog with live streaming for knowledge and data sharing.

If you'd like to support our efforts, please visit https://icm.museum/ to read about the museum and see membership/sponsorship opportunities. Donations to the ICM are fully tax deductible and in many cases can be matched with an employer such as Apple, Google, Meta, Microsoft and Boeing.

We're looking for volunteer remote sysadmins as well as those who would like to participate in regional Vintage Computer Festivals. If you have an interest in doing this, please get in touch.

We hope that you find this news especially exciting. When we started the SDF Vintage Systems program we had hoped to be able to open a brick and mortar museum and we are very happy that this has come to fruition. With your help, we can bring it to self-sustainability and continue to let it grow.

Sincerely,

Stephen Jones (smj), SDF.ORG / ICM.MUSEUM

 

crossposted from !victoria@lemmy.ca

 

Two peach farmers in B.C.'s Okanagan region say they're optimistic for the upcoming harvest after years of climate disasters wreaking havoc on their crops.

B.C.'s farmers have been particularly affected by climate disasters over the last few years, with a heat dome in 2021 cooking fruit on the branches, and two subsequent cold snaps in the winter. One of those, in 2024, led to the destruction of a year's worth of crops in some areas.

But now, two stone fruit farmers in the Okanagan Valley say they hope the push to buy local helps them as they look forward to a productive peach crop later this summer.

Jennifer Deol, the owner of There and Back Again Farms in Kelowna, says she hasn't had a full crop of peaches since 2021.

"It has been hard to survive these past four years, but we're just grateful," she told CBC News.

"This season we've got fruit on the trees and the trees are looking healthy — the trees that did survive the winter of 2024."

 

A number of communities use scheduled threads to help get discussion started, and I thought this community could benefit from something like that. It reduces the pressure on individual users to be the first one to post a discussion post, since this community is mostly news/research articles.

It could be to chat about how things are going professionally, to share stories from that week, to discuss a piece of news/research in depth, etc.

If this sounds good to you, how often should the threads be scheduled? Any other considerations?

 

cross-posted from: https://lemmy.ca/post/47246359

Quoting from the page:

The B.C. Government commits to open ways of working to transform into a Digital Government. We leverage GitHub to achieve our objective. Our open practices let us to share source code and non-sensitive data with our government developer community and partners.

Within the Ministry of Citizens’ Services, the Developer Experience team’s purpose is offering the best support possible to developer teams. We centralize, streamline and innovate developer resources so we can contribute towards quick project starts, and facilitate continuous improvement.

Although developers work deeper in the government ecosystems, their deliverables are crucial to building public trust. Whether top-down or collaborative, developers finalize a vision by building products that both government workers and public can interact with. Joining our community

We look forward to working with you! Our team manages the centralized resource for government developers called DevHub. It has instructions for joining the bcgov organization.

If you have any questions or concerns, please submit a support request.

 

Quoting from the page:

The B.C. Government commits to open ways of working to transform into a Digital Government. We leverage GitHub to achieve our objective. Our open practices let us to share source code and non-sensitive data with our government developer community and partners.

Within the Ministry of Citizens’ Services, the Developer Experience team’s purpose is offering the best support possible to developer teams. We centralize, streamline and innovate developer resources so we can contribute towards quick project starts, and facilitate continuous improvement.

Although developers work deeper in the government ecosystems, their deliverables are crucial to building public trust. Whether top-down or collaborative, developers finalize a vision by building products that both government workers and public can interact with. Joining our community

We look forward to working with you! Our team manages the centralized resource for government developers called DevHub. It has instructions for joining the bcgov organization.

If you have any questions or concerns, please submit a support request.

view more: next ›