Searching We.Love.Privacy.Club

Twts matching #practical
Sort by: Newest, Oldest, Most Relevant

CNCF Launches Technology Landscape Radar, Reference Architectures to Address Gaps in Cloud Native Ecosystem
CNCF’s End User Technical Advisory Board has compiled new materials to promote best practices and simplify the adoption of cloud native technologies  SALT LAKE CITY, Utah – KubeCon + CloudNativeCon North America – November 14, 2024… ⌘ Read more

⤋ Read More

KubeCon + CloudNativeCon North America 2024 co-located event deep dive: Kubernetes on Edge
Co-chairs: Tina Tsou and Mars Toktonaliev November 12, 2024 Salt Lake City, Utah Kubernetes on Edge Day demonstrates edge computing is here, and it’s powered by Kubernetes. We’re showcasing real-world use cases, best practices, and cutting-edge… ⌘ Read more

⤋ Read More

Docker at Cloud Expo Asia: GenAI, Security, and New Innovations
At Cloud Expo Asia 2024, Docker showcased its latest innovations in AI integration, security best practices, and product updates, highlighting how containers empower GenAI workflows and enable efficient, secure software development. ⌘ Read more

⤋ Read More

KubeCon + CloudNativeCon North America 2024 co-located event deep dive: Platform Engineering Day
Co-chairs: Paula Kennedy, Stacey Potter, Vijay Chintha November 12, 2024 Salt Lake City, Utah Platform Engineering Day focuses on solutions over tooling. We believe that Platform Engineering is a vital practice that helps organizations to increase their speed… ⌘ Read more

⤋ Read More

More thoughts about changes to twtxt (as if we haven’t had enough thoughts):

  1. There are lots of great ideas here! Is there a benefit to putting them all into one document? Seems to me this could more easily be a bunch of separate efforts that can progress at their own pace:

1a. Better and longer hashes.

1b. New possibly-controversial ideas like edit: and delete: and location-based references as an alternative to hashes.

1c. Best practices, e.g. Content-Type: text/plain; charset=utf-8

1d. Stuff already described at dev.twtxt.net that doesn’t need any changes.

  1. We won’t know what will and won’t work until we try them. So I’m inclined to think of this as a bunch of draft ideas. Maybe later when we’ve seen it play out it could make sense to define a group of recommended twtxt extensions and give them a name.

  2. Another reason for 1 (above) is: I like the current situation where all you need to get started is these two short and simple documents:
    https://twtxt.readthedocs.io/en/latest/user/twtxtfile.html
    https://twtxt.readthedocs.io/en/latest/user/discoverability.html
    and everything else is an extension for anyone interested. (Deprecating non-UTC times seems reasonable to me, though.) Having a big long “twtxt v2” document seems less inviting to people looking for something simple. (@prologic@twtxt.net you mentioned an anonymous comment “you’ve ruined twtxt” and while I don’t completely agree with that commenter’s sentiment, I would feel like twtxt had lost something if it moved away from having a super-simple core.)

  3. All that being said, these are just my opinions, and I’m not doing the work of writing software or drafting proposals. Maybe I will at some point, but until then, if you’re actually implementing things, you’re in charge of what you decide to make, and I’m grateful for the work.

⤋ Read More

@prologic@twtxt.net Thanks for writing that up!

I hope it can remain a living document (or sequence of draft revisions) for a good long time while we figure out how this stuff works in practice.

I am not sure how I feel about all this being done at once, vs. letting conventions arise.

For example, even today I could reply to twt abc1234 with “(#abc1234) Edit: …” and I think all you humans would understand it as an edit to (#abc1234). Maybe eventually it would become a common enough convention that clients would start to support it explicitly.

Similarly we could just start using 11-digit hashes. We should iron out whether it’s sha256 or whatever but there’s no need get all the other stuff right at the same time.

I have similar thoughts about how some users could try out location-based replies in a backward-compatible way (append the replyto: stuff after the legacy (#hash) style).

However I recognize that I’m not the one implementing this stuff, and it’s less work to just have everything determined up front.

Misc comments (I haven’t read the whole thing):

  • Did you mean to make hashes hexadecimal? You lose 11 bits that way compared to base32. I’d suggest gaining 11 bits with base64 instead.

  • “Clients MUST preserve the original hash” — do you mean they MUST preserve the original twt?

  • Thanks for phrasing the bit about deletions so neutrally.

  • I don’t like the MUST in “Clients MUST follow the chain of reply-to references…”. If someone writes a client as a 40-line shell script that requires the user to piece together the threading themselves, IMO we shouldn’t declare the client non-conforming just because they didn’t get to all the bells and whistles.

  • Similarly I don’t like the MUST for user agents. For one thing, you might want to fetch a feed without revealing your identty. Also, it raises the bar for a minimal implementation (I’m again thinking again of the 40-line shell script).

  • For “who follows” lists: why must the long, random tokens be only valid for a limited time? Do you have a scenario in mind where they could leak?

  • Why can’t feeds be served over HTTP/1.0? Again, thinking about simple software. I recently tried implementing HTTP/1.1 and it wasn’t too bad, but 1.0 would have been slightly simpler.

  • Why get into the nitty-gritty about caching headers? This seems like generic advice for HTTP servers and clients.

  • I’m a little sad about other protocols being not recommended.

  • I don’t know how I feel about including markdown. I don’t mind too much that yarn users emit twts full of markdown, but I’m more of a plain text kind of person. Also it adds to the length. I wonder if putting a separate document would make more sense; that would also help with the length.

⤋ Read More

Kubecon + CloudNativeCon North America 2024 co-located event deep dive: Data on Kubernetes Day
Co-chairs: Melissa Logan and Adam DurrNovember 12, 2024Salt Lake City, Utah Organizations like Etsy, Grab, Dish Network, and Chick-fil-A have standardized on Kubernetes and shared best practices for running different types of stateful workloads. Our aim for the… ⌘ Read more

⤋ Read More

CNCF and the Linux Foundation partner with Unified Patents on a community-driven approach to safeguard open source innovation from patent trolls
Now is the time for the open source ecosystem to band together and find strength in numbers  CNCF and The Linux Foundation are expanding their partnership with Unified Patents to protect open source software from non-practicing entities (NPEs), c … ⌘ Read more

⤋ Read More
In-reply-to » @movq Is there a good way to get jenny to do a one-off fetch of a feed, for when you want to fill in missing parts of a thread? I just added @slashdot to my private follow file just because @prologic keeps responding to the feed :-P and I want to know what he's commenting on even though I don't want to see every new slashdot twt.

@prologic@twtxt.net I believe you when you say registries as designed today do not crawl. But when I first read the spec, it conjured in my mind a search engine. Now I don’t know how things work out in practice, but just based on reading, I don’t see why it can’t be an API for a crawling search engine. (In fact I don’t see anything in the spec indicating registry servers shouldn’t crawl.)

(I also noticed that https://twtxt.readthedocs.io/en/latest/user/registry.html recommends “The registries should sync each others user list by using the users endpoint”. If I understood that right, registering with one should be enough to appear on others, even if they don’t crawl.)

Does yarnd provide an API for finding twts? Is it similar?

⤋ Read More

Docker Best Practices: Understanding the Differences Between ADD and COPY Instructions in Dockerfiles
What are Docker ADD/COPY instructions and when should you use them? We explain the differences between the ADD and COPY instructions in Dockerfiles, including when to use each based on security, functionality, and build context. ⌘ Read more

⤋ Read More

How to Measure DevSecOps Success: Key Metrics Explained
Discover two key metrics to measure your DevSecOps progression effectively. Learn how tracking security vulnerabilities over time and ensuring compliance with security policies can enhance your organization’s security posture, driving continuous improvement in your DevSecOps practices. ⌘ Read more

⤋ Read More

Mastering DevSecOps with Devtron: a strategic approach
Member post originally published on the Devtron blog by Nishant As the adoption of Kubernetes continues to grow, organizations encounter numerous challenges in securing their software development and deployment processes. Integrating security practices into DevOps, known as DevSecOps,… ⌘ Read more

⤋ Read More

Sipeed Lichee Book 4A: Affordable RISC-V Laptop with Upgradeable Computer Module
The Sipeed Lichee Book 4A is a cost-effective laptop utilizing RISC-V architecture, designed primarily for developers interested in exploring this platform. It merges standard laptop features with functionalities tailored to RISC-V, offering a practical tool for both software development and general use. According to recent updates on the company’s social media, the Sipeed Lichee Book … ⌘ Read more

⤋ Read More

Does your observability practice lack maturity? Here’s what to do
Member blog post originally published on the Logz.io blog by Jake O’Donnell Observability isn’t new. But organizations are struggling to adopt mature observability practices, and the impact on business is palpable. Organizations are seeing the value of observability for… ⌘ Read more

⤋ Read More

A step-by-step guide to securely upgrading your EKS clusters
Member post originally published on Fairwinds’s blog by Stevie Caldwell As an agile open source project, Kubernetes continues to evolve, as does the cloud computing landscape. Keeping up with the latest versions isn’t practical for many organizations, and… ⌘ Read more

⤋ Read More

(Updated) Pimoroni’s NVMe Base Duo Brings New Storage Options to Raspberry Pi 5
This week, Pimoroni introduced the NVMe Base Duo, a new storage solution for Raspberry Pi 5 users. It accommodates either one or two M-key NVMe SSDs, ranging from sizes 2230 to 2280. Designed to enhance the Raspberry Pi 5, this device provides a practical method for expanding storage capacity. Leveraging PCIe Gen 2 technology, the […] ⌘ Read more

⤋ Read More

Get the first look at CloudNativeSecurityCon North America 2024’s schedule, add-on events, and more
The schedule for CloudNativeSecurityCon North America 2024 is now live, and is filled with 75 sessions offering practical solutions and thoughtful discussions of some of the biggest challenges in security today. The conference will be held June 26… ⌘ Read more

⤋ Read More

Celebrating 1 year of A11y Design Bootcamp: Takeaways and tips
A11y Design Bootcamp is a live educational program that consists of exercises, discussions, and knowledge shares to raise awareness of web accessibility best practices, the role designers play in creating accessible products, and how to advocate for accessibility with cross-functional partners.

The post [Celebrating 1 year of A11y Design Bootcamp: Takeaways and tips](https://github.blog/2024-05-02-celebrating-1- … ⌘ Read more

⤋ Read More

Early explorations and practices of Xline, a stateful application managed by Karmada
Member post by DatenLord Background and Motivation More and more IT vendors are now embracing cross-cloud multi-clustering as cloud-native technologies and cloud markets continue to mature. Here’s Flexera’s mid-2023 survey on the cloud-native market’s acceptance of multi-cloud, multi-cluster… ⌘ Read more

⤋ Read More

Pinellas County - Long Run: 10.19 miles, 00:09:43 average pace, 01:39:03 duration
practicing 3 minutes running and one minute walking. not only for the knee but also for the PTC (~46.6 miles) coming in about 17 weeks. the knee actually hurt a little the first 5 miles but afterwards nothing. not sure if i finally found my stride but it felt great once the dull pain was gone.
#running

⤋ Read More

WebAssembly on Kubernetes: the practice guide (part 02)
Community post by Seven Cheng | View part one here In the previous article, I gave an overview of Wasm’s features and advantages. I also explained how to run Wasm modules within container environments. In this article, I… ⌘ Read more

⤋ Read More

Pimoroni’s NVMe Base Duo Brings New Storage Options to Raspberry Pi 5
This week, Pimoroni introduced the NVMe Base Duo, a new storage solution for Raspberry Pi 5 users. It accommodates either one or two M-key NVMe SSDs, ranging from sizes 2230 to 2280. Designed to enhance the Raspberry Pi 5, this device provides a practical method for expanding storage capacity. Leveraging PCIe Gen 2 technology, the […] ⌘ Read more

⤋ Read More

Pinellas County - Long Run: 17.80 miles, 00:08:57 average pace, 02:39:13 duration
practiced a marathon pacing strategy (simulated) of 5km/10mi/10mi/5km. went pretty well even though i was going faster than the paces at each step. but overall i felt good. also scouted out one of the two overpasses i will have to climb during the race. definitely nothing compared to the regular ones. freezing! started at 33F and ended at 45F. pretty lonely out there because the cold kept everyone inside.
#running

⤋ Read More