Email or username:

Password:

Forgot your password?
17 posts total
scy

So these four things happened:

1. #Bitwarden, who always advertised being open source, introduced a non-free dependency into their client.

2. People start speculating whether this means that Bitwarden will become proprietary. github.com/bitwarden/clients/i

3. After three days of speculation, founder and CTO Kyle Spearrin posts a comment saying that this is just a measure to isolate a part of the code from the GPL.

4. He then closes & locks the issue.

Looks totally not suspicious, yeah. šŸ˜¬

So these four things happened:

1. #Bitwarden, who always advertised being open source, introduced a non-free dependency into their client.

2. People start speculating whether this means that Bitwarden will become proprietary. github.com/bitwarden/clients/i

3. After three days of speculation, founder and CTO Kyle Spearrin posts a comment saying that this is just a measure to isolate a part of the code from the GPL.

Show previous comments
Andy Mouse

@scy I saw this coming over a year ago, and started switching to KeePassDX. I think I smelled the capitalist rot starting to take hold.

64 mastodonz logistics co-op

@scy if you can prove that the two halves of the code are in fact one program, the gpl would apply

is it possible for someone else to build an open source front end?

WerySkok :verified_think:

@scy I'm happy that I use KeePassXC with Nextcloud sync

scy

Oh, nice, Codeberg Pages supports proper HTTP redirects these days!

docs.codeberg.org/codeberg-pag

Including catch-alls like /my-spa/* to /my-spa/index.html šŸ‘

Thanks @Codeberg!

#Codeberg #CodebergPages #HTTP #redirect #WebHosting

n0toose

@scy @Codeberg lowkey didn't even know this one :D

scy

Interesting. According to Brent Spiner (the actor who plays the android Data in Star Trek: The Next Generation)

1) it was Patrick Stewart's UK pronunciation of his character's name (day-tah instead of the US's dah-tah) that made this pronunciation canon, and

2) the character of Data and the popularity of Star Trek has led to "day-tah" now being the common pronunciation in the US, too.

youtu.be/xeqTMTOxid8 (Ļ€ min)

#StarTrek #StarTrekTNG #TNG #data #pronunciation #English #EnglishLanguage

Show previous comments
PensionDan

@scy US pronunciation would be day-dah, right?

CM Skellington

@scy @swizzlevixen I prefer to give that nod to Ke Huy Quan in Goonies. ;-)

bent

@scy love the episode where he corrects the mispronounciation of his name.

scy

Did you know that #XScreenSaver (yes, the collection of screensavers for X11) is available on Android?

And that #Google requires it to have a privacy policy in order to be available in the Play Store?

And that the maintainer chose to crowd-source a privacy policy where every item starts with "Unlike Google"?

It's become a great list of all the privacy violations Google did and still does. And I thought that it's gonna be long, but it's even longer than I imagined.

jwz.org/xscreensaver/google.ht

Did you know that #XScreenSaver (yes, the collection of screensavers for X11) is available on Android?

And that #Google requires it to have a privacy policy in order to be available in the Play Store?

And that the maintainer chose to crowd-source a privacy policy where every item starts with "Unlike Google"?

XScreenSaver for Android ā€¢ Privacy Policy

Unlike Google, XScreenSaver collects no user data.

Unlike Google, XScreenSaver uses no user data, having collected no user data.

Unlike Google, XScreenSaver shares no user data, having collected no user data.

Unlike Google, XScreenSaver has no need to process requests for deletion of that user data, having collected no user data.

Unlike Google, XScreenSaver will honor deletion requests if you email us asking to delete all none of your user data that does not exist.

Unlike Google, XScreenSaver will never share user data with anyone, as it has no user data to share.

Unlike Google, XScreenSaver will never build an un-auditable personal profile of you.

Unlike Google, XScreenSaver will never use cookies.

Unlike Google, XScreenSaver will never track your location.

Unlike Google, XScreenSaver will never track your location even if you asked them not to.

Unlike Google, XScreenSaver will never track your location and lie about it.

Unlike Google, XScreenSaver will never prevent you from running an ad blocker.

Unlike Google, XScreenSaver will never restrict your ability to extend the software to protect your own privacy and security.

(continues off screen)
Show previous comments
Henning Paul DC4HP

@scy But will it (unlike Google) never give you up, let you down or run around and desert you?

scy

when you find a loaf on the street at 0:14 in the night

#cat #cats #catcontent

On the border between a cobblestone pavement and some shrubs lies, lit by sodium vapor lamps, a white-and-orange cat, looking very unimpressed.
scy

Eek. Apparently liblzma (part of the xz package) has a backdoor in versions 5.6.0 and 5.6.1, causing SSH to be compromised.

openwall.com/lists/oss-securit

This might even have been done on purpose by the upstream devs.

Developing story, please take with a grain of salt.

The 5.6 versions are somewhat recent, depending on how bleeding edge your distro is you might not be affected.

#liblzma #xz #lzma #backdoor #ITsecurity #OpenSSH #SSH

scy

Red Hat released an urgent security alert for Fedora 41 and Rawhide users:

> PLEASE IMMEDIATELY STOP USAGE OF ANY FEDORA 41 OR FEDORA RAWHIDE INSTANCES for work or personal activity.

redhat.com/en/blog/urgent-secu

> Although Fedora 40 beta contained the 5.6 version of xz in an update, the build environment prevents the injection from correctly occurring, and has not been shown to be compromised. Fedora 40 has now reverted to the 5.4.x versions of xz.

#RedHat #Fedora #FedoraRawhide #Fedora41

Red Hat released an urgent security alert for Fedora 41 and Rawhide users:

> PLEASE IMMEDIATELY STOP USAGE OF ANY FEDORA 41 OR FEDORA RAWHIDE INSTANCES for work or personal activity.

redhat.com/en/blog/urgent-secu

> Although Fedora 40 beta contained the 5.6 version of xz in an update, the build environment prevents the injection from correctly occurring, and has not been shown to be compromised. Fedora 40 has now reverted to the 5.4.x versions of xz.

Yesterday, Red Hat Information Risk and Security and Red Hat Product Security learned that the latest versions of the ā€œxzā€ tools and libraries contain malicious code that appears to be intended to allow unauthorized access. Specifically, this code is present in versions 5.6.0 and 5.6.1 of the libraries - at this time, only Fedora 41 and Fedora Rawhide contain these libraries. This vulnerability was assigned CVE-2024-3094.

Although Fedora 40 beta contained the 5.6 version of xz in an update, the build environment prevents the injection from correctly occurring, and has not been shown to be compromised.  Fedora 40 has now reverted to the 5.4.x versions of xz. 

PLEASE IMMEDIATELY STOP USAGE OF ANY FEDORA 41 OR FEDORA RAWHIDE INSTANCES for work or personal activity.
scy

Today I finally sat down to learn how #FIDO #U2F keys support an "unlimited" number of websites on a single token, without compromising privacy, and without running out of memory on the token.

Reusing the same public/private keypair would allow websites to track tokens. So, the token generates a new keypair on each registration. But where is it stored?

With the website! The token encrypts the private key with a token-specific secret and receives it back from the website on each login request.

scy

Check out fidoalliance.org/specs/u2f-spe for details on how this whole process works.

U2F is built in a rather flexible way, so there's also the possibility for the token to have onboard storage and keep its private keys to itself, however it doesn't have "unlimited" storage anymore in that case.

Chris

@scy the most current implementation would be fido2 non-discoverable keys. And you should have come to my cccamp talk so you would have known in summer already :-)

I'll go over it in a fresh version at gpn22 I think

scy

A few days ago, my groovebox, the #SynthstromDeluge, running the new and awesome community-built firmware, crashed, which was very cool.

Not that it crashed, but what happened next: It displayed a colorful pattern on its pads.

That's a stack trace. It's listing the last steps the code made before crashing. The devs have asked to be sent photos of these, to help them find bugs.

I've pasted it on Discord, and there's a _bot_ that recognizes these images and decodes them into addresses!

Me, in a Discord channel called "nightly-testing", writing "This is from 1.0.1 and happened a few days ago. I think I was adding synths to a kit when it crashed, but I don't remember with absolute certainty."

Below that, a picture of my Deluge. It's a black metal device with several silicone buttons with colorful LEDs below them. It also has seven knobs (some black, some gold) and an OLED screen. The lower two thirds of the device are taken up by a matrix of 8 rows and 16 columns of square pads with RGB LEDs below them. Then there's an additional 2 columns of 8 rows of the same pads to the right of that, used for muting, auditioning, and playing.

From left to right, the main matrix displays four binary patterns, each 4 columns and 8 rows in size, in different colors: purple, blue, green, and cyan. The two columns on the right also display a pattern, in red.

In each of the patterns, each LED is either illuminated in the color of that block, or not at all. Each block of 4Ɨ8 LEDs thus represents a 32Ā bit address. The two columns on the right represent the first four hex digits of the firmware's Git commit hash.

The small OLED screen says, in capital letters, white on black "Error: E339. Press select knob to attempt resume, then save to new file."

Below my post, there's a reply of the bot "Deluge Crash Reader", saying:

Thanks for the image, @scy!, it decodes as:
0x201157c0
0x2011585c
0x20110840
0x20048f4c
0xfe31
fe31a4f9b112890b16315796907788eb81314ff
Show previous comments
Jigme Datse

@scy I was looking at that and thinking... "That's a really interesting beat" but only just saw that you said it's a stack trace. Which really is amazing way to handle it. Crashing isn't fun, but having a crash that *might* be easier to handle debugging of is really awesome.

scy

"Mir's kalt. Darf ich dein Hoodie haben?"

"Ah, ein Pulli Request."

adorfer

@scy Erstaunlich aber wahr: Die Zieh-Begehren gehen den Vereinigungskonflikten voraus.

scy

Holy shit I think Iā€™m in love.

#Protomaps, a way to serve vector #maps of the entire world using a single static file and HTTP range requests.

Itā€™s basically a static site generator for interactive maps. Tile servers are pretty much obsolete now. No database needed, you can run your interactive, smooth-zooming vector map from any HTTP storage. S3, Caddy running on your Wi-Fi router, even GitHub pages.

protomaps.com/

Itā€™s open source & free to use. Wow. šŸ¤Æ

via chaos.social/@djh/111280447304

Holy shit I think Iā€™m in love.

#Protomaps, a way to serve vector #maps of the entire world using a single static file and HTTP range requests.

Itā€™s basically a static site generator for interactive maps. Tile servers are pretty much obsolete now. No database needed, you can run your interactive, smooth-zooming vector map from any HTTP storage. S3, Caddy running on your Wi-Fi router, even GitHub pages.

Show previous comments
Anthony Sorace

@scy @delan This looks like a neat project, but Iā€™m unclear of the benefits if Iā€™m not using S3 &c. 100% agree on not wanting a database, but is there a benefit if this approach Iā€™m missing over separate vector files if Iā€™m not concerned about S3 costs?

šŸŒˆ Andrew ā˜„ļø

@scy So cool! Iā€™ve been wondering for a while now whether you could do a similar thing for font subsetting. I really need to take another look at that idea.

scy

the existence of Cisco implies the existence of oh wait never mind

Google image search results showing several logos and semi trucks, all "TRANSCO".
nin

@scy and while one is packet switching, the other is shipping them. :>

scy

Hey there, #CCCamp23 people! I have about 20 or so #MiniDiscā s and would love to archive them (lossless) as FLACs. However, I only have a MiniDisc player with analog output, and would like to avoid a DACā†’ADC round trip.

Iā€™m sure one of you has a player with either a digital output, or some kind of device that can rip the discs faster than in real time? Would you mind bringing it to the Camp, and could I borrow it for a while? (Iā€™m also open to paying for that, if you want.)

scy

So @element took part in the European Police Congress in Berlin, had a booth and presentation there, and is proudly posting on the fedi about it.

mastodon.matrix.org/@element/1
mastodon.matrix.org/@element/1

Iā€™m currently paying them $11.90 a month to host my homeserver on their EMS platform.

My payment in April will have been the last.

Itā€™s one thing to provide FLOSS comms to the government. Itā€™s another to proudly support our fucked up police system.

So @element took part in the European Police Congress in Berlin, had a booth and presentation there, and is proudly posting on the fedi about it.

mastodon.matrix.org/@element/1
mastodon.matrix.org/@element/1

Iā€™m currently paying them $11.90 a month to host my homeserver on their EMS platform.

Screenshot of two toots by Element, 1 day ago:

ā€œšŸ—£ļø Our CPO, Patrick Alberts, has been busy at the European Police Congress.

Taking part in the P20 panel & presenting a prototype live demo, he's been in his Element showcasing how Element helps leverage Matrix for secure, interoperable messaging across Germany's police forces šŸ”’ā€

Attached is a photo showing a bald white guy in a suit speaking on stage, with two other white guys sitting in a panel-like setting in the back. There are EU & German & Berlin flags in the background.

ā€œWe're in Berlin today at European Police Congress! šŸš”šŸ‡©šŸ‡Ŗ  

šŸ‘‹ Come by stand 66 to talk to us about secure and sovereign communication for police and national security.

#EuropeanPoliceCongressā€

Attached is a picture with the logos of Element & the European Police Congress.
scy

I mean I remember a time when they were called ā€œRiotā€.

lol

scy

Iā€™m gonna leave this here as a reaction video for you all to add to your collection.

Source: youtu.be/BCnYOpcd_hs

#Linus #LinusTechTips #no

scy

By the way, since @vkc recently talked about using #Kdenlive to edit her videos, and not some proprietary tool:

As someone whoā€™s been using DaVinci Resolve in the past, Iā€™m increasingly using Kdenlive, too, especially for short clips. Because as ā€œprofessionalā€ as Resolve might be, itā€™s also incredibly picky about the input formats it supports. Kdenlive will basically take just about anything, from whereever you mightā€™ve downloaded it from, no matter the codecs or containers.

scy

well since we all agree that a coworker is someone who orks cows, itā€™s obvious that a manager ages men, right

Show previous comments
DELETED

@scy please oh please oh please tell me "orks" is a new sexual euphemism.

Mike, First of His Name

@scy can confirm I have aged every time I've been in the presence of a manager

the Hearth

@scy anyone named Bartholomew had better avoid bartenders, too
-F

scy

#German animal names are really something.

sloth: Faultier (ā€œlazy animalā€)
seal: Seehund (ā€œsea dogā€)
turtle: Schildkrƶte (ā€œshield toadā€)
skunk: Stinktier (ā€œstink animalā€)
squid: Tintenfisch (ā€œink fishā€)
slug: Nacktschnecke (ā€œnude snailā€)
hippo: Nilpferd (ā€œnile horseā€)
armadillo: GĆ¼rteltier (ā€œbelt animalā€)

Murmeltier, (marmot, ā€œmumble animalā€) has nothing to do with mumbling, by the way. Itā€™s from ā€œmurmentiā€, based on Latin ā€œmus montisā€, ā€œmouse of the mountainā€.

#etymology

#German animal names are really something.

sloth: Faultier (ā€œlazy animalā€)
seal: Seehund (ā€œsea dogā€)
turtle: Schildkrƶte (ā€œshield toadā€)
skunk: Stinktier (ā€œstink animalā€)
squid: Tintenfisch (ā€œink fishā€)
slug: Nacktschnecke (ā€œnude snailā€)
hippo: Nilpferd (ā€œnile horseā€)
armadillo: GĆ¼rteltier (ā€œbelt animalā€)

Show previous comments
Der Giga

@scy I mean: This has less to do with the German language than taking an outsiders perspektive.
But still; lots of fun. :D

I add:
Platypus: Schnabeltier ("beak animal")
We don't shame the feet, we shame the face.

Daniel Barlow
@scy "The Latin word hippopotamus is derived from the ancient Greek į¼±Ļ€Ļ€ĪæĻ€ĻŒĻ„Ī±Ī¼ĪæĻ‚, hippopĆ³tamos, from į¼µĻ€Ļ€ĪæĻ‚, hĆ­ppos, 'horse', and Ļ€ĪæĻ„Ī±Ī¼ĻŒĻ‚, potamĆ³s, 'river', meaning "horse of the river"", says wikipedia

"Nile horse" is just being specific about which river, I suppose.
FiXato

@scy
similarly a sloth is called a 'luiaard' in Dutch ('lui' (lazy) + '-aard' (nature, character)).
en.wiktionary.org/wiki/luiaard

Not to be confused with a 'luipaard' (leopard) though (note the added 'p' in the middle), where the 'lui' part has nothing to do with being lazy as far as I can tell, but merely is derived from 'leo'.
I first assumed the 'paard' suffix would come from the Dutch word for 'horse', making it a 'lion horse', but that too seems to be just derived from leopard's etymology: en.wiktionary.org/wiki/pard, en.wiktionary.org/wiki/luipaar

#etymology

@scy
similarly a sloth is called a 'luiaard' in Dutch ('lui' (lazy) + '-aard' (nature, character)).
en.wiktionary.org/wiki/luiaard

Not to be confused with a 'luipaard' (leopard) though (note the added 'p' in the middle), where the 'lui' part has nothing to do with being lazy as far as I can tell, but merely is derived from 'leo'.
I first assumed the 'paard' suffix would come from the Dutch word for 'horse', making it a 'lion horse', but that too seems to be just derived from leopard's etymology:

Go Up