IRC: #techbytes @ Techrights IRC Network: Thursday, May 18, 2023

back to Techrights (Main Index)

beginning of new day, May 18

00:50 *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #techbytes

00:52 *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #techbytes

3 AM, May 18

03:19 *u-amarsh04 (~amarsh04@nqkitbgnqjad4.irc) has joined #techbytes

03:31 *u-amarsh04 has quit (Quit: Konversation terminated!)

03:32 *u-amarsh04 (~amarsh04@nqkitbgnqjad4.irc) has joined #techbytes

03:54 *u-amarsh04 has quit (Ping timeout: 2m30s)

4 AM, May 18

04:54 *u-amarsh04 (~amarsh04@nqkitbgnqjad4.irc) has joined #techbytes

5 AM, May 18

05:07 *u-amarsh04 has quit (Ping timeout: 2m30s)

05:36 *u-amarsh04 (~amarsh04@nqkitbgnqjad4.irc) has joined #techbytes

6 AM, May 18

06:23 *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #techbytes

06:26 *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #techbytes

06:45 *u-amarsh04 has quit (Ping timeout: 2m30s)

8 AM, May 18

08:20 schestowitz; <li>

08:20 schestowitz; <h5><a href="https://9to5linux.com/linux-kernel-6-2-reaches-end-of-life-users-urged-to-upgrade-to-linux-kernel-6-3">Linux Kernel 6.2 Reaches End of Life, Users Urged to Upgrade to Linux Kernel 6.3</a></h5>

↺ https://9to5linux.com/linux-kernel-6-2-reaches-end-of-life-users-urged-to-upgrade-to-linux-kernel-6-3">Linux

08:20 schestowitz; <blockquote>

08:20 schestowitz; <p>Being a short-lived kernel branch, Linux 6.2 has now reached end of life (EOL) with the Linux 6.2.16 release that was announced today by renowned kernel developer and maintainer Greg Kroah-Hartman, who urges users to upgrade to the latest Linux 6.3 kernel series as soon as possible.</p>

08:20 schestowitz; </blockquote>

08:20 schestowitz; </li>

08:20 schestowitz;

08:20 -TechBytesBot/#techbytes-Linux Kernel 6.2 Reaches End of Life, Users Urged to Upgrade to Linux Kernel 6.3 - 9to5Linux

08:31 *Noisytoot has quit (Quit: ZNC 1.8.2 - https://znc.in)

=> https://znc.in) ↺ https://znc.in)

08:32 *Noisytoot (~noisytoot@tkbibjhmbkvb8.irc) has joined #techbytes

10 AM, May 18

10:01 *u-amarsh04 (~amarsh04@nqkitbgnqjad4.irc) has joined #techbytes

10:24 *acer-box (~acer-box@freenode/user/schestowitz) has joined #techbytes

10:24 *schestowitz-TR2 has quit (Ping timeout: 120 seconds)

10:31 *u-amarsh04 has quit (Ping timeout: 2m30s)

10:39 schestowitz; +x2 <li>

10:39 schestowitz; <h5><a href="https://www.vice.com/en/article/z3m4e9/cnet-workers-unionize-as-automated-technology-threatens-our-jobs">CNET Workers Unionize as Automated Technology Threatens Our Jobs</a></h5>

↺ https://www.vice.com/en/article/z3m4e9/cnet-workers-unionize-as-automated-technology-threatens-our-jobs">CNET

10:39 schestowitz; <blockquote>

10:39 schestowitz; <p>Around 100 workers are unionizing at CNET, a popular tech news and product review site, in response to a lack of transparency from management regarding layoffs and the companys use of AI, according to an announcement by the union Tuesday.</p>

10:39 schestowitz; </blockquote>

10:39 schestowitz; </li>

10:39 -TechBytesBot/#techbytes-www.vice.com | CNET Workers Unionize as Automated Technology Threatens Our Jobs

10:56 *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #techbytes

11 AM, May 18

11:16 *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #techbytes

11:19 *Noisytoot has quit (Quit: ZNC 1.8.2 - https://znc.in)

=> https://znc.in) ↺ https://znc.in)

11:21 *Noisytoot (~noisytoot@tkbibjhmbkvb8.irc) has joined #techbytes

11:44 *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #techbytes

11:47 *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #techbytes

1 PM, May 18

13:50 *GNUmoon2 has quit (Ping timeout: 2m30s)

13:51 *GNUmoon2 (~GNUmoon@282dmj5h35cfi.irc) has joined #techbytes

11 PM, May 18

23:17 schestowitz; http://ipkitten.blogspot.com/2023/04/construing-claims-to-include-technical.html?showComment=1684256765283#c3378598045111789984

↺ http://ipkitten.blogspot.com/2023/04/construing-claims-to-include-technical.html?showComment=1684256765283#c3378598045111789984

23:17 schestowitz; Forgive me if this has already been addressed, but I am wondering whether a feature in claim 1 with a prima facie narrow meaning could be given a broader meaning when interpreted in light of the description? I have a specific case in mind, where claim 1 refers to a &quot;Boolean input&quot;. On the face of it, this would mean either true or false, 1 or 0. The description, however, makes it clear that this is actually intended to be much

23:17 schestowitz; broader, covering any input string. How should an opposition division construe the claim feature? Narrowly (and therefore possibly novel) or broadly (and therefore lacking novelty)?

23:17 -TechBytesBot/#techbytes-ipkitten.blogspot.com | Construing the claims to include technical effects mentioned in the description (T 1924/20) - The IPKat

23:18 schestowitz; http://ipkitten.blogspot.com/2023/05/breaking-in-person-proceedings-are.html?showComment=1684329325621#c8583714408016346706

↺ http://ipkitten.blogspot.com/2023/05/breaking-in-person-proceedings-are.html?showComment=1684329325621#c8583714408016346706

23:18 schestowitz; @proof of the pudding<br />Your suggestion to preemptively include in any petition dealing with Vico a request to exclude the chair of the BA from EBA panels must be considered. It could even be generalised so that the chair of the BA is 100 % exempted of acting as a judge and can focus on his/her <br /> managerial duties.</blockquote></li>

23:18 -TechBytesBot/#techbytes-ipkitten.blogspot.com | BREAKING: In-person proceedings are still the "Gold Standard" - Boards of Appeal start to diverge on ViCo (T 2432/19) - The IPKat

IRC: #techbytes @ Techrights IRC Network: Thursday, May 18, 2023

back to Techrights (Main Index)