Actually given that, if you have a weekly with AI as part of it, tagging [AIT] will allow people to filter it out.

Its pretty ancillary to the newsletter itself so its not really required, but just to mention… if it were tagged, any low effort comments like “slop” or similar would then be removed. I don’t really see that on your posts in general though, so more a thought for later should it become a problem.

Please tag your post ( [CBH] or [AIP] ) and if AI was used, add the disclosure

See rules 7&8 and message with any questions

Thanks!

Telemetry is one reason.

Not having to worry about the service shutting down (Google Reader) is another.

Synced read status is a common one as well.

You may also use it in combination with another service to create RSS feeds for sites that dont have one.

Honestly having it not just get killed like Google Reader is a big chunk of the userbase.

Edit: Completely misread things, I thought you had 192.168.10.0 and 192.168.20.0. Yes it would be the whole subnet for a /24, if you wanted less you’d go higher as mentioned.

192.168.0.0/29 would include 192.168.0.1-192.168.0.7.

/28 would get you up to 192.168.0.15.

No, /24 is just 256 IPs.

192.168.0.0/24 = 192.168.0.0 mask 255.255.255.0, or 192.168.0.1-192.168.0.254.

If you want 192.168.0.0 through, say, 192.168.7.254, you need to cover 2k ip’s, which is a /21. The mask would be 255.255.248.0.

A /24 would only be the last octet.

Then you are missing the [CBH] tag.

If its a single image, I’d agree. If its a compose with multiple images though, better off combining into a single lxc or VM.

I got so annoyed when work tossed a system with that case. It was supposed to be set aside, but someone missed the memo.

Proxmox supports OCI containers natively now

As of 9.1, and kind of. To be clear what its doing is not a drop-in replacement for docker, but using that image as a basis for an lxc - so you’re not just pulling a new image to update, more like re-deploying, so keep your stored data elsewhere, outside of the lxc. So what was handled by pulling an image or a change to a compose is done manually in proxmox now, but it does make things like backups/snapshots much more consistent and proxmox-native.

DIY robovac time!

I wanna see full uprights, like the canister vacs mounted on an rc truck base.

If you waited long enough to get past the account duration requirement and it was open source, where people could evaluate and comment on what they see, yes.

If it were paid/closed source, then no, not without using that alt constantly to meet the requirements.

The point in the first place was the large influx in promo postings that were made, as well as create filterable tags for users who are or are not interested in seeing AIT or AIP. It also means for those who create an AI involved project, no matter the level, aren’t being bombarded with low effort, one word disparaging comments.

If you have another idea, or some way you believe a third person can have any realistic insight to provide a disclosure, you are welcome to create a meta discussion on it as there were for rules 7 & 8 already.

Its required for self promotion, there is no way for a third party to know the details to tag and disclose.

It would be like posting plex feature updates. There is no way for the poster to know whether or not any AI was used in development (though given the Plex trajectory, we all know, but thats a different matter).

Doing Things For You is not its best use.

Thats a bingo!

I find it a great tool for QA/QC (with RAG, without its… eh), managing tone in a document, finding potential security issues, etc.

But doing it all for you I have not found to be a useful experience.

Much appreciated!

Please also add the disclosure, see expanded details for rule 8 and the examples post

Thanks!

One is pre-k and the other is elementary school aged, so I think even a yubikey is going to be too much 😄

But I’ve been thinking NFC because I have a bag full of tags I can use, I’d just need a reader there

I dunno, I can understand a curated blocklist, topic-based. Obviously not what this is - if things were up front it wouldn’t have been an issue - but maybe someone just does not like memes. A curated meme community list would be handy. If someone didn’t want to be on a more curated instance like blahaj but still wanted to filter out specifically problematic anti-trans users, that would be useful.

Just like its up to the users to decide what instance you want to join, it also should be up to the user to decide if they want to take that further, and a front end would be the appropriate place for that (especially since its not baked into lemmy or piefed to have an imported list).

The problem has nothing to do with the option of centralized blocklists, but the hidden nature of the one in tesseract in its entirety.

Its no different than when GarageBand was a thing - it was really accessible, so musicians who couldn’t figure out the tech side before (or didn’t want to pay money out for something) started using it heavily and really liked it. You also got an outsized influx of people who didn’t understand music who created a whole bunch of stuff that had… issues. You’d see people ask for feedback, and get constructive criticism, and they would just get pissed off at the lack of praise.

Which led to every time someone newer posted something they made, a bunch of comments about how horrible it was that people were pumping out garbage with GarageBand. The scale was much smaller obviously, but the results are the same as now imo.

I think some will start to us LLMs as a tool to get answers (instead of a stackoverflow link that is marked duplicate and the old post is gone or uses horribly outdated libraries), some will get lost thinking they are geniuses with unique prompt mastery, and others will move on. Time will tell though.

Eh, I think it depends.

In terms of display and content management, even how the client apps work, I’d say Jellyfin is far, far ahead.

Plex’s only advantage (to me) would be remote access, and even then I’d say its just how accounts are handled. Which is only good when Plex auth is working properly, and an absolutely awful experience when its not.

I like having SSO in front of JF, I think its a much better experience. Now I just need to figure out how to get my kids to use SSO without a device… Which I’m leaning toward an NFC reader and a tag for each of them, maybe in a toy or something they can tap to a reader. TBD.