m0xEE @m0xee@librem.one

@newt @echo
But we can still thank dating sites for giving us social networks 😂
In fact what we mean by social networking existed even in the nineties: dating sites had messaging/chats, rating photos, casual online multiplayer games… No one was conning them social networks though. Facebook's major breakthrough IMO was proper marketing — shifting the focus away from dating so less people started shying away from participating.

@newt @echo
Looks like this field is in a bit of a crisis now: https://www.theguardian.com/lifeandstyle/article/2024/aug/17/dating-apps-decline-bumble-tinder
I find it not hard to believe they might be hiring workforce abroad to keep the people engaged TBH 😏
Not that I would miss if most of these websites and companies close down, I've always found commodification of romance cynical and if you're looking for a hook-up, it's not like there were no options even without these apps.

@romin
My conpooters aren't that old yet 😏
The MacMini my Repolma instance is hosted on is nearing twenty though 🤭

@aronow
That donut toy looks so much fun 😻
My cats would certainly carry it around a lot!

@newt
> No, I mean the Personal Area Network profile in Bluetooth. It also emulated Ethernet.
Yeah, I remember PAN back from the days when my ThinkPad T43 was still brand new — I've never seen it used in real world, yes — why bother when there is Wifi? 🤔
It might make more sense now that Bluetooth LE exists — to save the battery, but I've never tried that myself.
@Aeder

@awilfox
There is also a branch with an attempt to port newer libgo to older gccgo in the Adelie tree — that one failed to build on my machine too, but my experimenting with it is somewhat hindered by the fact that complete rebuild of gcc on this MacMini takes forever😅 So I might've missed something.

@awilfox Thanks for all your patches and for keeping PowerPC alive!
Did you manage to advance any further in making newer Go work on 32-bit machines? I see that Adelie got updated with GCC 13 about 10 days ago? Does gccgo in that one get built properly? I think I've tried those patches when they were still in the experimental branch and it didn't work for me.

@newt
> PAN.
This has existed since the early days of Bluetooth, but I've never seen it used in reality. Well, with absence of serial interface, looks like its time has come. Why even bother with Bluetooth then and not just use wireless ethernet, is it easier on the battery?
> Those I saw provide a virtual ethernet adapter.
Well, like I said, mine might be just old. I like none of this! First integrated audio interfaces using USB and now this. This is just fucked up, man! 😠
@Aeder

@newt
> They no longer support DUN or RFCOMM profiles via bluetooth.
For real?! 😲 This sucks!
How does tethering over Bluetooth work then? 🤔 I've never used it TBH.
Dedicated cellular modems still do provide virtual serial port though — but I won't put my money on it, the ones I have are rather old too.

@Aeder

@romin
Minor downside: you have to put local modules into src/ too — obviously (it's in the name) GO111MODULE didn't exist in this version either.

@romin
You can now! I'm not even sure when they have added it — this version doesn't support it either. A directory named "vendor" is handled in some special way, but it only seems to affect the namespace visibility and nothing else, it doesn't look for dependencies in this dir.
But you can always put everything under src/ and point GOROOT to the current directory — very straightforward!

@newt @Aeder
How dare you — SMS is a zoomer thing! I want fax interface for Fedi: you dial in, tone-dial the thread id and in a couple of minutes it calls you back and faxes you the printout of the thread — now we're playing! Read grown-up stuff! 👨‍💼

@romin
I've already forgotten that GOPROXY simply didn't exist then, you don't even have to do "go env -w GOPROXY=direct" — that might be related to "go env" simply not supporting the "-w" parameter in this version though 🤣

@romin
Ackshually yeah — correct! I had to deal with this older go yesterday and it appeared to be way less broken than it is today 😂
E.g. the way it handles the dependencies: just issuing "go build" and seeing it retrieve all the dependencies itself is fine and dandy, but having them saved in a particular directory locally and not depending on… 🤬 GOPROXY is preferable to me.

@tyler
Turns out you can!
I'm still updating the thread: https://social.librem.one/@m0xee/112983810359104857
TL; DR it's REALLY old — backporting to that would take a significant effort, but it works! I've managed to get BloatFE running matively on the same PowerPC machine my Pelorma instance runs on. It has very few dependencies, but it still took me a couple of hours yesterday.
@pyrate

I've also had to update libbacktrace to the one from gcc 10.5 — my system seems pro produce binaries with dwarf-5, but older libbacktrace does not support that and adding "-gdwarf-4" to CFLAGS somehow failed to fix that for me.
This go toolchain still fails to produce fully statically linked binaries as normal go toolchain does — this is probably related to libucontext in Void only exporting prefixed symbols. But that's a relatively minor problem, statically linking libgo works fine.

Good news is — it's possible to make #golang work on a relatively up-to-date #powerpc system, even though it's really dated: gccgo that comes with gcc 8.5.0 provides go 1.10.3… Yeah-yeah, but even this is one hell of an achievement, at least programs that only depend on the standard library work reliably.
Thanks to Adelie Linux maintainers and their set of patches: https://cgit.adelielinux.org/packages/tree/system/gcc?id=b7807f42fbd231b0783eb0d26fd60b63153ca6d9

And yes, I've built #ziglang too, but it fails to produce binaries even for the hello_world type of programs, I have no idea what the problem might be, but as it depends on LLVM (and even comes with LLVM 18 for bootstrapping), it could be literally anything.

And you can't build newer Rust using older tools — because it only supports last 3 releases of LLVM and they have cranked out quite a few of them in the past couple of years, but the worst part is those LLVM releases can only be built with GCC 13. This looks somewhat relevant: https://github.com/llvm/llvm-project/issues/95594
Why does everything have to depend on the latest versions and be so fucking broken? 😩