Technology

34728 readers
96 users here now

This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.


Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.


Rules:

1: All Lemmy rules apply

2: Do not post low effort posts

3: NEVER post naziped*gore stuff

4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.

5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)

6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist

7: crypto related posts, unless essential, are disallowed

founded 5 years ago
MODERATORS
2076
2077
 
 

After being purchased by Snapchat, it appears that gfycat has been abandoned.

The Gfycat service is being discontinued. Please save or delete your Gfycat content by visiting https://www.gfycat.com and logging in to your account. After September 1, 2023, all Gfycat content and data will be deleted from gfycat.com

2078
2079
 
 
2080
 
 
2081
 
 

What happened in Marketing today!

1/ Twitter & Elon Musk have gone rogue as Elon musk introduces new limits to Twitter.

Unverified accounts can read only 600 posts a day & Verified ones 6,000. And new unverified ones with 300 posts limit.

2/ Google Universal Analytics says goodbye to all the marketers.

  • new update: New GA4 users will not have access to some attribution models.

3/ Attest & Modernretail’s research shows since the TikTok US ban issues. Instead of consumption decrease, 32% increase was seen.

4/ WPP partners with Contentful, A growing Marketing CRM & Data platform.

5/ Pinterest is going deep with targeting, As the platform is building a patent to find audience interest through email data of user.

6/ Google Introduces Search Page Checkout option for businesses. No need to visit the website!

7/ New Reddit API Policies are also live now!

8/ Budlight reintroduces the BudKnight. And disapproves allegations of firing top Marketing Executives.

9/ New Endorsement FTC policies for Influencers need to have more clear paid partnership policies for Influencer content.

  • it is manadtory for Non-EU Bloggers & Influencers with US viewers.

10 / Link from your website or blog to Twitter, now requires sign-In first. No chances of users viewing the content simply.

11/ Huge Fitness Influencer Joe Aesthetics Dead at age of 30. (Not marketing, but RIP)

12/ Adobe & Walmart are the highest paying brands amoong Influencer marketing brands.

I hope you liked the breakdown curated from The Social Juice Newsletter. I will see you on Monday with new updates.

2082
2083
2084
 
 

cross-posted from: https://radiation.party/post/33742

[ comments | sourced from HackerNews ]

2085
2086
2087
 
 

🍿

2088
2089
 
 

Probably not but one can hope… to the Fediverse lemmings!

2090
2091
 
 

a Louis Rossmann video.

2092
2093
2094
2095
2096
2097
2098
 
 

Hey everyone! So I've been doing some playing around with Mint Linux and have quite enjoyed it in the virtual machine. Thank all of you for the insight into the mindset I should take when approaching a new distribution.

Now that I'm not struggling as much with the terminal and other general computer organizational problems, I wanted to learn how to train my own chat-bot assistants. These assistants would be trained on monographs, textbooks, and other scholarly resources on topics I've been trying to learn more deeply.

I was wondering if anyone here has done this before, and if you have any advice to lend me!

Thanks for all the help!

2099
 
 

https://web.archive.org/web/20230630111531/https://rockylinux.org/news/keeping-open-source-open/

ArticleEvery user of Rocky Linux is valued and their contributions matter. From software engineers to IT professionals and hobbyists, together, we are all part of the Linux and open source community. The Rocky Enterprise Software Foundation was established based on our shared vision that open source software should remain stable, accessible to all, and managed by the community.

This commitment is ingrained in everything we do. Since the inception of the Rocky project, we have prioritized reproducibility, transparency in decision-making, and that no single vendor or company can ever hold the project hostage. When we first started, we discussed our model and mission, and we decided not to bisect the Enterprise Linux community. Instead, in the spirit of open source principles and standards, we created something compatible with Red Hat Enterprise Linux (RHEL). By adhering to this approach, we adhere to a single standard for Enterprise Linux and align ourselves with the original goals of CentOS.

However, Red Hat has recently expressed their perspective that they ”do not find value in a RHEL rebuild.” While we believe this view is narrow-minded, Red Hat has taken a strong stance and limited access to the sources for RHEL to only their paying customers. These sources primarily consist of upstream open source project packages that are not owned by Red Hat.

Previously, we obtained the source code for Rocky Linux exclusively from the CentOS Git repository as they recommended. However, this repository no longer hosts all of the versions corresponding to RHEL. Consequently, we now have to gather the source code from multiple sources, including CentOS Stream, pristine upstream packages, and RHEL SRPMs.

Moreover, Red Hat’s Terms of Service (TOS) and End User License Agreements (EULA) impose conditions that attempt to hinder legitimate customers from exercising their rights as guaranteed by the GPL. While the community debates whether this violates the GPL, we firmly believe that such agreements violate the spirit and purpose of open source. As a result, we refuse to agree with them, which means we must obtain the SRPMs through channels that adhere to our principles and uphold our rights.

The latency of this status update has been due to our desire to balance the needs of the community and technical requirements, with the challenges to open source and community principles that Red Hat has created. Fortunately, there are alternative methods available to obtain source code, and we would like to highlight two examples:

One option is through the usage of UBI container images which are based on RHEL and available from multiple online sources (including Docker Hub). Using the UBI image, it is easily possible to obtain Red Hat sources reliably and unencumbered. We have validated this through OCI (Open Container Initiative) containers and it works exactly as expected.

Another method that we will leverage is pay-per-use public cloud instances. With this, anyone can spin up RHEL images in the cloud and thus obtain the source code for all packages and errata. This is the easiest for us to scale as we can do all of this through CI pipelines, spinning up cloud images to obtain the sources via DNF, and post to our Git repositories automatically.

These methods are possible because of the power of GPL. No one can prevent redistribution of GPL software. To reiterate, both of these methods enable us to legitimately obtain RHEL binaries and SRPMs without compromising our commitment to open source software or agreeing to TOS or EULA limitations that impede our rights. Our legal advisors have reassured us that we have the right to obtain the source to any binaries we receive, ensuring that we can continue advancing Rocky Linux in line with our original intentions.

While we continuously explore other options, the aforementioned approaches are subject to change. However, our unwavering dedication and commitment to open source and the Enterprise Linux community remain steadfast.

In the unfortunate event that Red Hat decides to ramp up efforts to negatively impact the community, Rocky Linux will persist to continue serving the best interests of the entire open source community.

As a reminder, we welcome everyone to contribute to our efforts. You can learn more about how you can join us and all of the various ways to contribute on our wiki. Want to voice your support for Rocky Linux? Help us spread the word by sharing with your network, engaging with or contributing to the community, or telling friends about us. Our community is vital to our success, and we value your support. Together, we can make Rocky Linux continue to thrive!

2100
view more: ‹ prev next ›