@rml
Do you know any small #scheme (#guile?) projects I could browse to learn by example?
I've been trying to get into #lisp for ages, but most tutorials are either philosophical/historical or only cover the basics. Take hautils[1], a collection of small POSIX utilities written in #hare/#harelang, which demonstrates digestible common programming practices, which would be out of scope for the official tutorial. Is there an analogue project for scheme?
Feel free to boost.
> [...] an important announcement: I will migrate all my repositories and projects from Sourcehut to Codeberg in the following days (including Husky). Over the last year I tried to make myself comfortable with the email workflow, but over time, I felt that workflow is not suitable for me.
Awh... All that contributor frustration! I understand you just want Husky development to progress.
Okay, fine, actual #introduction . I've been on the Internet or social media by the handle Albatross since 1977.
In 1983 I created the world's first #MMORPG company, GamBit MultiSystems, and our franchisees went on to start some big-name game companies.
In 1991 I helped co-write the Internet Gopher protocol, RFC 1436.
I've been in infosec since 1996 and I'm heartily tired of keyboards.
I've written books and plays and shoot pictures. I have 3 terrific adult kids.
@dheadshot @apps
Yep.
Also, shouldn't the "Edited at .." thing be more attention grabbing? Maybe keep it small, but give "Edited" a strong colour, jet pink? To mitigate edit abuse.
An update on leap seconds
Tony Finch
https://dotat.at/@/2022-12-04-leap-seconds.html
@Yujiri
See other reply
https://qoto.org/@torresjrjr/109355952588722622
👋 Hello Fediverse! 👋
@captainepoch
There's *a lot* to unpack and explain, but basically,
This thread on leap minutes and hours got me thinking
https://pairlist6.pair.net/pipermail/leapsecs/2022-November/thread.html
And this post made me think and disagree
https://pairlist6.pair.net/pipermail/leapsecs/2022-November/007444.html
Resolving ambiguous or nonexistent UTC timestamps is a much easier and encapsulable problem when the shifts and deltas are within 1 second. The domain of applications which handle UTC leapsecs are niche (scientific, military, fintech), and when they do, it's fairly simple, or can be with good design.
The @hare standard library separates the concerns of 'civil' timeshifts (timezones, DST) and timescale timeshifts (leap seconds), going as far as to include a 'timescale' type.
https://docs.harelang.org/time/chrono#timescale
The proposed alternative leap-minutes or leap-hours make a lot civil time software needlessly complicated, blurring 'civil' and 'timescale'. The same clusterduck of problems with timezone shifts and DST would now be part of UTC itself.
Then there's also the Earth's phase and velocity of rotation, drifting noons and midnights, politicians and dictators chiming in, forward compatibility, etc. It's a charged topic for sure.
Gek — The stack-based stream editor
https://gek.johngebbie.com/
@Pixificial
I have heard of YaCy. Search engine decentralisation is a very tricky thing to achieve. I don't know how effective YaCy is.
I'd love to use P2P chat app Briar[1] all the time and for everything, but my battery drains very quickly. Seeding is resource taxing. It's P2P design is impractical and thus unsusable for casual use.
Web engine and Javascript bloat is another topic.
Fediverse _should_ mean that of the ActivityPub network and only the ActivityPub network, and this poll, like many others, sets this precedent.
Otherwise, we risk diluting the meaning of this word. The Fediverse is growing, and it won't take long before some profit-motivated company comes along and starts providing trojan horse "Fediverse compatible" service with "mostly not really interoperable ActivityPub extensions". Law makers won't tell the difference.
@Pixificial
Cheap devices with low specs, and thus developing areas around the world, wouldn't be able to keep up. Centralisation is not inherently bad, and pure peer-to-peer is not inherently good. Generally, federation is the best of both worlds. A single server on a VPS for a single small website is cost effective.
Making DNS lookups purely peer-to-peer is a great idea, though. We ought to support projects like #opennic and break censorship.
@Pixificial
They're all designed for different purposes. You use what you need. They are not mutually exclusive.
My black body story (it's physics).
By Rob Pike
2022-08-22
https://commandcenter.blogspot.com/2022/08/my-black-body-story-its-physics.html
Libre software engineer with physics background.
Maintainer for @hare date/time.
.py .go .ha ...
en es ...
\t <dl> agpl posix 9p