HN user

gertrunde

1,250 karma
Posts1
Comments348
View on HN

My jellyfin setup is not that different.

Jellyfin container instance running on a mini pc, reading media from an NFS share on a NAS, organised in a very similar fashion.

The advantage is there is a "native" app on the TV, so everything is very adapted to the TV UX, i.e. remote control driven UI etc.

(And the jellyfin side is relatively disposable, the container can be trashed and redone fairly quickly).

There were some telephone engineers I used to know who worked in telephone exchanges in the electromechanical era, and they could tell when they walked in if things were not working correctly by the sound...

This reminds me of the time when I removed en-US from windows, leaving just en-GB, and it blue screened.

It's both surprising and irritating how many US-centric things are just assumed. (Don't even get me started on paper sizes...! ;) )

More like a replacement for something like CyberArk than for Citrix.

It's not so much about the remote access as it is about control and auditing.

i.e. ability to permit/deny certain commands/behaviours, and a complete audit log of the session, sometimes extending to a screen recording of an rdp session.

The lack of security is one thing, but why have they retained the information at all!

iirc, one of the elements of GDPR is "storage limitation", i.e. you must not keep personal data for longer than you need it - and in this case, the data is only needed to verify the age of the user, and shouldn't ever be required again (unless people can now get younger).

Once a document has been used to verify a person's identity and that the person is of legal age, there is no reason to retain a copy of the document any more.

It would be reasonable and fair to retain a photo of the user to verify that the person matches the account, but that's it.

With "AWP" (Amusement with Prize, as opposed to SWP: Skill with Prize, i.e. quiz machines), they're often set to payout 80-85% of money taken in. (SWP's are usually around 30%).

And at that level they're still pocketing hundreds of pounds per week per machine.

The most lucrative ones I've seen (admittedly ~20 years ago now) were being emptied by the operator twice a week and taking out £600-800 every time, per machine, with 3-4 machines per location.

An eye opening industry - I'm sure there are businesses out there that pretend to be one thing (pub, club, etc), but their primary profit source is gambling.

Quite possibly.

But the way that they dealt with the whole thing smelt very "we don't know what we're talking about", enough to put us off.

And shifting all the IP space about would have had costs with very little return, so little business appetite to go through it.

I once asked them if we could enable IPv6 on a 1Gb DIA circuit, and the response I got back was that "we can convert the circuit to IPv6, but you'll need to give up your IPv4."

I don't think I bothered asking them again!!

(Edit "them" = Virgin Media)

Fox to buy Roku 1 month ago

I can't really see this ending well for the end user, however well it does/doesn't end for the stakeholders.

I thought Roku took off due to their focus on the streaming platform itself, and being agnostic to the streaming services that could be accessed via that platform. Having one specific content producer buy that platform feels like it destroys or devalues the USP of the platform, at least from the point of view of the consumer/end-user.

Or is this just another step in the relentless enshittification of all services?

I'd not seen that one, and it does look like it has some nice points - although needing its own special app is rather frustrating (vs leveraging apps that people are already using).

Seems not too disimilar from the echo show's video calling capabilities in that respect (i.e. only calls within the Amazon ecosystem).

We bought two portals for elderly relatives, predominantly for video calling, and I don't think there has been another product, then or since, that fitted that use case as well, especially with people who maybe aren't as familiar with smartphones.

So somewhat frustrating when it all started to wind down various bits of functionality disappeared a bit at a time, until finally you had something that would receive calls, but not be able to make them - and perhaps not even that any more.

(About the only downside I saw on it was the messenger vs whatsapp tussle caused a bit too much confusion).

But it was a solid bit of household tech for several years, so +1 for that!

the time to fun is/was too high and was for a long time.

Yup - I got one for the other half as a present... like an hour and a half / two hours into setup/onboarding, they lost interest, it went back in the box and never came out again. :(

Literally the first sentence:

"The goal of Search has always been simple: to help you ask anything on your mind — from quick facts to the deep, complex or hyper-specific questions that can be hard to articulate."

Really? My aim has always been to find a place off google that has the information that I'm looking for.

If the purpose of google search is no longer aligned with what I want from the product... then maybe that tells me all I need to know.

If you want a search engine... it sounds like that's not what Google is any more.

Weirdly this might be a CPE problem, e.g. crappy ISP routers.

Put in something more interesting, e.g. OpenWRT, or there are proprietary options too, that provides simple & reliable local LAN DNS, then the problem just goes away.

There's a few things here that are a bit iffy tbh!

I can't see why an ISP is dynamically changing the IPv6 addressing for a client, but if that's what is going on, then v6 NPT is your friend (RFC6296 - https://datatracker.ietf.org/doc/html/rfc6296).

But pfsense's behaviour is a bit iffy too, unless when you say 'public IP', you mean the IPv6 address being used on the pfsense facing the clients? (I'm assuming it's using DHCPv6 prefix delegation, and the delegation is being changed? And potentially the uplink subnet as well).

Reminds me a bit of S/KEY (RFC1760, RFC2289 and others around the 1990's).

Not because of the encryption element, but the part about representing a 64 bit integer as a six word sequence for usability.

(https://en.wikipedia.org/wiki/S/KEY#Usability).

Also used outside of that for quickly/easily recognising hash fingerprints.

(It's easier to recognise that your fingerprint is "GAFF WAIT SKID GIG SKY EYED" than "87FE C776 8B73 CCF9").

(It also slips some parity in there for good measure).