bolha.us is one of the many independent Mastodon servers you can use to participate in the fediverse.
We're a Brazilian IT Community. We love IT/DevOps/Cloud, but we also love to talk about life, the universe, and more. | Nós somos uma comunidade de TI Brasileira, gostamos de Dev/DevOps/Cloud e mais!

Server stats:

251
active users

#openstandard

0 posts0 participants0 posts today

Standard interchange image format for Open Source DTP

Hi people,

with all the mayor GUI #DTP software reaching their peak: #GIMP, #Scribus and #Inkscape; and the well established #TeX software #ConTeXt and #SpeedataPublisher, and #ImageMagick we need a serious discussion about which image format we should adopt that works seamlessly across all these applications and it is generally accepted in the press workflow, whereas is embedded or not into a PDF file.

It should be something that has good quality, supports #CMYK and Alpha channels and it is #opensource friendly and perhaps an #openstandard.

I would dare to say that perhaps jpeg2000 matches most of them, it exists from a very long time and can be adopted as common ground, however it is need a combined effort, if what I am writing makes sense for you.

ImageMagick supports it, Gimp 3 currently doesn't, #LuaTeX and #LuaMetaTeX neither. I guess that Inkscape once it will be able to export in CMYK it will decide which format using to store images in CMYK with alpha into a PDF.

It would be very beneficial if we can adopt a format that works everywhere and it is press friendly, thanks.

Replied in thread

What is the AT Protocol?

Wikipedia: “The #ATProtocol (Authenticated Transfer Protocol, pronounced "@ protocol" and commonly shortened to ATProto) is a protocol and #OpenStandard for #distributed #socialNetworking services. It is under development by #BlueskySocial #PBC, a public benefit corporation originally created as an independent research group within #Twitter to investigate the possibility of #decentralizing the service.”

<en.m.wikipedia.org/wiki/AT_Pro>

en.m.wikipedia.orgAT Protocol - Wikipedia

"Show don't tell" of federate #FOSS code & apps doesn't work well in environment where we need "Show don't tell" of #OpenStandard specs to make progress. Especially if the specs are so vague that each code implementation thrown in the cauldron of #ActivityPub #fediverse installed base is known to only add #ProtocolDecay and #TechDebt.

In #Commons #CommonSense makes #CommonsSense: Don't introduce the opposite of #interoperabily when in pursuit of seamless interop.

We need both forms of showing.

Replied in thread

@koakuma @techokami also #UltraSparcT2 as cool as it was at release (including dual 10Gbit-NICs and hardware RNG on die) has a lot of things noone would want to deal with in 2024 (i.e. DDR2-FBDIMMs).

  • Plus #RISCv unlike #SPARCv9 amd #OpenPOWER was designed on a clean slate in academia by people who had dealt with #RISC & #CISC architectures and needed something #OpenSource as they can't just violate NDAs nilly-willy for teaching.

Pretty shure @stman could write an entire curriculum on why #SPARC, #PowerPC, #s390x and even #ARM / #ARM64 should not be pursued and why #mc68k died alongside the unfixable-by-design mess that is #ix86 & #amd64.

  • Plus RISCv's ISA has been an #OpenStandard from the get go, whereas the efforts by #Oracle nee #Sun and #IBM were mostly done in reaction to it and to keep the few invested licensees and co-designers onboard and not drop the platform entirely...

Look, I'd love to get my hands on some Sun SPARC Hardware but aside from making my room hot and noisy there isn't much to justify blowing likely over half a Euro per hour (electricity price: € 0,40/kWh) just to have it up and running, as compared to a #PiCluster like those @geerlingguy had built multiple times are more practical.

  • For comparison: It's like driving a 2011 Ford CVPI-71 with a 11,9l SONNY'S SAR-729 engine for commuting from Leverkusen to Köln when there's ample of affordable, reliable and fast public transport that gets me faster from Opladen to Deutz than it takes to drive up the 15th deck of a parking garage just to find a spot to park that 5,7m long street yacht where one can climb out of it from the doors and not the trunk!

And that's just bottom-billing, low-cost ARM SoC tech designed for a price tag (to the point that until the #Pi5 they neither included a power button nor #RTC onboard!

  • OFC RISC-V is still 5-25+ years behind #ARMv9 solely based off #patents, #budget and #PersonnelHours invested in it, so it's barely getting on-par with 10-20yr old ARM devices in terms.of power and support.