Wait this is still a thing? I remember writing a DCC download bot in arexx on the amiga, back in the mid 90s.

So, just going to say. I feel like this violates rule 1: (Not United States Internal News)

In any case, as an outsider I feel like it’s more than obvious that the step up in activities and rhetoric is a direct response to the realisation that there’s mid-terms coming this year and as it stands they will lose hugely.

So yes, they want to either take control of the voting, or even better stop the election entirely. This is what is being worked towards right now, just from me looking from the outside in.

I would say, now it’s learning that actually sticking your head in the sand is only ever a delaying tactic. But, if it DID learn that, it’d mean it has surpassed us already.

Yep. I also valid concerns. But those seem to be their next steps. I just wondered if there would be degradation. You wouldn’t even be able to tell until it reached the destination.

Definitely interesting stuff.

I think my question on all this would be whether this would ultimately cause problems in terms of data integrity.

Currently most amplifiers for digital information are going to capture the information in the light, probably strip off any modulation to get to the raw data. Then re-modulate that using a new emitter.

The advantages of doing this over just amplifying the original light signal are the same reason switches/routers are store and forward (or at least decode to binary and re-modulate). When you decode the data from the modulated signal and then reproduce it, you are removing any noise that was present and reproducing a clean signal again.

If you just amplify light (or electrical) signals “as-is”, then you generally add noise every time you do this reducing the SNR a small amount. After enough times the signal will become non-recoverable.

So I guess my question is, does the process also have the same issue of an ultimate limit in how often you can re-transmit the signal without degradation.

At home I’m on Linux but yes I also have a work laptop and I hate windows more and more daily.

So far I’ve mostly avoided the whole “things that don’t need to be on the Internet” situation.

Non smart TV (well that period when they started adding smart features but they’re all out of date now so not even connected to the Internet)

All kitchen stuff is just kitchen stuff. No Internet.

Car is still offline.

Only real exception is smart thermostat, and that’s just because when the boiler was installed that’s what they put in.

It’s interesting for everyone, but if the split is US news and World news, this is a US centric story. All of the players are US based. Like I say, the subreddit’s the naming convention these communities are based on had very much a “US” goes in news and “RoW” goes into WorldNews ethos.

I don’t see policies stating that here. So I think it’s a very different situation to the other place (and we can argue about why there’s two news communities, but that’s another story). But, I was just wondering if the moderation was done in the same vain.

I wonder if not allowing this on world news is a leftover from the reddit split between news/worldnews. In the rules here I cannot see anything that says news = US news. But on reddit the news sub DID have that rule. They would delete any non-us story.

As such worldnews was for all non-US news and in that case deleting this very US centric topic would be fair game.

There isn’t that clear cut difference between news/worldnews on the fediverse. It looks like the two communities were created to mirror reddit. But, the rules don’t align.

Also, even as a non American. I knew it would be OAN.

Then I suggest they use an XNOR pointer instead! Checkmate patent trolls!

Huh. I am sure you could search for individual books. For sure you could do it by goodreads ID I think? Yes, adding an entire author as the primary way to do things is a bit much for some. I know for sure I have managed to do individual books before now.

It’s a real shame because Readarr did work and they really just needed to fix their own metadata servers. No? Or were there other problems I’m not aware of?

I mean, I have to say I’ve hastened my own demise (in program terms) by over-engineering something that should be simple. Sometimes adding protective guardrails actually causes errors when something changes.

Yes, had the same happen. Something that should be simple failing for stupid reasons.

Yep. It seems they haven’t changed a thing about the format. Probably a script much older than mine on their end is generating it too.

I have a tool that I wrote, probably 5+ years ago. Runs once a week, collects data from a public API, translates it into files usable by the asterisk phone server.

I totally forgot about it. Checked. Yep, up to date files created, all seem in the right format.

Sometimes things just keep working.

Oh, this might be some instagram/threads thing then, I know they share an account. I don’t use either of those services.

I know on Facebook there’s these ads for threads and it’s putting random thread “stories” (I don’t know what they’re called) up on the timeline. So I thought they were doing a similar thing between all three services and not honouring the privacy setting.

Still, just my personal opinion. If there’s automatic crossposting, the default really should be to use the more restrictive privacy setting for each service.

No, it’s obviously the trans led far left extremists!

Well, I still have a Facebook account for the few people that are only on there. I am getting ads showing Threads posts, and if you click it, it takes you to threads and wants you to make an account.

So I’m assuming what is happening is that they’re taking posts from one service and showing them on their other services with click through to make accounts on those services. I guess they’re not honouring the privacy setting on the source service. Which if that is the case, is just terrible.

I was about to say, it’s normal for meta. But then I read they made private posts public on the other platform.

No, just no. No excuse for that at all.