@thomasfuchs cheese.
soapdog@toot.cafe
Posts
-
What do you think the most important human invention is? -
Posted a long rant about #Apple and how they lost me after being a user for 26 years:@dzwiedziu yeap
-
“So it failed age verification and locked me out of many features.@aral am fumming here
-
Posted a long rant about #Apple and how they lost me after being a user for 26 years:@thomas no, Linux and Android will have more glitches or maybe just as much, but in Linux I can fix things.
-
Posted a long rant about #Apple and how they lost me after being a user for 26 years:@retrofan64 be aware that UK law doesn't require device or operating system age verification. Only social networks need to do it. That was a proactive move by apple.
-
Posted a long rant about #Apple and how they lost me after being a user for 26 years:jesus... this post ended up on HN and now I need to hear why my personal view on my personal computing future posted on my own personal blog is not valid.
-
Posted a long rant about #Apple and how they lost me after being a user for 26 years:@zlatko American lobbying extends to other countries such as the UK and EU
-
Posted a long rant about #Apple and how they lost me after being a user for 26 years:Posted a long rant about #Apple and how they lost me after being a user for 26 years:
-
I miss the future.@cstross that is exactly how I develop my software.
-
I wish #ActivityPub was a "pull" protocol instead of a "push" protocol.@david_megginson the good thing about expectations is that we can adjust them

I'm not saying replace AP with something else, I'm saying let's build something different and let them all blossom. I really liked the spec described here:
FEP-b06c: ActivityPoll - Fediverse Enhancement Proposals
ActivityPoll is a proper subset of ActivityPub that excludes activity delivery, making it easier to implement for static Web sites or content management systems. It meets an equivalent need to RSS or Atom feeds.
(fediverse.codeberg.page)
-
I wish #ActivityPub was a "pull" protocol instead of a "push" protocol.@julian that was a very interesting read. I think I can implement this. Will try a small experiement soon. Thanks for sharing.
-
I wish #ActivityPub was a "pull" protocol instead of a "push" protocol.@david_megginson that is the exact problem that I want to get rid of. It really sucks. For example, I'd like to host a single-user AP server here at my flat, but knowing that it will use so much bandwidth is enough for me to reconsider it.
-
I wish #ActivityPub was a "pull" protocol instead of a "push" protocol.@LovesTha it would be a radically different experience indeed. The key is when to fetch, right? You can’t fetch as you build the feed for visualisation, fetching is slow.
You need to either make it an explicit action such as a refresh button or fetch in the background according to some interval.
Regardless, you would cache it and the feed always shows the cache. It might be out of date but it is local and fast.
Marking broken and inactive accounts is easy.
-
I wish #ActivityPub was a "pull" protocol instead of a "push" protocol.I wish #ActivityPub was a "pull" protocol instead of a "push" protocol. The way it works, whenever you take an action, it sends that action to all followers. I would prefer if it simply stored them and then let each follower pull them when they see fit.
That would introduce latency and more async comms as your messages wouldn't pop up into someone elses feed until their software fetch the data, but I think it would make it easier to self host.
-
A new twist in the "AI license laundering of chardet" story https://github.com/chardet/chardet/issues/327@cwebber that whole relicensing and this slop reply are vomit inducing.