deleted by creator

Yeah, that’s the fun bit. It’s not that Graphene can’t do calls.

It’s that in Australia, post-3G, “works on 4G” is no longer enough. The phone / firmware / carrier combo has to play nicely with VoLTE, IMS provisioning, and 000 emergency calling. If the carrier doesn’t like that exact combo, you can have perfectly good LTE data and still lose service or get nuked by IMEI/TAC filtering.

Graphene on a supported Pixel is probably the best-case scenario. Sadly, that doesn’t generalise to other phones here. It’s a dice roll.

TL;DR: VoLTE is carrier-blessed black magic. Same bands, same radio hardware on paper…very different outcomes.

Very cromulent system. Much consumer choice.

Download the shit I want, stick it on a USB key and plug it into my car. The old magics.

If you’re talking about ambient music then you have things like Navidrome or Jellyfin that can stream music throughout your house.

Ad hoc, on device streaming: I use PipePipe, choose a YT music playlist and just…play in radio mode. There are better options (like InnerTune) but those tend to crap out when YT futzes with their back end / aren’t updated as frequently as PipePipe.

I also have an iRiver MP3 player (about size of a box of matches) that’s awesome.

Don’t let the perfect be the enemy of the good.

Probably a bit too far

https://invidious.nerdvpn.de/watch?v=z5Otla5157c

PS: I used the invidious link only semi ironically.

PPS: Lemmy is social media…and it gets crawled, so…

PPPS: Back in ye olden times we used to have a rule that was “don’t reveal anything online that you wouldn’t want to appear in a court of law”. Maybe it’s time to bring that defensive online culture back.

An additional sting for some of us -

In Australia, not only is 3G deprecated (I miss my Nokia n91), but 4G / 5G must be of the VoLTE variety. To date, there is no after market OS that is fully VoLTE compatible (Legacy, Graphine etc) here - its hit or miss. Additionally, most (but not all) overseas phones are on IMEI black lists by default.

Essentially, because the OEM are lock step with Google, you can’t avoid this issue by purchasing a common phone, unlocking your boot loader (assuming you could in the first place) and flashing CFW. Do that and you can’t make phone calls. Don’t do it, and you get caught up with this new app verification slop.

They think they’re winning… but I think “lol. Keep going. I have a flip phone.” As soon as this Samsung dies (adb debloated and all), I’m out entirely.

My Galaxy A20 has been going strong since 2019. If I get anything, I’ll either be something from that era or just go full flip phone.

PS: someone mentioned the commodore flipphone. I like Perri and the C64 revival but let’s be honest here…the Callback 8020 phone is $$$ for pretty bog standard dumb phone parts. The components don’t justify it (barring perhaps the 48MP camera), let alone some of the design decisions.

If you look, I imagine you can find a local equivalent of this instead -

https://www.officeworks.com.au/shop/officeworks/p/opel-mobile-touchflip-4g-flip-phone-optouchfp

(TTfone or Sunbeam I think?)

With right launcher and larger battery, I find it perfectly cromulent, with very good keyboard. It even runs FUTO voice STT (albeit slowly), my banking apps, Signal, FB messenger, maps, 5MP camera etc. It’s not going to replace flagship anything… but maybe it doesn’t need to. And it’s 1/8th the cost.

There’s a good YouTube channel for anyone considering such devices -

https://www.youtube.com/channel/UCFtVwG0NFd6gT3TXfMCU7oA

Using a VPN makes it difficult to categorise the user. You’re obfuscating the data they want to mine and on sell. As such, your account is deemed “suspicious” (aka same profile as “bad actors”) and gets banned.

It’s all algorithmic theatre. The rules are intentionally opaque. Pay it no mind; it’s not about you, it’s about them. Their algo is coarse and binary.

Tldr: you made it too hard to sell your data (you’re the product). Fuck reddit. Speed its death by taking the good stuff elsewhere.

Try here - see post under my name

https://lemmy.ml/post/48724623

No dramas. Lemmy people be all “FuckAI!”, but anyone that audits your code can see it’s not slop

In any case,

https://vger.to/aussie.zone/comment/23463519

TL:dr

Live, on demand pirate streams (debride) as separate channel in Jellyfin (home media server).

Turns Jellyfin into a torrent-stream aggregator without needing to manage torrents locally.

Can do!

Probably not. Which means - work phone should be entirely separate from your private device, not a dual sim.

Have your work phone forward messages etc to your private device if you must, but enforce the hard boundary yourself if IT won’t won’t provide you with separate device.

It was a localsend / dropbox alternative. I’ll see if I can find it. I doubt it was removed… I suspect the dev didn’t want to deal with the pile on and deleted it.

Edit:

https://vger.to/lemmy.world/post/48335808

https://0807.st/

Anything else? Would you like to see passport and blood tests too?

“Make it my way or you’re concealing something” is a wildly self entitled take.

Your computer, your rules? Fine.

The part I don’t buy is “closed source = compromised author with ulterior motives” and “engineers who don’t prioritize FOSS are untrustworthy.” You’re automatically assuming mal-intent when there are 1000 other reasons why something might be closed source.

Maybe the code is ugly and the dev is embarrassed. Maybe there are dependency licencing issues. Maybe they want to get paid without you forking their shit. Maybe they don’t want to deal with support and PRs from people who paid nothing but expect everything.

“Open source it or it’s suss” is not a privacy argument, it’s a purity test in a trench coat. And here’s what it looks like in practice - a dev ships a no-account, no-tracking, Tor-capable file sharing tool, and gets told it’s “spam” and “malware” for not being open source:

https://vger.to/lemmy.dbzer0.com/comment/26565282

https://vger.to/lemmy.dbzer0.com/comment/26561235

Prefer open source? Sure. Support it? Of course. “Demand” it as some sort of fealty oath? Yeah, nah.

If you don’t want to use something, don’t. Maybe stop accusing others of being secret agents because you don’t like their license.

That came out 25 years ago?

…

Fuck.

Are you asking a technical question or a moral question?

Pragmatically - IDGAF. If I have it on the ssd, I’ll watch it there. If I need to download from torrent or usenet and then watch it, cool. If it’s easier to use CloudStream (for some transient series), no problem.

I tend to keep a corpus of movies / shows on my ssd because it’s always there, always reliable, always fast. I have stuff that’s just not easy to find online any more and multi-tenancy / bandwidth are no issue. I can throw it in my bag and watch it wherever, even without net.

It’s also agnostic. Not every pirate streaming app works on every device. OTOH, samba share / sftp pretty much does. Tonight I streamed stuff onto a OLPC X-O4…good luck getting fmhy to work with that - it can’t even load YouTube directly but stream stuff off the router just fine.

I don’t use JF much any more (prefer ssd plugged directly into router, accessed via NovaPlayer on android devices; files uploaded to via ftp transfer - yes, very 2010) but I think its pretty amazing. Cloudstream and fmhy are amazing too. Use what works.

Cmon now…leaving Agents.md in the repo is bush-league :)

You can bet your bottom dollar if the claude.md or agents.md hasn’t been added to the gitignore, then it’s -

1. intentional

2. actual slop (which you can more easily tell in 2 seconds of looking at the readme.md)

didn’t say it has to be a tag, what I had in mind was a simple disclosure in the post description explaining how you used AI

Same issue before though, be the actual disclosure a tag or a statement.

I do take issue with inexperienced developers that create privacy related software without proper knowledge of what their code actually does (AKA vibe-coding) and going around promoting it as “privacy-friendly” and “secure” while that may not be the case.

Slop is galling for sure but if we’re talking about trust…well…why trust anyone based on what they say (or don’t say)?

“Trust but verify” means I still verify. If the thing is mission critical or important to you, then you SHOULD verify, always. Hell, if the threat profile is high, sandbox it and sniff the packets it sends.

Personally, I think you having to look at the porn I look at is sufficient punishment for snooping on me :)

[Some of this is social engineering. “I have nothing I want to show” works even better when I literally can’t (because X isn’t on my phone or Y doesn’t run on my PC]

Maybe there are better ways to go about this though, which is partly why I created this post.

I think so.

Beyond the obvious slop (which is exceedingly obvious), you’re going to waste a lot of cognitive bandwidth trying to sniff out AI.

May as well assume AI is used by default and then do the due diligence on the privacy aspects that are of concern to you.

That holds true whether the project is hand coded or AI assisted. If it’s important, poke it.

Assume all software is “guilty until proven innocent”

But please don’t fall into the FuckAI mindset because llm=bad.

Most devs aren’t going to perform contritition for AI use to appease vocal minority. They’re just not. There’s no up side for them and it reads desperate.

I’m happy to do it because IDGAF if you use my shit or not. If I’m sharing it, it’s out of love. And If it’s open source, and I made it for me (which I generally did), then I’m probably not out to steal bitcoin or nudes. Still, do your own due diligence.

OK, seeing you asked for pushback.

TL;DR: Tool disclosure is a poor proxy for doing your own due diligence.

“Forced disclosure about AI use in projects” sits sorta funny for a privacy based group, doesn’t it? Kinda “Papers, please”. Smells bad.

How would you even verify “did this project use an LLM” anyway? If I don’t disclose, what’s the back up, pistols at dawn? Read the code (if available), or get a third party checker…like an LLM? Do you have capacity to audit? Or is it just “trust me, bro” (which if you’re actually concerned about due diligence, isn’t enough).

More to the point: disclosure tag doesn’t change whether the code is accurate, safe or good. Shitty code is shitty either way, so the tag doesn’t touch the actual harm you’re concerned about.

What it does do is create two classes: labeled projects get extra scrutiny, unlabeled ones get a free pass, “no disclosure, must be hand-written, must be fine.” Backwards. Honest disclosure gets tarnished as slop, staying quiet gets rewarded. (Go check !self hosted right now for such an occurrence).

Better footing: assume ALL software in 2026 has had AI assistance, and review it on its merits.

There are better quality signals than hand on bible “are you now or have you ever been” oaths or performative humiliation for the FuckAI crowd.

For what it’s worth, I use an LLM to write code because I’ve got osteoarthritis and typing all day isn’t free. But if you think that means logging into Claude and telling it “make this for me, no mistakes”, you couldn’t be more wrong.

I define the project, I pseudo code it with pen and paper (hurts my hands less) I scope every ticket (yes, I make the llm go thru 3 stage ticket review), I review outputs, I smoke test and I even call in outside reviewers to spot check sometimes. I’m an absolute bastard to it in QA. I do that because when I’m done, I can stand in front of it and honestly tell you I made this, even if my fingers didn’t type most of it. And if it’s fucked, that’s on me, not “hallucinations”.

So, what box do I tick - “AI-assisted”? “Vibe slop”?

That tells you nothing about who’s accountable or how it was made. It carries no nuance and silently resolves to “ignore this one, a robot wrote it,” … which is backwards for projects where the human did more QA than most “fully human” teams ever do.

As always, ICBW and YMMV.

Pain. Suffering. Death.

(I’m kidding…or am I?).

I always think of home assistant like that scene in V for Vendetta, where he set up an elaborate circle of dominoes, and everything is working perfectly right up until he gets to the last domino.

Ah, I thought you meant there was some technical issue that I wasn’t aware of / it had been superseded by a superior method.

Ethical issues aside, the arr stack is a good gateway drug for self hosting. It’s fiddly but probably in a useful way. JF/Radarr/Sonarr/Sabnzdb set up genuinely introduces a variety of branching skills.

Arr leads to self hosting, self hosting leads to home assistant, home assistant leads to … suffering :)

Your en dash is showing, Wesley.