It’s cool man, don’t worry about it.

Make sure the ram is upgradable. A lot of them are soldered on these days and you’re stuck with that amount forever.

It seems as if showing that the air defense systems are not working 100% is being seen as a threat to the government.

The world uses 102 million barrels per day.

https://www.worldometers.info/oil/

And the article says they’ll be releasing it over the course of 120 days. Maybe it’ll bring the price down by a few percent, not enough to be noticeable.

It’s just not practical to store enough oil to make any long term difference, we use too much of it and it’s too valuable to leave lying around unused.

20 hours of work turns into 20 minutes

The gains, where they exist, are nowhere near that much. In some cases, it makes developers slower (even though they think they’re a bit faster):

we find that when developers use AI tools, they take 19% longer than without - AI makes them slower.

https://metr.org/blog/2025-07-10-early-2025-ai-experienced-os-dev-study/

!general@activitypub.space, that one. Yep.

There is a convention of putting a FEDERATION.md file in the root of your project (there is a FEP about it but I can’t remember what it is, heh) which lists the FEPs your project implements.

e.g. https://codeberg.org/rimu/pyfedi/src/branch/main/FEDERATION.md

There is no standardised API endpoint for discovering this info so basically you just need to lurk in all the dev spaces you can and watch what they’re talking about, stalk each other’s codeberg/github issue queues and PRs and just cope with the jank.

Yes theoretically you could have any type in there but votes are the biggest inefficiency in the system so I’ve only implemented it for them.

There are some nodebb forums that federate with us, which are intended for AP dev discussions - !technical-discussion@activitypub.space for example. Not very active. Also some Matrix channels, again not exactly humming. Everyone is pretty focused on their own projects, really.

Maybe.

I can’t find any gavinmooney profiles on any socials… even x dot com.

It’s probably just AI generated bs.

Generally, solar takes 10+ years to break even in a residential situation, I can’t see how things would be 10x cheaper at the TWh scale.

There is a discussion but it’s an email chain between myself, Lemmy, Mbin, NodeBB so not really out in the open.

I’m thinking of using the normal OrderedCollection structure that AP has - https://www.w3.org/TR/activitystreams-vocabulary/#dfn-orderedcollection. An object of type ‘OrderedCollection’ with an array of ‘items’.

You’re right, to be more similar to the ActivityPub style of doing things the object should be a “type” of “Collection”, not just suddenly be an array instead of an object. I will migrate PieFed over to that instead.

That sounds pretty fun, I like your extremist take on things.

If you want to federate votes in an efficient way, consider doing them in batches, like this - https://codeberg.org/rimu/pyfedi/src/branch/main/docs/fep-4248.md. Sending batches means building up a queue, etc which is a pain in the ass so you might want to just receive batches and send individually.

You can do nested comments more efficiently by doing a single query for all the comments on a post and then constructing the comment tree in Go, rather than using multiple SQL queries. It’s a bit tricky to code but you can copy PieFed’s code - https://codeberg.org/rimu/pyfedi/src/commit/68d6799be5c321f9abf84d136cafef6de6e3aafb/app/post/util.py#L141

Man, I am a cranky bastard sometimes. Shouldn’t post when I’m tired.

How about - the origin server, the place where the post was originally created, gets all the metadata (og:image, og:title, etc) and includes that in the Activity that tells other instances about the post? That way there is only one request made to the link and receiving instances can use that to make their preview?

It does mean that receiving instances will need to trust the sender so there’s potential for some misrepresentation but that seems acceptable to me.

I definitely did read it.

This idea is so bad that I’m not even going to bother elaborating.

This will just lead to more requests being made.

Also anonymous requests, like those done by Mastodon to generate previews should be cached at the CDN or web server level, making them inexpensive to serve.

etckeeper can keep track of changes you make to your config. I’ve never used it but there have been many times I wish I had.

https://wiki.archlinux.org/title/Etckeeper

The thing about doing age verification at the OS level is the user could just install a crack that rewrites the necessary code. It’ll take some heavy DRM type stuff to block that. Possibly hardware support, like a specialised TPM.

No way can that be standardised and then rolled out quickly. If they rush it then it’ll be some proprietary power grab.

The alternative is each website and app does it separately which will be spotty and provide endless security breaches.

It’ll be a shitshow either way.

18% is nowhere near high enough to be throwing around accusations like that. Seems like the teachers don’t know how to interpret the results.

I recommend you set the Content-Security-Policy http header so that inline javascript (commonly used for XSS attacks) cannot be executed.

https://web.dev/articles/strict-csp

CSP being off is not exactly a security hole but it makes security holes much more likely. By using a strict CSP configuration you close off the possibility of a whole class of holes.

Also think about setting the Access-Control-Allow-Origin header and enable CORS on your REST endpoints.

https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Access-Control-Allow-Origin

Again, kind of a pain in the ass but gets rid of a bunch of potential problems before they start.