@mdhughes @screwlisp

i suppose it is probably confined to utility tools and text editors, i will admit.

you are right that a lot of BASIC is tied to the hardware that it is running on.

the platforms i have dealt with most are variants of 8K MS BASIC, which includes the C64 and VIC-20.

i have also had dealings with Dartmouth, and also Atari BASIC.

like anything, i think it depends what you want to get out of the language, and what you want to do with it, practically.

#basic

@danog @thephpf i'm auto-updating, but only once per day. so with a vulnerability like this, that window is a bit large?

It was my first thought too but there are downsides to it. Trust is a small one given the nature of the system but compute and bandwidth costs could be an issue also, especially for larger instances.

The first solution is more fragile but could be CDN’d and those are cheap.

@ramsey @thephpf "Doing more security releases" = how often exactly? Once a week at most? With AI-based vulnerability research, I would allow at least one release a day.

Yes, it will feel like the release cadence of npm packages, but this must not be a blocker: people have to get used to autoupdating PHP.

@futzle I've just been going with PHPwned

OpenAI expands ChatGPT ads to 26 additional countries, taking the total to 83 countries, and says the platform's advertiser base is 100K+, up from 20K in August (Alix Coutures/The Information)

https://www.theinformation.com/briefings/openai-expands-chatgpt-ads-26-countries-says-100-000-advertisers
http://www.techmeme.com/261021/p26#a261021p26

@albertcardona @guenther no version is safe, for now...

I’m trusting the user who submitted the link and/or the instance that user is on. I’m doing that anyway by clicking on their link right?

HTTP signatures are not a default feature, the baseline is ECDHE key exchange with forward secrecy and deniability.

There isn’t even an official standard for redistributable signed page metadata. There’s just prototypes

Rappers for Regime Change: How the CIA Recruits Hip Hop Artists Around the World – Orinoco Tribune
https://orinocotribune.com/rappers-for-regime-change-how-the-cia-recruits-hip-hop-artists-around-the-world/

#CIA #Propaganda

Finally we have created the random number "4" from the famous XKCD strip "do not just make your random number 4"

@pixelfed What exactly is going on with #PHP?

That’s not true, you know the data hasn’t been tampered with because of HTTP signatures. The fediverse isn’t just “yolo, just trust me bro”. There are some parts that are a bit more towards that side (particularly with groups on Lemmy) but I don’t think this should be.

The same way you know the rest of the data hasn’t been tampered with - you don’t. And when you find untrustworthy instances, you defederate from them.

how would you know the results havent been tampered with?

There are two proposed solutions I have seen. I do not claim that this is exhaustive, just only limited to the proposals that I have stumbled across.

FASP - Fediverse Auxiliary Service Provider

The idea that mastodon has is to have a third-party service that does something like generate a link preview once and then share that to fediverse instances that need it. They have a whole spec they wrote up about these kinds of services that can be run to help out fediverse instances with different things like this, search, or discoverability. They call these FASPs - the repo with the spec is here.

I don’t yet know of any FASP that is live and running, so it is kind of a paper spec at the moment. I don’t do too much on the microblogging side of the fediverse though, so I very well could be wrong.

Federate link metadata and the post at the same time

This comes from an issue on PieFed’s repo. It is basically just an idea at this point, but it is a pretty basic one; have the originating instance fetch the link preview information and simply federate it out alongside the post itself.